date:20161214

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

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

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

Title:
  does not read mpeg transport streams since #1643467

Status in libav package in Ubuntu:
  Confirmed

Bug description:
  Since the security update to 6:9.20-0ubuntu0.14.04.1 triggered today
  by #1643467, vlc and mplayer do not play mpeg transport streams that
  were previously playable.  Other types of stream are unaffected.

  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  libav-tools 6:9.20-0ubuntu0.14.04.1
  libavcodec54:amd64  6:9.20-0ubuntu0.14.04.1
  libavdevice53:amd64 6:9.20-0ubuntu0.14.04.1
  libavfilter3:amd64  6:9.20-0ubuntu0.14.04.1
  libavformat54:amd64 6:9.20-0ubuntu0.14.04.1
  libavresample1:amd646:9.20-0ubuntu0.14.04.1
  libavutil52:amd64   6:9.20-0ubuntu0.14.04.1
  libswscale2:amd64   6:9.20-0ubuntu0.14.04.1

  vlc 2.1.6-0ubuntu14.04.2
  mplayer 2:1.1+dfsg1-0ubuntu3

  $ mplayer -ao sdl file.mpg 
  MPlayer 1.1-4.8 (C) 2000-2012 MPlayer Team
  mplayer: could not connect to socket
  mplayer: No such file or directory
  Failed to open LIRC support. You will not be able to use your remote control.

  Playing file.mpg.
  libavformat version 54.20.4 (external)
  Mismatching header version 54.20.3
  MPEG-PS file format detected.
  VIDEO:  MPEG2  720x576  (aspect 3)  50.000 fps  9500.0 kbps (1187.5 kbyte/s)
  Load subtitles in /
  Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object 
file: No such file or directory
  [vdpau] Error when calling vdp_device_create_x11: 1
  ==
  Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
  libavcodec version 54.35.1 (external)
  Mismatching header version 54.35.0
  Selected video codec: [ffmpeg2] vfm: ffmpeg (FFmpeg MPEG-2)
  ==
  ==
  Requested audio codec family [mpg123] (afm=mpg123) not available.
  Enable it at compilation.
  Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
  AUDIO: 48000 Hz, 2 ch, floatle, 256.0 kbit/8.33% (ratio: 32000->384000)
  Selected audio codec: [ffmp2float] afm: ffmpeg (FFmpeg MPEG layer-1 and 
layer-2 audio)
  ==
  [AO SDL] Samplerate: 48000Hz Channels: Stereo Format floatle
  [AO SDL] Unsupported audio format: 0x1d.
  Failed to create secure directory (/run/user/0/pulse): Permission denied
  Failed to create secure directory (/run/user/0/pulse): Permission denied
  AO: [sdl] 48000Hz 2ch s16le (2 bytes per sample)
  Starting playback...
  Unsupported AVPixelFormat 53
  Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
  VO: [xv] 720x576 => 1024x576 Planar YV12 

  
  MPlayer interrupted by signal 11 in module: decode_video
  - MPlayer crashed by bad usage of CPU/FPU/RAM.
Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
  - MPlayer crashed. This shouldn't happen.
It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
gcc version. If you think it's MPlayer's fault, please read
DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
won't help unless you provide this information when reporting a possible 
bug.
   [ This binary of MPlayer in Debian is currently compiled with
 '--enable-debug'; the debugging symbols are in the package
 'mplayer-dbg'.]

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

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

[Touch-packages] [Bug 1648905] Re: VPN username and settings not saved

2016-12-14 Thread dwmw2

When do we get a fix for 16.04?

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

Title:
  VPN username and settings not saved

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The OpenConnect VPN auth-dialog doesn't remember usernames and other
  settings.

  See discussion (and fix) in
  https://bugzilla.redhat.com/show_bug.cgi?id=1332491

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

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

[Touch-packages] [Bug 1583088] Re: Randomly corrupt characters in Unity8

2016-12-14 Thread dinamic

same here on both 17.04 and 16.04+overlay (intel and nvidia)

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

Title:
  Randomly corrupt characters in Unity8

Status in Canonical System Image:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1649861] [NEW] When upgrading to oxide 1.19, tabs from saved session are not restored

Public bug reported:

When upgrading to oxide 1.19, tabs from a session saved with oxide 1.18
are not restored. I’m seeing the following in the browser’s log:

  Failed to read initial state: invalid data

It appears sessions::SerializedNavigationEntry::ReadFromPickle() fails,
most likely because the format of the serialized entries was changed in
chromium 55. Specifically, this commit seems like a good suspect:
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

** Affects: oxide
 Importance: Undecided
 Status: New

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

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

** Summary changed:

- With oxide 1.19, tabs from saved session are not restored
+ When upgrading to oxide 1.19, tabs from saved session are not restored

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

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

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

[Touch-packages] [Bug 1640823] Re: [trusty] mount -o loop is limited to 8 loop devices

This bug was fixed in the package util-linux - 2.20.1-5.1ubuntu20.9

---
util-linux (2.20.1-5.1ubuntu20.9) trusty; urgency=medium

  * mount/lomount.c: Query /dev/loop-control for next free loopback device.
(LP: #1640823)

 -- Thomas Voß   Tue, 15 Nov 2016 09:52:37
+0100

** Changed in: util-linux (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  [trusty] mount -o loop is limited to 8 loop devices

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Fix Released

Bug description:
  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature
  was introduced in Linux 3.1 already (i. e. before precise even). This
  is a showstopper for backporting snappy as that needs a lot of loop
  mounts.

  Support for loop-control got introduced later util-linux versions, but
  backporting full support for it (for losetup) is too intrusive. We
  only need a partial backport for "mount -o loop".

  SRU TEST CASE:
  First, use up all default 8 loop devices:
  $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done

  Now try to use a 9th:
  $ dd if=/dev/zero of=/tmp/img bs=1M count=50
  $ mkfs.ext2 -F /tmp/img
  $ sudo mount -o loop /tmp/img /mnt

  With current trusty's "mount" package this will fail with "could not
  find any free loop device". With the proposed version, this should
  succeed, and "sudo losetup -a" should show "/dev/loop8: ...
  (/tmp/img)".

  Now, reboot, disable loop-control with

    sudo mv /dev/loop-control{,.disabled}

  and run the test case again. Now "mount -o loop" should fail with
  "could not find any free loop device" (as before). Ensure that there
  are no hangs, infinite loops, etc.

  ADDITIONAL REGRESSION CHECKING TEST CASES

  1. Check that every type of losetup call documented in the losetup
  manpage still works correctly.

  2. Check that mount and umount commands that use loop devices still
  work correctly.

  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-
  linux support has exited for a long time without known/major issues,
  so this should be fairly safe. Also, the patch falls back to the
  previous "iterate over loop0 to loop7" behaviour if loop-control is
  not available.

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

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

[Touch-packages] [Bug 1649313] Re: Mediascanner is not working

2016-12-14 Thread Victor gonzalez

Hi @jamesh

1. Here is the content of mediascanner log after installing my sdcard:
https://pastebin.canonical.com/173543/

2. From adb shell I get mediascanner-2.0 start/running, process 8728

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

Title:
  Mediascanner is not working

Status in mediascanner2 package in Ubuntu:
  New

Bug description:
  Story: looks like this is a well known bug but there wasn't a bug
  report yet so I'm opening it. Mediascanner doesn't work in
  frieza_arm64 so files in sdcards aren't detected.

  Environment:

  current build number: 99
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-12 12:21:18
  version version: 99
  version ubuntu: 20161210
  version device: 20161014.0
  version custom: 20161210

  Steps:

  1º Put some media files(songs,videos) on a sdcard
  2º Install the sdcard in frieza
  3º Open music app or music/video scopes

  Current result: music app reports no songs were found and music/video
  scopes don't show the media files either

  Expected result: all files from sdcard r other external devices should
  be detected

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

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

2016-12-14 Thread Robie Basak

> The test case in
https://github.com/krb5/krb5/pull/436#issuecomment-209017277 is the best
we can offer without going through the trouble of setting up OMI.

This is fine, but it should be explained in this bug so people
processing this update do not get confused. Please follow
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure step 3, which is
not yet complete. If you can't edit the bug description, adding that
information in a comment is fine.

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Incomplete
Status in krb5 source package in Xenial:
  Incomplete
Status in krb5 source package in Yakkety:
  Incomplete

Bug description:
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

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

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

[Touch-packages] [Bug 1640823] Update Released

2016-12-14 Thread Robie Basak

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

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

Title:
  [trusty] mount -o loop is limited to 8 loop devices

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Fix Committed

Bug description:
  trusty has a very old util-linux which does not yet know about /dev
  /loop-control to create arbitrarily many loop devices. This feature
  was introduced in Linux 3.1 already (i. e. before precise even). This
  is a showstopper for backporting snappy as that needs a lot of loop
  mounts.

  Support for loop-control got introduced later util-linux versions, but
  backporting full support for it (for losetup) is too intrusive. We
  only need a partial backport for "mount -o loop".

  SRU TEST CASE:
  First, use up all default 8 loop devices:
  $ for i in `seq 8`; do echo $i; sudo losetup --find /etc/issue; done

  Now try to use a 9th:
  $ dd if=/dev/zero of=/tmp/img bs=1M count=50
  $ mkfs.ext2 -F /tmp/img
  $ sudo mount -o loop /tmp/img /mnt

  With current trusty's "mount" package this will fail with "could not
  find any free loop device". With the proposed version, this should
  succeed, and "sudo losetup -a" should show "/dev/loop8: ...
  (/tmp/img)".

  Now, reboot, disable loop-control with

    sudo mv /dev/loop-control{,.disabled}

  and run the test case again. Now "mount -o loop" should fail with
  "could not find any free loop device" (as before). Ensure that there
  are no hangs, infinite loops, etc.

  ADDITIONAL REGRESSION CHECKING TEST CASES

  1. Check that every type of losetup call documented in the losetup
  manpage still works correctly.

  2. Check that mount and umount commands that use loop devices still
  work correctly.

  REGRESSION POTENTIAL: /dev/loop-control and the corresponding util-
  linux support has exited for a long time without known/major issues,
  so this should be fairly safe. Also, the patch falls back to the
  previous "iterate over loop0 to loop7" behaviour if loop-control is
  not available.

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

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

[Touch-packages] [Bug 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

2016-12-14 Thread Федотов Сергей

Adam, I can confirm, bug fix is worked for me, while Russian keyboard
and timezone was selected.

dist: xenial
apt: 1.2.18/xenial-proposed
ubiquity: 2.21.63.3

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1641328] Re: Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS lookups to fail -- breaks network printing

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

** Changed in: nss-mdns (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes
  mDNS lookups to fail -- breaks network printing

Status in nss-mdns package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  (See also libnss-resolve:amd64   231-9ubuntu1 amd64nss module
  to resolve names via systemd-resolved)

  
  # fresh install of yakkety 

  mtearle@liberation:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  # package details

  mtearle@liberation:~$ apt-cache policy libnss-resolve
  libnss-resolve:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages
  mtearle@liberation:~$ apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.rackspace.com/ubuntu yakkety-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.rackspace.com/ubuntu yakkety/main amd64 Packages



  # attempt to ping VM elsewhere on network with mDNS hostname

  mtearle@liberation:/etc$ ping bazzavan.local
  ping: bazzavan.local: Name or service not known

  # can find both ipv4 and ipv6 addresses for the host

  mtearle@liberation:/etc$ avahi-resolve-host-name bazzavan.local
  bazzavan.localfe80::a00:27ff:fea5:3f51

  mtearle@liberation:/etc$ avahi-resolve-host-name -4 bazzavan.local
  bazzavan.local172.16.44.48

  # can ping it

  mtearle@liberation:/etc$ ping -c 1 172.16.44.48
  PING 172.16.44.48 (172.16.44.48) 56(84) bytes of data.
  64 bytes from 172.16.44.48: icmp_seq=1 ttl=64 time=0.265 ms

  --- 172.16.44.48 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.265/0.265/0.265/0.000 ms

  # original ordering

  mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf 
  hosts:  files resolve [!UNAVAIL=return] mdns4_minimal 
[NOTFOUND=return] dns

  # go away and edit /etc/nsswitch.conf
  # change ordering of resolve and mdns4_minimal

  mtearle@liberation:/etc$ grep hosts /etc/nsswitch.conf 
  hosts:  files mdns4_minimal [NOTFOUND=return] resolve 
[!UNAVAIL=return] dns

  # check mdns lookups now work, and it now pings

  mtearle@liberation:/etc$ ping -c 1 bazzavan.local
  PING bazzavan.local (172.16.44.48) 56(84) bytes of data.
  64 bytes from 172.16.44.48 (172.16.44.48): icmp_seq=1 ttl=64 time=0.161 ms

  --- bazzavan.local ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.161/0.161/0.161/0.000 ms

  
  # check libnss-resolve is still doing its thing

  mtearle@liberation:/etc$ ping -c 1 localhost.localdomain
  PING localhost.localdomain(localhost (::1%1)) 56 data bytes
  64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.016 ms

  --- localhost.localdomain ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.016/0.016/0.016/0.000 ms

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

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

[Touch-packages] [Bug 1519499] Re: Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

2016-12-14 Thread Martin Pitt

This is likely fixed in current systemd versions already, but the recent
commit https://github.com/systemd/systemd/commit/ad2706db7cce should fix
the remaining traces of this.

Current systemd package in
https://launchpad.net/~pitti/+archive/ubuntu/systemd contains this
patch, if you want to give it a try on Ubuntu 16.10.

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

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

Title:
  Shutdown failure: Assertion 'sd_id128_randomize() >= 0' failed at
  ../src/core/dbus.c:657, function bus_on_connection(). Aborting.

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  This is a follow-up on this issue here:
  https://github.com/lxc/lxd/issues/1336 I cannot stop a LXD container
  gently and as it seems the issue lies within ubuntu/systemd which does
  not handle SIGPWR correctly.

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

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

[Touch-packages] [Bug 1649262] Re: Segmentation fault (core dumped) on 17.04

2016-12-14 Thread dinamic

#3 @osomon yep glxgears works fine

** Summary changed:

- Segmentation fault (core dumped) on 17.04
+ webbrowser app Segmentation fault (core dumped) on 17.04

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

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

Title:
  webbrowser app Segmentation fault (core dumped) on 17.04

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

Bug description:
  17.04 unity7

  ~$ webbrowser-app 
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  UCUriHandler: Empty "APP_ID" environment variable, ignoring.
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information
  could not open containers config file  
"/home/pixel/.local/share/libertine/ContainersConfig.json"
  APP_ID isn't set, the handler can not be registered
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
  Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
  Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" 
QFlags(0x2)
  Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
  Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

  (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not 
connect: Permission denied
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  APP_ID isn't set, the handler ignored
  qml: Loaded 13 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  ^CSegmentation fault (core dumped)

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

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

[Touch-packages] [Bug 1649077] Re: OSK appears blank in the lock screen

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

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

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

Title:
  OSK appears blank in the lock screen

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04

2016-12-14 Thread Rik Mills

I note that Jose has some apparently successful builds of 1.8.0-3 in the
following ppa

https://launchpad.net/~panfaust/+archive/ubuntu/kde-test-good

so I would like to enquire if the changes contained there are
acceptable, as if so can these be applied to the ubuntu archive package
to enable moving forward with applications that now require the new Qt
bindings to build.

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

Title:
  1.8.0-2 FTBFS in zesty 17.04

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all
  architectures from source with the error:

  checking whether a simple qt program can be built... no
  configure: error:
  ***
  *** Qt5 (Qt5Core) is required for Qt binding.
  ***

  The packages builds without this issue in debian unstable.

  A little experimentation shows that is a ubuntu sbuild/pbuilder and
  ppa, setting -pie in the hardening options allows the build to proceed
  with the Qt bindings building properly.

  Not being overly familiar with the hardening, I am unsure if dropping
  that feature set is relatively harmless, or massively undesirable and
  potentially harmful.

  However, in a ppa build, but NOT in my local sbuild/pbuilder chroot,
  the resulting build then hangs on the (python?) tests on starting or
  stopping gpg-agent, and the build is eventually killed due to
  inactivity after 150 mins as follows

  GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= 
top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" 
/usr/bin/python3 ./run-tests.py \
    --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=.  \
    initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py 
t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py 
t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py 
t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py 
t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py
  starting gpg-agent

  Session terminated, terminating shell...make[1]: *** wait: No child 
processes.  Stop.
  make[1]: *** Waiting for unfinished jobs
  make[1]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
   ...terminated.
  make: *** wait: No child processes.  Stop.
  make: *** Waiting for unfinished jobs
  make: *** wait: No child processes.  Stop.
  Makefile:457: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Terminated
  Makefile:602: recipe for target 'xcheck' failed
  make[4]: *** [xcheck] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

  I would note that this is the first gpgme version from gpg directly,
  with the Qt bindings built. These will be essential for future KDE
  applications and frameworks, as the gpgmepp previously built in KDE's
  own packages is being dropped.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions

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

[Touch-packages] [Bug 1649696] Re: /usr/include/mirclient/mir_toolkit/events/event.h:24:32: fatal error: mir_toolkit/common.h: No such file or directory

I've confirmed that a reinstall of libmircommon-dev, libmirclient-dev
and libmircore-dev seemed to have fixed it.  Not sure what was up with
that!

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

Title:
  /usr/include/mirclient/mir_toolkit/events/event.h:24:32: fatal error:
  mir_toolkit/common.h: No such file or directory

Status in Mir:
  Incomplete
Status in Mir 0.25 series:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete

Bug description:
  A header from libmirclient-dev has an include for a file that used to
  be in libmircommon-dev, which seems to have been removed in
  0.25.0+16.04.20161203-0ubuntu1

  libmircommon-dev=0.24.1+16.04.20160928-0ubuntu1 did have
  mir_toolkit/common.h

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

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

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

2016-12-14 Thread dwmw2

This is actually a NetworkManager bug. As noted in bug 1648905 it's
fixed upstream by
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2=bb45adeda0bf427ada23b09daf970b0757e82d60

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

** Bug watch added: Red Hat Bugzilla #1332491
   https://bugzilla.redhat.com/show_bug.cgi?id=1332491

** Also affects: fedora via
   https://bugzilla.redhat.com/show_bug.cgi?id=1332491
   Importance: Unknown
   Status: Unknown

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openconnect package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

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

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

[Touch-packages] [Bug 1609700] Re: username is not saved in openconnect connection dialog

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

Title:
  username is not saved in openconnect connection dialog

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openconnect package in Ubuntu:
  Confirmed
Status in Fedora:
  Unknown

Bug description:
  
  Hi,

  I clicked on "save passwords" but only the password is filled in
  automatically when I open the connection dialog. The "Username" field
  is empty!

  This happens for a SSLVPN configuration.

  For another VPN config (don't know which type) everything is ok.

  
  openconnect: 7.06-2build2

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

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

[Touch-packages] [Bug 1649077] Re: OSK appears blank in the lock screen

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

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

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

Title:
  OSK appears blank in the lock screen

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1649077] Re: OSK appears blank in the lock screen

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

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

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

Title:
  OSK appears blank in the lock screen

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 1649077] Re: OSK appears blank in the lock screen

2016-12-14 Thread Nekhelesh Ramananthan

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

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

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

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

** Description changed:

  After using OTA-14 a while, the OSK starts to exhibit a strange
- behaviour. It appears blank after a while in the lock screen. You can
- still press randomly which then makes the OSK to appear fully. When you
- press a character again it starts to flicker.
+ behaviour.
+ 
+ 1. It appears blank after a while in the lock screen. You can still
+ press randomly which then makes the OSK to appear fully. When you press
+ a character again it starts to flicker.
+ 
+ 2. OSK starts to flicker similar to bug #1590765 which was fixed in
+ OTA-12. It seems to have resurfaced in OTA-14.
+ 
+ Systems Info:
+ OTA-14 Stable Channel
+ Devices: E4.5, E5

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

Title:
  OSK appears blank in the lock screen

Status in Canonical System Image:
  New
Status in Mir:
  New
Status in mir package in Ubuntu:
  Confirmed
Status in ubuntu-keyboard package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  After using OTA-14 a while, the OSK starts to exhibit a strange
  behaviour.

  1. It appears blank after a while in the lock screen. You can still
  press randomly which then makes the OSK to appear fully. When you
  press a character again it starts to flicker.

  2. OSK starts to flicker similar to bug #1590765 which was fixed in
  OTA-12. It seems to have resurfaced in OTA-14.

  Systems Info:
  OTA-14 Stable Channel
  Devices: E4.5, E5

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

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

[Touch-packages] [Bug 441502] Re: Front Audio Jacks Not Working

2016-12-14 Thread bhikkhu subhuti

My computer has a realtek ALC255 according to hdaJackRetask  but lscipi
command shows only Intel.  The windows version has realtek drivers.  I
am not sure if that is the problem.  I have seemed to have read that
there are sub sound systems and sometimes it does not choose them.

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

Title:
  Front Audio Jacks Not Working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu karmic (development branch)
  Release:  9.10
  alsa-base:
Installed: 1.0.20+dfsg-1ubuntu4

  What is expected?

  I should plug in my headset (microphone included) and be able to hear
  and talk through any software, or at least restart such software if it
  does not automagically detect and adjust immediately so it may use the
  new configuration.

  What happened instead?

  The front jacks do not seem to be working. They did in ubuntu 9.04
  (and only the ubuntu flavour, they did not in kubuntu 9.04) but not
  there's no output.

  Microphone works with configuration!

  * The microphone is still configured in the same manner. I open `alsamixer`.
  * In the [Playback] View which opens by default I adjust certain settings to:
 "Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I".
 "Front Mic Jack Mode" TO "Mic In"
  * In the [Capture] View:
 "Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing)
 "Capture" is ENABLED and volume adjusted (Maxed out for testing)

  Any other option is discardable in the front microphone jack configuration.
 
  This makes the microphone work when it is plugged in the front jack. I have 
not tested the back panel.

  Headphone

  I have not been able to configure the headphones yet, I'm not an alsa
  or pulse-audio expert ;[

  LSPCI important output:

  00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
  Audio Controller

  Notes:

  No alsa global configuration was tampered with. Only alsamixer for
  microphone configuration.

  ProblemType: Bug
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  exodus 1440 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22'
 Mixer name : 'IDT 92HD73E1X5'
 Components : 'HDA:111d7676,80865002,00100202'
 Controls  : 47
 Simple ctrls  : 29
  CheckboxCommand: alsa_record_playback
  CheckboxTest: alsa_record_playback_alternates
  Date: Sat Oct  3 11:23:19 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu4
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-11-generic i686

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

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

[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair

2016-12-14 Thread Egbert van der Wal

I just gave up and got me a Asus Xonar sound card and disabled the
onboard. Works a treat!

The longer I worked with it, the more I got convinced it's a crappy
chip. Even in Windows 10 it doesn't work properly - sometimes the volume
levels are ignored or attached to different outputs than they should be.

Also, when I started Ubuntu 16.04 once, I needed to completely shut down
the computer - if I just reboot to Windows it will also not work in
Windows. After a shut down it usually works again.

I have no clue what this chip is doing and how it's interacting with the
driver on Linux, but it's bad. Very bad.

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

Title:
  Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken
  Beyond All Repair

Status in ALSA driver:
  Unknown
Status in Skylinux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  [WORKAROUND] Run the following command:

  echo "options snd-hda-intel position_fix=1" | sudo tee -a
  /etc/modprobe.d/alsa-base.conf

  [EDIT]
  Workaround doesn't work anymore for me at least. I assume it only has a small 
possibility of working due to a firmware bug.

  [ORIGINAL REPORT]
  No sound, no jacks; It is detected by Linux however.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
  Uname: Linux 3.8.0-16-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Mon Apr  8 18:56:44 2013
  InstallationDate: Installed on 2013-04-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed
  Symptom_Card: HDA Creative - HDA Creative
  Symptom_Type: No sound at all
  Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1102
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

[Touch-packages] [Bug 441502] Re: Front Audio Jacks Not Working

2016-12-14 Thread bhikkhu subhuti

I loaded the 4.9 upstream and 1.15 BIOS from ACER.  Bug still exists.. Please 
let me know what to do next.  My internal microphone has static and I want to 
use a headset and then eventually a plug splitter of microphone and headphone.  
The headphones work.
The microphone does not work
Both work fine in windows (sorry).
I have pauvolume control and it does not list a secondary input device.
I tried hdajackretask and it also did not seem to work.

According to what I know.. The internal microphone should be muted and the 
external should work..
That happens to the headphones and speakers respectively when you plug it in.

Please advise.  Maybe you can help me figure out the "advanced settings"
for hdajackretask and then it can go into the builds for the next rc.

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

Title:
  Front Audio Jacks Not Working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu karmic (development branch)
  Release:  9.10
  alsa-base:
Installed: 1.0.20+dfsg-1ubuntu4

  What is expected?

  I should plug in my headset (microphone included) and be able to hear
  and talk through any software, or at least restart such software if it
  does not automagically detect and adjust immediately so it may use the
  new configuration.

  What happened instead?

  The front jacks do not seem to be working. They did in ubuntu 9.04
  (and only the ubuntu flavour, they did not in kubuntu 9.04) but not
  there's no output.

  Microphone works with configuration!

  * The microphone is still configured in the same manner. I open `alsamixer`.
  * In the [Playback] View which opens by default I adjust certain settings to:
 "Digital Input Source" (NOT "Digital Input Source 1") TO "Analog I".
 "Front Mic Jack Mode" TO "Mic In"
  * In the [Capture] View:
 "Front Mic Mixer" is ENABLED and volume adjusted (Maxed out for testing)
 "Capture" is ENABLED and volume adjusted (Maxed out for testing)

  Any other option is discardable in the front microphone jack configuration.
 
  This makes the microphone work when it is plugged in the front jack. I have 
not tested the back panel.

  Headphone

  I have not been able to configure the headphones yet, I'm not an alsa
  or pulse-audio expert ;[

  LSPCI important output:

  00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD
  Audio Controller

  Notes:

  No alsa global configuration was tampered with. Only alsamixer for
  microphone configuration.

  ProblemType: Bug
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 2/2
 Subdevice #0: subdevice #0
 Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  exodus 1440 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd322 irq 22'
 Mixer name : 'IDT 92HD73E1X5'
 Components : 'HDA:111d7676,80865002,00100202'
 Controls  : 47
 Simple ctrls  : 29
  CheckboxCommand: alsa_record_playback
  CheckboxTest: alsa_record_playback_alternates
  Date: Sat Oct  3 11:23:19 2009
  DistroRelease: Ubuntu 9.10
  NonfreeKernelModules: nvidia
  Package: alsa-base 1.0.20+dfsg-1ubuntu4
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
  SourcePackage: alsa-driver
  Tags: checkbox-bug
  Uname: Linux 2.6.31-11-generic i686

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

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

[Touch-packages] [Bug 1649875] [NEW] OSK does not pop up in new window

2016-12-14 Thread Victor gonzalez

Public bug reported:

Story: looks like new window and private window opens correctly but OSK
doesn't pop up when tapping over address bar, I can make it work by
swiping to the main webbrowser page where OSK works fine.

Environment:

current build number: 101
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-12-14 09:38:52
version version: 101
version ubuntu: 20161214
version device: 20161014.0
version custom: 20161214

Steps:

1º Open webbrowser-app
2º On the right side menu button select "New window"
3º Tap over the address field in the new window(notice OSK does not pop up)
4º On right side menu select "New private mode"
5º Tap over the address field in new private window (notice OSK does not pop up)
6º Swipe to the main window and tab, check that OSK pops up

Current result: when tapping over the address bar in a new window or
private window, OSK does not appear

Expected result: OSK should always appear when tapping on address bar or
search fields like in the main page of webbrowser

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

** Description changed:

- Story: looks like first time a new window opens OSK doesn't pop up when
- tapping over address bar, I can make it work by swiping to the main
- webbrowser page where OSK works fine.
+ Story: looks like new window and private window opens correctly but OSK
+ doesn't pop up when tapping over address bar, I can make it work by
+ swiping to the main webbrowser page where OSK works fine.
  
  Environment:
  
  current build number: 101
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-14 09:38:52
  version version: 101
  version ubuntu: 20161214
  version device: 20161014.0
  version custom: 20161214
  
  Steps:
  
  1º Open webbrowser-app
  2º On the right side menu button select "New window"
  3º Tap over the address field in the new window(notice OSK does not pop up)
  4º On right side menu select "New private mode"
  5º Tap over the address field in new private window (notice OSK does not pop 
up)
  6º Swipe to the main window and tab, check that OSK pops up
  
  Current result: when tapping over the address bar in a new window or
  private window, OSK does not appear
  
  Expected result: OSK should always appear when tapping on address bar or
  search fields like in the main page of webbrowser

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

Title:
  OSK does not pop up in new window

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Story: looks like new window and private window opens correctly but
  OSK doesn't pop up when tapping over address bar, I can make it work
  by swiping to the main webbrowser page where OSK works fine.

  Environment:

  current build number: 101
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2016-12-14 09:38:52
  version version: 101
  version ubuntu: 20161214
  version device: 20161014.0
  version custom: 20161214

  Steps:

  1º Open webbrowser-app
  2º On the right side menu button select "New window"
  3º Tap over the address field in the new window(notice OSK does not pop up)
  4º On right side menu select "New private mode"
  5º Tap over the address field in new private window (notice OSK does not pop 
up)
  6º Swipe to the main window and tab, check that OSK pops up

  Current result: when tapping over the address bar in a new window or
  private window, OSK does not appear

  Expected result: OSK should always appear when tapping on address bar
  or search fields like in the main page of webbrowser

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

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

[Touch-packages] [Bug 1648905] Re: VPN username and settings not saved

2016-12-14 Thread dwmw2

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

Actually, this is probably a duplicate of bug 1609700

** This bug has been marked a duplicate of bug 1609700
   username is not saved in openconnect connection dialog

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

Title:
  VPN username and settings not saved

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  The OpenConnect VPN auth-dialog doesn't remember usernames and other
  settings.

  See discussion (and fix) in
  https://bugzilla.redhat.com/show_bug.cgi?id=1332491

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

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

[Touch-packages] [Bug 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

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

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

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

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  --

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  Date: Sun Nov 27 21:29:34 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-09-03 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago)

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

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

[Touch-packages] [Bug 1399129] Re: A system icon of iBus is not displayed in Kubuntu Plasma 5

2016-12-14 Thread Aron Xu

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

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

Title:
  A system icon of iBus is not displayed in Kubuntu Plasma 5

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  In Kubuntu 14.10 Plasma 5, a system icon of iBus is not displayed.
  I installed Kubuntu 14.10 Plasma 5 in Japanese (日本語).
  Because iBus-Anthy is installed then,
  I change it to Anthy in Super+Space and can perform Japanese input again.
  but systray does not have an icon, and a big problem occurs in operability.

  This problem is one of the side effects of systray of Plasma 5 having changed 
the specifications:
  https://community.kde.org/Plasma/5.0_Errata
  http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/

  As for this problem, bug report is performed in iBus:
  https://code.google.com/p/ibus/issues/detail?id=1749

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

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

[Touch-packages] [Bug 1649729] Re: ntpd startup failures under xenial

2016-12-14 Thread Joshua Powers

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Do you want NTP to listen on all addresses? That is not typically what
someone will want. That is why there is the -I option (e.g. -I
127.0.0.1) that can be added to the command line in /etc/default/ntp to
listen on a specific port or address.

Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as Incomplete. We'd be grateful if you would then provide a
more complete description of the problem, explain why you believe this
is a bug in Ubuntu rather than a problem specific to your system, and
then change the bug status back to New.

If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community

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

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

Title:
  ntpd startup failures under xenial

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  I have a system running 16.04.1 with multiple interfaces configured
  via /etc/network/interfaces.  Following a restart, ntpd will often be
  found not running, despite being installed and configured.

  syslog suggests ntpd is being repeatedly stopped and restarted within
  seconds.

  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING

  My current assumption is that this is the work of /etc/network/if-
  up.d/ntpdate being run on several interfaces nearly simultaneously.
  The rapid stop/start cycle of the daemon appears to trip up the port
  binding, and eventually cause ntpd to become unhappy and wind up
  stopped.

  Manually restarting ntpd (or even running /etc/network/if-
  up.d/ntpdate) outside of interface up/down time properly brings up
  ntpd.  It doesn't appear to be a configuration issue as such.

  Further, running  /etc/network/if-up.d/ntpdate from bash several times
  in rapid succession also produces the 'missing ntpd' behavior, outside
  of the context of any interface activity.

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

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

[Touch-packages] [Bug 1649729] Re: ntpd startup failures under xenial

2016-12-14 Thread Joshua Powers

My information may be out of date, instead of using -I you may also try
adding the following:

interface ignore wildcard
interface listen 127.0.0.1
interface listen ::1

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

Title:
  ntpd startup failures under xenial

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  I have a system running 16.04.1 with multiple interfaces configured
  via /etc/network/interfaces.  Following a restart, ntpd will often be
  found not running, despite being installed and configured.

  syslog suggests ntpd is being repeatedly stopped and restarted within
  seconds.

  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23)
  Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4119]:  * Stopping NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntp[4183]:  * Starting NTP server ntpd
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct  5 12:34:45 
UTC 2016 (1): Starting
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -g -u 106:113
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24)
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING
  Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - 
another process may be running - EXITING

  My current assumption is that this is the work of /etc/network/if-
  up.d/ntpdate being run on several interfaces nearly simultaneously.
  The rapid stop/start cycle of the daemon appears to trip up the port
  binding, and eventually cause ntpd to become unhappy and wind up
  stopped.

  Manually restarting ntpd (or even running /etc/network/if-
  up.d/ntpdate) outside of interface up/down time properly brings up
  ntpd.  It doesn't appear to be a configuration issue as such.

  Further, running  /etc/network/if-up.d/ntpdate from bash several times
  in rapid succession also produces the 'missing ntpd' behavior, outside
  of the context of any interface activity.

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

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

[Touch-packages] [Bug 1647830] Re: no wifi choices supplied in wizard on unity8-snap on classic

** Branch linked: lp:~pete-woods/indicator-network/fix-uss-wifi-
settings-lp1647830

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

Title:
  no wifi choices supplied in wizard on unity8-snap on classic

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  in a recent unity8-snap on classic install, i was made to run through
  the wizard. i found that when arriving at the wifi page, there were no
  wifi networks provided just a blank white screen. Altho, when
  proceeding, the wifi indicator did show i was connected.

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

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

[Touch-packages] [Bug 1648965] Re: grafica

2016-12-14 Thread Paul White

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Please also change the title of the bug to something more meaningful.

Perhaps you could upload a screenshot that shows us the problem?

Thanks!

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

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

Title:
  grafica

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  grafica

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Dec 10 13:11:10 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a]
   Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] 
[1002:6840] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2015-07-20 (509 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 184A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd02/21/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn184A:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Dec 10 12:54:03 2016
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

I confirm that
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38
introduced the regression: serialized navigation entries are pickled one
after the other, and the size of the resulting data is not stored
anywhere. As a result, the new implementation of
SerializedNavigationEntry::ReadFromPickle() starts reading from the
beginning of the next entry looking for extended info.

It is unfortunate that navigation entries are serialized this way. To
prevent this from happening again in the future when additional data is
added to serialized navigation entries, we should pickle them
separately, and for each entry store the size followed by the raw data.

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

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

** Changed in: oxide
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: oxide
Milestone: None => branch-1.20

** Also affects: oxide/1.19
   Importance: Undecided
   Status: New

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

** Changed in: oxide/1.19
   Importance: Undecided => Critical

** Changed in: oxide/1.19
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: oxide/1.19
   Status: New => Confirmed

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

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  Confirmed
Status in Oxide 1.19 series:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

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

[Touch-packages] [Bug 1649096] Re: SYSTEM DLUGO SIE URUCHAMIA

2016-12-14 Thread Paul White

Using translate.google.com to translate:
>SYSTEM DLUGO SIE URUCHAMIA
>CZARNY EKRAN PRZY ROZRUCHU
gives me:
SYSTEM LONG CAN SIE
BLACK SCREEN AT THE START

Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem,
preferably in English..

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).

Please also change the bug title to something more meaningful.

Thanks!

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

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

Title:
  SYSTEM DLUGO SIE URUCHAMIA

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  CZARNY EKRAN PRZY ROZRUCHU

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30
  Uname: Linux 4.4.0-53-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Dec 11 15:40:28 2016
  DistUpgraded: 2016-12-09 09:02:47,236 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.59, 3.13.0-105-generic, x86_64: installed
   ndiswrapper, 1.59, 4.4.0-53-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS600M [Radeon Xpress 1250] 
[1002:7942] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd RS600M [Radeon Xpress 1250] 
[144d:c034]
  InstallationDate: Installed on 2016-12-09 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. R59P/R60P/R61P
  ProcEnviron:
   LANGUAGE=pl_PL
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic 
root=UUID=75dda18b-b31f-4dbd-90e9-be3864009852 ro splash quiet vesafb.invalid=1 
plymouth:debug=1=1=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-12-09 (2 days ago)
  dmi.bios.date: 03/05/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 07YI
  dmi.board.name: R59P/R60P/R61P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr07YI:bd03/05/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR59P/R60P/R61P:pvr07YI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR59P/R60P/R61P:rvr:cvnSAMSUNGELECTRONICSCO.,LTD.:ct1:cvrN/A:
  dmi.product.name: R59P/R60P/R61P
  dmi.product.version: 07YI
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Dec 11 14:32:15 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1647830] Re: no wifi choices supplied in wizard on unity8-snap on classic

2016-12-14 Thread Lukáš Tinkl

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

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

Title:
  no wifi choices supplied in wizard on unity8-snap on classic

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  in a recent unity8-snap on classic install, i was made to run through
  the wizard. i found that when arriving at the wifi page, there were no
  wifi networks provided just a blank white screen. Altho, when
  proceeding, the wifi indicator did show i was connected.

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

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

[Touch-packages] [Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses

2016-12-14 Thread LaMont Jones

** Description changed:

  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164
  
  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)
  
  Bugs related to uploads for this specific SRU:
  
  cloud-init:
  bug 1460715: different fix unrelated to this SRU
  bug 1639930: ip6= on kernel command line
  bug 1642679: different fix unrelated to this SRU
  bug 1644043: different fix unrelated to this SRU
  
  ifupdown:
  bug 1629972: networking.service takes down lo on stop
  
  initramfs-tools:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1628306: regression-update (failure when ip="")
  bug 1631474: regression-update (failure when ip=:eth0:dhcp)
  
  isc-dhcp:
  bug 1621507: no IPv6 DHCP support in early boot
  bug 1633479: dhclient does not wait for IPv6 DAD
  
  open-iscsi:
  bug 1621507: no IPv6 DHCP support in early boot
  
  [Impact]
  
  It is not possible to netboot Ubuntu with a network-based root
  filesystem in an ipv6-only environment.  Anyone wanting to netboot in an
  ipv6-only environment is affected.
  
  [Stable Fix]
  
  These uploads add "ip6=" to the command line syntax to configure ipv6
  using the defacto isc-dhcp-client.  IPv4 configuration (and "ip="
  syntax) remain unchanged.
  
  Valid format for the ip6= command line option is:
     ip6=none (or ip6=off or ip6=) -- do not configure ipv6
     ip6=DEVICE  -- run IPv6 dhclient on device DEVICE.
  
  [Test Case]
  
  See Bug 1229458.  Configure radvd, dhcpd, and tftpd for your ipv6-only
  netbooting world.  Pass the boot process an ipv6 address to talk to, and
  see it fail to configure the network.
  
  [Regression Potential]
  
  1) This increases the uncompressed initramfs size by approximately 500KB, 
since isc-dhcp-client is added, but klibc is still needed for some other 
things, and is therefore present.  On systems with a very small /boot 
partition, this could result in failure to upgrade the initramfs.
  2) In at least some cases, DHCP network configuration shifts from klibc's 
ipconfig to isc-dhcp-client's dhclient.  This should be of minimal risk, as 
isc-dhcp-client is in very very widespread use.  In the event of a regression, 
network boot would fail, but the prior kernel should still be bootable.
  
  [Tests for verification]
  
  Whoever checks the last one off, please mark verification done.
  
  MAAS test cases:
- [ ] MAAS on IPv6-only network
- [ ] MAAS on IPv4-only network
+ [+] MAAS on IPv6-only network
+ [+] MAAS on IPv4-only network
  [ ] MAAS booting IPv4 on dual-stack network
  [ ] MAAS booting IPv6 on dual-stack network
  
  Non-MAAS test cases:
  [ ] d-i install with iSCSI remote root should complete normally
  [ ] Validate normal boot without remote root
  [ ] Booting an iSCSI remote root via IPv4 (using ip=)
  [ ] Booting an iSCSI remote root via IPv6 (using ip6=)
  [ ] Booting an iSCSI remote root via IPv4 (no ip=, d-i use case)
  [ ] Booting an iSCSI remote root via IPv6 (no ip6=, d-i use case)
  [ ] Booting an iSCSI remote root with BOOTIF specified (BOOTIF=mac of booting 
device)
  [ ] Booting an iSCSI remote root on mixed network with no options (IPv4 
should be used only)
  [ ] jderose's use cases

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

Title:
  initramfs-tools configure_networking() fails to dhcp ipv6 addresses

Status in MAAS:
  Fix Committed
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Won't Fix
Status in open-iscsi package in Ubuntu:
  In Progress
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in isc-dhcp source package in Xenial:
  Fix Committed
Status in klibc source package in Xenial:
  Won't Fix
Status in open-iscsi source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Yakkety:
  Fix Committed
Status in isc-dhcp source package in Yakkety:
  Fix Committed
Status in klibc source package in Yakkety:
  Won't Fix
Status in open-iscsi source package in Yakkety:
  Fix Released
Status in klibc package in Debian:
  New

Bug description:
  initramfs' configure_networking function uses ipconfig to configure the 
network.
  ipconfig does not support dhcpv6.  See: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164

  Related bugs:
    * bug 1229458: grub2 needed changes
    * bug 1621615: network not configured when ipv6 netbooted into cloud-init
    * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6)

  Bugs related to uploads for this specific SRU:

  cloud-init:
  bug 1460715:

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Description changed:

+ Hi,
+
+ Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
+ package shipping currently in the development version of Ubuntu zesty.
+ You will find the corresponding debdiff attached to this bug thread.
+
+ Can a sponsor please review the debdiff?
+
+ Thanks in advance.
+
+ Francesco
+
+ =
+ Original description:
+
See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
Source code below.

What I expect to happen is that the GtkPlug has the same size as the
GtkSocket.
What actually happens is that GtkPlug only covers a quarter of the area of
the GtkSocket.

Impact: Onboard on HiDPI displays is near unusable at login and lock
screen, aka unity-greeter and gnome-screensaver. Original bug report
here: https://bugs.launchpad.net/bugs/1562734.

Steps to reproduce:
- build plug and socket samples from below
- set display scaling factor to 2
- System Settings -> Display -> Scale for menu and title bars = 2
+ System Settings -> Display -> Scale for menu and title bars = 2
- run ./socket $(head -1 <(./plug))
-> blue GtkPlug is too small, it should cover all the black

- resize the window
-> at smaller sizes the scaling suddenly corrects itself, at larger ones it's
wrong again

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgtk-3-0 3.18.9-1ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 20 01:48:50 2016
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Patch added: "gtk+3.0_3.22.5-1ubuntu2.debdiff"

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791611/+files/gtk+3.0_3.22.5-1ubuntu2.debdiff

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

Title:
GtkPlug scaled to half the expected size on HiDPI screens + zesty
debdiff

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

Bug description:
Hi,

Marmuta performed tests with org.gnome.desktop.interface scaling-
factor = 2 , where few issues are left for Onboard on hidpi screens,
that are not related to gtk, but rather to unity-greeter or gnome-
screensaver. He did not notice any issue with scaling-factor = 1.

Can a sponsor please review the debdiff?

Thanks in advance.

Francesco

=
Original description:

See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
Source code below.

What I expect to happen is that the GtkPlug has the same size as the
GtkSocket.
What actually happens is that GtkPlug only covers a quarter of the area of
the GtkSocket.

Impact: Onboard on HiDPI displays is near unusable at login and lock
screen, aka unity-greeter and gnome-screensaver. Original bug report
here: https://bugs.launchpad.net/bugs/1562734.

Steps to reproduce:
- build plug and socket samples from below
- set display scaling factor to 2
System Settings -> Display -> Scale for menu and title bars = 2
- run ./socket $(head -1 <(./plug))
-> blue GtkPlug is too small, it should cover all the black

- resize the window
-> at smaller sizes the scaling suddenly corrects itself, at larger ones it's
wrong again

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

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

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5.orig.tar.xz"

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791619/+files/gtk+3.0_3.22.5.orig.tar.xz

** Description changed:

Hi,

Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
package shipping currently in the development version of Ubuntu zesty.
You will find the corresponding debdiff attached to this bug thread.
+
+ Marmuta performed tests with org.gnome.desktop.interface scaling-factor
+ = 2 , where few issues are left for Onboard on hidpi screens, that are
+ not related to gtk, but rather to unity-greeter or gnome-screensaver. He
+ did not notice any issue with scaling-factor = 1.

Can a sponsor please review the debdiff?

Thanks in advance.

Francesco

=
- Original description:
+ Original description:

See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
Source code below.

What I expect to happen is that the GtkPlug has the same size as the
GtkSocket.
What actually happens is that GtkPlug only covers a quarter of the area of
the GtkSocket.

Impact: Onboard on HiDPI displays is near unusable at login and lock
screen, aka unity-greeter and gnome-screensaver. Original bug report
here: https://bugs.launchpad.net/bugs/1562734.

- resize the window
-> at smaller sizes the scaling suddenly corrects itself, at larger ones it's
wrong again

** Summary changed:

- GtkPlug scaled to half the expected size on HiDPI screens
+ GtkPlug scaled to half the expected size on HiDPI screens + zesty debdiff

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

Title:
GtkPlug scaled to half the expected size on HiDPI screens + zesty
debdiff

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

Bug description:
Hi,

Can a sponsor please review the debdiff?

Thanks in advance.

Francesco

=
Original description:

See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
Source code below.

What I expect to happen is that the GtkPlug has the same size as the
GtkSocket.
What actually happens is that GtkPlug only covers a quarter of the area of
the GtkSocket.

Impact: Onboard on HiDPI displays is near unusable at login and lock
screen, aka unity-greeter and gnome-screensaver. Original bug report
here: https://bugs.launchpad.net/bugs/1562734.

- resize the window
-> at smaller sizes the scaling suddenly corrects itself, at larger ones it's
wrong again

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

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

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5-1ubuntu2.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791614/+files/gtk+3.0_3.22.5-1ubuntu2.dsc

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

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

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-12-14 Thread Ryan Harper

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

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  New

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient to drop systemd-networkd's 
After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and 
(for

[Touch-packages] [Bug 1649932] Re: crashes when opening from the peer picker on unity8 desktop

** Attachment added: "_usr_bin_camera-app.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1649932/+attachment/4791620/+files/_usr_bin_camera-app.1000.crash

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

Title:
  crashes when opening from the peer picker on unity8 desktop

Status in camera-app package in Ubuntu:
  New

Bug description:
  If camera-app is already running when selected in the peer picker, it
  switches to picking mode just fine.  However if camera-app is not
  running, it crashes on startup when selected from the peer picker.

  In order to get camera-app to show up in the peer picker, you need a
  deb built from my branch[1] and run the hook[2] manually once after
  installing the deb.

  1. 
https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232
  2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook

  upstart log:

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
  Camera app directory "/usr/share/camera-app/"
  qq= QDeclarativeCamera_QML_37(0x224) 0x248c610
  Focus mode selection is not supported
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  QFileSystemWatcher::removePaths: list is empty
  DelegateModel::item: index out range 0 0

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

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

[Touch-packages] [Bug 1649931] [NEW] systemd-networkd needs to ensure DNS is up before network-online.target

2016-12-14 Thread Ryan Harper

Public bug reported:

Currently resolvconf and systemd-networkd don't ensure DNS has been
configured before allowing network-online.target to be reached.

This was discussed in https://launchpad.net/bugs/1636912 however it was
not a regression since there aren't any users of networkd + DNS early in
boot at this time, it was requested that we move this DNS issue to a
separate bug.

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

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

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

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

Title:
  systemd-networkd needs to ensure DNS is up before network-
  online.target

Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently resolvconf and systemd-networkd don't ensure DNS has been
  configured before allowing network-online.target to be reached.

  This was discussed in https://launchpad.net/bugs/1636912 however it
  was not a regression since there aren't any users of networkd + DNS
  early in boot at this time, it was requested that we move this DNS
  issue to a separate bug.

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

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

[Touch-packages] [Bug 1641243] Re: Provide full AppArmor confinement for snaps on 14.04

2016-12-14 Thread Tyler Hicks

** Description changed:

  = apparmor SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper AppArmor 
confinement for snaps when running under the 16.04 hardware enablement kernel. 
The apparmor userspace package in 14.04 is missing support key mediation 
features such as UNIX domain socket rules, AppArmor policy namespaces, and 
AppArmor profile stacking. UNIX domain socket mediation is needed by nearly all 
snaps. AppArmor policy namespaces and profile stacking are needed by the lxd 
snap.
  
  Unfortunately, it was not feasible to backport the individual features
  to the 14.04 apparmor package as they're quite complex and have a large
  number of dependency patches. Additionally, the AppArmor policy
  abstractions from Ubuntu 16.04 are needed to provide proper snap
  confinement. Because of these two reasons, the decision to bring 16.04's
  apparmor package to 14.04 was (very carefully) made.
  
  [Test Case]
  
    https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor
  
  This update will go through the Test Plan as well as manual testing to
  verify that snap confinement on 14.04 does work. Manual tests include
  installing snapd in 14.04 and running simple snaps such as pwgen-tyhicks
  and hello-world, as well as a much more complex snap such as lxd.
  
  The following regression tests from lp:qa-regression-testing (these
  packages ship an AppArmor profile) can be used to verify that their
  respective packages do not regress:
  
   test-apache2-mpm-event.py
   test-apache2-mpm-itk.py
   test-apache2-mpm-perchild.py
   test-apache2-mpm-prefork.py
   test-apache2-mpm-worker.py
   test-bind9.py
   test-clamav.py
   test-cups.py
   test-dhcp.py
   test-mysql.py
   test-ntp.py
   test-openldap.py
   test-rsyslog.py
   test-squid.py
   test-strongswan.py
   test-tcpdump.py
  
- I have a branch of lp:qa-regression-testing (unmerged, currently at
- https://code.launchpad.net/~tyhicks/+git/qa-regression-testing/+ref
- /apparmor-trusty-sru) that pulls in the parser and regression tests from
- the apparmor 2.8.95~2430-0ubuntu5.3 package currently shipping in
- Trusty, in addition to the tests in the 2.10.95 based package.
+ I have pushed changes to lp:qa-regression-testing which pulls in the
+ parser and regression tests from the apparmor 2.8.95~2430-0ubuntu5.3
+ package currently shipping in Trusty, in addition to the tests in the
+ 2.10.95 based package.
  
  Additionally, manually testing evince, which is confined by an AppArmor
  profile, should be done. The manual test should check basic
  functionality as well as for proper confinement (`ps auxZ` output).
  
  [Regression Potential]
  High. We must be extremely careful to not regress existing, confined 
applications in Ubuntu 14.04. We are lucky that the upstream AppArmor project 
has extensive regression tests and that the Ubuntu Security team adds even more 
testing via the AppArmor Test Plan.
  
  Care was taken to minimally change how the AppArmor policies are loaded
  during the boot process. I also verified that the abstractions shipped
  in apparmor and the profiles shipped in apparmor-profiles are the same
  across this SRU update.
  
  = dbus SRU =
  [Rationale]
  For backporting snapd to 14.04 LTS, we need to provide proper D-Bus mediation 
for snaps when running under the 16.04 hardware enablement kernel. The dbus 
package in 14.04 is missing support for blocking unrequested reply messages. 
This functionality was added to the D-Bus AppArmor mediation patches after 
14.04 was released but before the patches were merged upstream in dbus. The 
idea is to prevent a malicious snap from attacking another snap, over D-Bus, 
with unrequested reply messages and also to prevent two connections from 
subverting the snap confinement by communicating via unrequested reply messages.
  
  [Test Case]
  
  The upstream AppArmor userspace project has thorough tests for D-Bus
  mediation, including unrequested replies. Its
  tests/regression/apparmor/dbus_*.sh tests should be ran before and after
  updating to the dbus SRU. Before updating, the dbus_unrequested_reply.sh
  should fail and should pass after updating.
  
  To run the dbus_*.sh tests:
  
  $ sudo apt-get install -y bzr libdbus-1-dev
  $ bzr branch lp:apparmor # apt-get source apparmor to test the current 
apparmor
  $ cd apparmor/tests/regression/apparmor/
  $ make USE_SYSTEM=1 \
-   dbus_{eavesdrop,message,service,unrequested_reply} uservars.inc
+   dbus_{eavesdrop,message,service,unrequested_reply} uservars.inc
  $ for t in dbus_{eavesdrop,message,service,unrequested_reply}.sh; \
-   do sudo VERBOSE=1 bash $t || break; done
+   do sudo VERBOSE=1 bash $t || break; done
  
  The exit code should be 0 and all output lines should start with "ok:".
  
  In addition, the test-dbus.py tests from lp:qa-regression-testing should
  be ran to verify basic D-Bus functionality.
  
  This update will go through the Test Plan as well as manual testing to
  verify that snap

[Touch-packages] [Bug 1649932] [NEW] crashes when opening from the peer picker on unity8 desktop

Public bug reported:

If camera-app is already running when selected in the peer picker, it
switches to picking mode just fine.  However if camera-app is not
running, it crashes on startup when selected from the peer picker.

In order to get camera-app to show up in the peer picker, you need a deb
built from my branch[1] and run the hook[2] manually once after
installing the deb.

1. 
https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232
2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook

upstart log:

Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
Camera app directory "/usr/share/camera-app/"
qq= QDeclarativeCamera_QML_37(0x224) 0x248c610
Focus mode selection is not supported
No media control support for org.qt-project.qt.cameraflashcontrol/5.0
No flash control support
No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
No exposure control support
No media control support for org.qt-project.qt.cameraflashcontrol/5.0
No flash control support
No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
No exposure control support
QFileSystemWatcher::removePaths: list is empty
DelegateModel::item: index out range 0 0

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

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

Title:
  crashes when opening from the peer picker on unity8 desktop

Status in camera-app package in Ubuntu:
  New

Bug description:
  If camera-app is already running when selected in the peer picker, it
  switches to picking mode just fine.  However if camera-app is not
  running, it crashes on startup when selected from the peer picker.

  In order to get camera-app to show up in the peer picker, you need a
  deb built from my branch[1] and run the hook[2] manually once after
  installing the deb.

  1. 
https://code.launchpad.net/~ken-vandine/camera-app/content-hub_and_add-profile/+merge/313232
  2. /usr/lib/x86_64-linux-gnu/content-hub/content-hub-peer-hook

  upstart log:

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  Import path added "/usr/lib/x86_64-linux-gnu/camera-app"
  Camera app directory "/usr/share/camera-app/"
  qq= QDeclarativeCamera_QML_37(0x224) 0x248c610
  Focus mode selection is not supported
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  No media control support for org.qt-project.qt.cameraflashcontrol/5.0
  No flash control support
  No media control support for org.qt-project.qt.cameraexposurecontrol/5.0
  No exposure control support
  QFileSystemWatcher::removePaths: list is empty
  DelegateModel::item: index out range 0 0

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

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

[Touch-packages] [Bug 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)

2016-12-14 Thread Ryan Harper

I've opened a new bug for the DNS networkd/resolvconf issue:

https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1649931

We'll track a new SRU for fixing that issue separately.

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

Title:
  systemd-networkd runs too late for cloud-init.service (net)

Status in systemd:
  Fix Released
Status in cloud-init package in Ubuntu:
  Triaged
Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in resolvconf source package in Xenial:
  In Progress
Status in systemd source package in Xenial:
  Fix Committed
Status in cloud-init source package in Yakkety:
  New
Status in resolvconf source package in Yakkety:
  In Progress
Status in systemd source package in Yakkety:
  Fix Committed
Status in resolvconf package in Debian:
  New

Bug description:
  Ubuntu Core 16 images using cloud-init fail to function when the
  DataSource is over the network (Like OpenStack) as networking is not
  yet available when cloud-init.service runs.

  cloud-init service unit deps look like this:

  [Unit]
  Description=Initial cloud-init job (metadata service crawler)
  DefaultDependencies=no
  Wants=cloud-init-local.service
  Wants=local-fs.target
  Wants=sshd-keygen.service
  Wants=sshd.service
  After=cloud-init-local.service
  After=networking.service
  Requires=networking.service
  Before=basic.target
  Before=dbus.socket
  Before=network-online.target
  Before=sshd-keygen.service
  Before=sshd.service
  Before=systemd-user-sessions.service
  Conflicts=shutdown.target

  Here's networkd unit deps:

  [Unit]
  Description=Network Service
  Documentation=man:systemd-networkd.service(8)
  ConditionCapability=CAP_NET_ADMIN
  DefaultDependencies=no
  # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be
  # dropped once tuntap is moved to netlink
  After=systemd-udevd.service dbus.service network-pre.target 
systemd-sysusers.service systemd-sysctl.service
  Before=network.target multi-user.target shutdown.target
  Conflicts=shutdown.target
  Wants=network.target

  # On kdbus systems we pull in the busname explicitly, because it
  # carries policy that allows the daemon to acquire its name.
  Wants=org.freedesktop.network1.busname
  After=org.freedesktop.network1.busname

  And a critical-chain output:

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd
  Failed to get ID: Unit name systemd-networkd is not valid.
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  systemd-networkd.service +440ms
  └─dbus.service @11.461s
    └─basic.target @11.403s
  └─sockets.target @11.401s
    └─dbus.socket @11.398s
  └─cloud-init.service @10.127s +1.266s
    └─networking.service @9.305s +799ms
  └─network-pre.target @9.295s
    └─cloud-init-local.service @3.822s +5.469s
  └─local-fs.target @3.813s
    └─run-cgmanager-fs.mount @12.687s
  └─local-fs-pre.target @1.393s
    └─systemd-tmpfiles-setup-dev.service @1.116s +195ms
  └─kmod-static-nodes.service @887ms +193ms
    └─system.slice @783ms
  └─-.slice @721ms

  cloud-init would need networkd to run at or before
  'networking.service' so it can raise networking to then find and use
  network-based datasources.

  # grep systemd /usr/share/snappy/dpkg.list
  ii  libnss-resolve:amd64  229-4ubuntu11   
 amd64nss module to resolve names via systemd-resolved
  ii  libpam-systemd:amd64  229-4ubuntu11   
 amd64system and service manager - PAM module
  ii  libsystemd0:amd64 229-4ubuntu11   
 amd64systemd utility library
  ii  systemd   229-4ubuntu11   
 amd64system and service manager
  ii  systemd-sysv  229-4ubuntu11   
 amd64system and service manager - SysV links

  # grep cloud-init /usr/share/snappy/dpkg.list
  ii  cloud-init
0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all  Init 
scripts for cloud instances

  SRU INFORMATION FOR systemd
  ===
  Fix: For xenial it is sufficient

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5-1ubuntu1.dsc"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791618/+files/gtk+3.0_3.22.5-1ubuntu1.dsc

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

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

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5-1ubuntu2_source.changes"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791616/+files/gtk+3.0_3.22.5-1ubuntu2_source.changes

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

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

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5-1ubuntu2.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791613/+files/gtk+3.0_3.22.5-1ubuntu2.debian.tar.xz

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

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

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5-1ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791617/+files/gtk+3.0_3.22.5-1ubuntu1.debian.tar.xz

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

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

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1572331] Re: GtkPlug scaled to half the expected size on HiDPI screens

** Attachment added: "gtk+3.0_3.22.5-1ubuntu2_source.build"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1572331/+attachment/4791615/+files/gtk+3.0_3.22.5-1ubuntu2_source.build

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

Title:
  GtkPlug scaled to half the expected size on HiDPI screens + zesty
  debdiff

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

Bug description:
  Hi,

  Marmuta wrote a patch for this issue, that I applied to the gtk+3.0
  package shipping currently in the development version of Ubuntu zesty.
  You will find the corresponding debdiff attached to this bug thread.

  Marmuta performed tests with org.gnome.desktop.interface scaling-
  factor = 2 , where few issues are left for Onboard on hidpi screens,
  that are not related to gtk, but rather to unity-greeter or gnome-
  screensaver. He did not notice any issue with scaling-factor = 1.

  Can a sponsor please review the debdiff?

  Thanks in advance.

  Francesco

  =
  Original description:

  See attached screen shot. Blue is a GtkPlug, black is a GtkSocket.
  Source code below.

  What I expect to happen is that the GtkPlug has the same size as the 
GtkSocket.
  What actually happens is that GtkPlug only covers a quarter of the area of 
the GtkSocket.

  Impact: Onboard on HiDPI displays is near unusable at login and lock
  screen, aka unity-greeter and gnome-screensaver. Original bug report
  here: https://bugs.launchpad.net/bugs/1562734.

  Steps to reproduce:
  - build plug and socket samples from below
  - set display scaling factor to 2
    System Settings -> Display -> Scale for menu and title bars = 2
  - run  ./socket $(head -1 <(./plug))
  -> blue GtkPlug is too small, it should cover all the black

  - resize the window
  -> at smaller sizes the scaling suddenly corrects itself, at larger ones it's 
wrong again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 20 01:48:50 2016
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1649419] Re: unable to install apps from ubuntu store

2016-12-14 Thread Daniel Frost

Hi Alberto,

thanks for taking time to look into this matter.

1) Done, see attached screenshots, I took them with my original language
settings in german and changed to english and took them again
Regardless of the app I am trying to install the box at the top is always empty.
I did also try to press "deny" (could have been the buttons mixed up) without
success.

2) Yes I do have an UbuntuOne account set up and registered within system
settings
I did that in order to get app updates after OTA 13. Ohterwise I had to enter
the credentials every time I was checking for updates. That was a bit anoying
;-) .

3) That was already done before trying to install apps, see 2).

If you need anything else please let me know, I will try to provide wit.

** Attachment added: "screenshots as requested, see comment no. 3"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+attachment/4791625/+files/bugreport%201649419.zip

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

Title:
unable to install apps from ubuntu store

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Incomplete

Bug description:
Since OTA 13 I am not able to install ANY app from the ubuntu store on my BQ
E5.
I do click on install, then I am asked to confirm access to my UbuntuOne
account and thats it, back to the install page.
I tried several apps with the same negative result.
I do have over 4GB free space, so that should not cause trouble.
The phone has been rebooted a couple of times i.e. to upgrade to OTA 14.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1649419/+subscriptions

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

[Touch-packages] [Bug 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

(tag change as per previous comment)

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

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in apt source package in Xenial:
  Fix Committed
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  [Impact]
  Breaks installation in some non-English locales.

  [Test case]
  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  [Regression potential]
  Very low, we're running this in 1.3 since a long time. The fix depends on 
another one that restricts the Date parser to accept only UTC time zones in 
Release files, though (we do not understand the other ones anyway), and thus 
might reject some repositories it silently accepted in a wrong way previously 
(we have not seen anyone report a regression yet since uploading that in June).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls

2016-12-14 Thread Tyler Hicks

** Also affects: libseccomp (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: libseccomp (Ubuntu Trusty)
   Status: New => In Progress

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

** Changed in: libseccomp (Ubuntu Trusty)
 Assignee: (unassigned) => Tyler Hicks (tyhicks)

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

Title:
  seccomp missing many new syscalls

Status in Snappy:
  Fix Released
Status in Snappy 15.04 series:
  Fix Released
Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Trusty:
  In Progress
Status in libseccomp source package in Vivid:
  Fix Released
Status in libseccomp source package in Wily:
  Fix Released

Bug description:
  [Impact]
  Several syscalls were discovered to be missing when using the launcher on 
snappy. These should be added so we may properly support seccomp filtering.

  [Test Case]
  seccomp itself has a comprehensive testsuite, and while it doesn't fail the 
build, regressions can be seen by looking at the build log. Eg:

  Regression Test Summary
  tests run: 6494
  tests skipped: 52
  tests passed: 6494
  tests failed: 0
  tests errored: 0

  
  Furthermore, on a snappy system, perform:
  $ sudo snappy install hello-world
  $ hello-world.env

  It should show the environment. On an arm system with 2.1.1-1 from the 
archive, this will fail due to a seccomp denial:
  audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 
pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 
compat=0 ip=0xb6fb0bd6 code=0x0

  (note, snappy images have a ppa fix for this, see notes below).

  
  To test the segfault fix, do:
  $ scmp_sys_resolver 1024
  Segmentation fault

  It should return:
  $ scmp_sys_resolver 1024
  UNKNOWN

  
  For the new 3.19 syscalls:
  $ scmp_sys_resolver getrandom
  -1

  it should return something like (actual number depends on arch, this is on 
armhf):
  $ scmp_sys_resolver getrandom
  384


  autopkgtests for libseccomp have been added as part of this update to verify 
that the library recognizes all the syscalls from 3.19 and the private 
syscalls. These tests can be run like so (assuming you are in the unpacked 
source and the binaries are in ../binary):
  $ export REL=vivid
  $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source 
../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot 
autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED"

  Alternatively, if you don't have autopkgtest setup, you can do:
  $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev 
seccomp
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter
  ...
  PASS
  $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh 
./debian/tests/test-scmp_sys_resolver
  ...
  PASS

  
  Lastly, seccomp is used by lxc. lxc can be tested by using the test case as 
outlined in step 4 of 
https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only.

  
  [Regression Potential]
  If the above tests, regression potential is considered low. Unknown syscalls 
will continue to be handled as before.


  Description of changes:
  add finit_module:
  
https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15

  sync the syscall table entries - 3.16
  
https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75
  
https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4
  
https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd
  
https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb
  
https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718
  
https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a

  sync the syscall table entries - 3.17
  
https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9

  sync the syscall table entries - 3.19
  
https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3

  This should also be applied (fix a segfault for invalid syscall numbers):
  
https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3

  In addition, add-missing-arm-private-syscalls.patch is add to add 5
  private ARM syscalls. These are absolutely required on snappy. This
  portion of the patch has been well tested and is included by default
  in stable snappy images via the snappy image PPA.

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

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

[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7.1

> much earlier than anybody thought

...except for the guy who commented on the Qt blog with "what took y'all
so long?" :)

Enjoy the holidays!

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

Title:
  Update Qt to 5.7.1

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1650007] [NEW] Consider changing Google API key

Public bug reported:

evolution-data-server (e-d-s) 3.20 before 3.20.6 and 3.22 before 3.22.2
had bugs that caused users using Google services to experience daily
limit timeouts and authentication errors. Unfortunately, users using
older versions are causing those problems for everyone that still uses
the affected API key. Therefore GNOME is updating the API key used by
GNOME Online Accounts. For more info, see LP: #1649995 and
https://bugzilla.gnome.org/774202

- I don't know yet if e-d-s before 3.20 is also affected. I asked but
you're welcome to ask the Evolution devs yourself.
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61

- Upstream evolution has two ways to configure a Google account: GNOME
Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd way.
(I think e-d-s will need to switch to a new Google API key too but that
hasn't happened yet.)

- For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP:
#1639926) to be pushed to yakkety-updates and fully 100% phased before
publishing the new key.

- Therefore, assuming Ubuntu Online Accounts is affected, I suggest you
consider changing the Google API key used in Ubuntu 16.10 and above. (We
might also need to make these changes to 16.04 LTS too.)

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
Importance: Undecided
Status: New

Title:
Consider changing Google API key

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
New

Bug description:
evolution-data-server (e-d-s) 3.20 before 3.20.6 and 3.22 before
3.22.2 had bugs that caused users using Google services to experience
daily limit timeouts and authentication errors. Unfortunately, users
using older versions are causing those problems for everyone that
still uses the affected API key. Therefore GNOME is updating the API
key used by GNOME Online Accounts. For more info, see LP: #1649995 and
https://bugzilla.gnome.org/774202

- I don't know yet if e-d-s before 3.20 is also affected. I asked but
you're welcome to ask the Evolution devs yourself.
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61

- Upstream evolution has two ways to configure a Google account: GNOME
Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd
way. (I think e-d-s will need to switch to a new Google API key too
but that hasn't happened yet.)

- For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP:
#1639926) to be pushed to yakkety-updates and fully 100% phased before
publishing the new key.

- Therefore, assuming Ubuntu Online Accounts is affected, I suggest
you consider changing the Google API key used in Ubuntu 16.10 and
above. (We might also need to make these changes to 16.04 LTS too.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1650007/+subscriptions

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

[Touch-packages] [Bug 1640293] Re: Backport graphical-session{, -pre}.target to xenial

2016-12-14 Thread Dan Streetman

I verified this does add the targets, without enabling them.

with systemd 229-4ubuntu7:

ubuntu@lp1640293:~$ systemctl --user status graphical-session{,-pre}.target
● graphical-session.target
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)

● graphical-session-pre.target
   Loaded: not-found (Reason: No such file or directory)
   Active: inactive (dead)


after adding xenial-proposed repo and upgrading to systemd 229-4ubuntu13:

ubuntu@lp1640293:~$ systemctl --user status graphical-session{,-pre}.target
● graphical-session.target - Current graphical user session
   Loaded: loaded (/usr/lib/systemd/user/graphical-session.target; static; 
vendor preset: enabled)
   Active: inactive (dead)
 Docs: man:systemd.special(7)

● graphical-session-pre.target - Session services which should run early before 
the graphical sessio
   Loaded: loaded (/usr/lib/systemd/user/graphical-session-pre.target; static; 
vendor preset: enable
   Active: inactive (dead)
 Docs: man:systemd.special(7)


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

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

Title:
  Backport graphical-session{,-pre}.target to xenial

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed

Bug description:
  Ted Gould and Dimitri Ledkov requested that the graphical-
  session{,-pre}.target user units introduced in yakkety should be
  backported to xenial, so that snapd units can use them.

  At the moment they will *not* be used by default by any desktop
  session in xenial, so they will stay inert. The net effect is solely
  to ship those two new unit files.

  TEST CASE: Verify that these two new units exist in the -proposed
  version:

/usr/lib/systemd/user/graphical-session-pre.target
/usr/lib/systemd/user/graphical-session.target

  and that they are *not* running (systemctl --user status graphical-
  session{,-pre}.target)

  REGRESSION POTENTIAL: Practically zero.

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

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

[Touch-packages] [Bug 1649995] Re: Replace Google API key used by GNOME services

2016-12-14 Thread Bug Watch Updater

** Changed in: gnome-online-accounts
   Status: Unknown => Fix Released

** Changed in: gnome-online-accounts
   Importance: Unknown => Medium

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

Title:
  Replace Google API key used by GNOME services

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnome-online-accounts source package in Yakkety:
  New

Bug description:
  Impact
  ==
  Some bugs in evolution-data-server were causing daily limit errors for those 
using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example).

  This update changes the API key used by those using the GNOME Online
  Accounts feature.

  Test Case
  =
  Restart your computer after applying the updates.

  Then use Evolution with a Google account configured by gnome-control-
  center's Online Accounts. The easiest way to configure that correctly
  is to use Ubuntu GNOME.

  Make sure that Evolution works without getting authentication errors
  with your Google services.

  Regression Potential
  
  I think the only possibility for regression is if GNOME did not configure the 
key correctly with Google's developer platform.

  Other Info
  ==
  This update depends on the pending evolution-data-server 3.22.3 SRU (LP: 
#1639926) since we need to make sure the user has a fixed version of 
evolution-data-server so we don't taint the new keys too!

  Also, Evolution has two ways to use Google services: 1) GNOME Online
  Accounts 2) evolution-data-server has its own Google authentication
  method. The evolution-data-server key probably will similarly need to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1649995/+subscriptions

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

[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

** Changed in: oxide/1.20
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: oxide/1.20
   Importance: Undecided => High

** Changed in: oxide/1.20
   Status: New => Incomplete

** Changed in: oxide/1.20
   Status: Incomplete => Confirmed

** Changed in: oxide/1.20
Milestone: None => 1.20.0

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

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  In Progress
Status in Oxide 1.19 series:
  Confirmed
Status in Oxide 1.20 series:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

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

[Touch-packages] [Bug 1649964] Re: POWER9 128-bit iEEE float point support in GDB

2016-12-14 Thread Steve Langasek

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

** Changed in: gdb (Ubuntu)
Milestone: None => ubuntu-17.02

** Changed in: gdb (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => 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/1649964

Title:
  POWER9 128-bit iEEE float point support in GDB

Status in gdb package in Ubuntu:
  Triaged

Bug description:
  It is missing the 128-bit IEEE floating-point types support in GDB

  These are the commit ids from the patchset already included on
  upstream GDB, they should be available on next gdb release:

  5f3bceb68dd211be977eb61d5f1ea68e7de51b7aFix typo in ada_language_arch_info
  ae438bc5c06b770c00f37e4ed244707ce3ab9ff4Fix TYPE_SPECIFIC_FIELD for types 
created via arch_type
  88dfca6c43c11dea69db24cfb87e6821e63e29b2Add some missing arch_..._type 
helpers
  19f392bc2a93d9e64d063b884cd6eca547c8dad0Unify init_type and arch_type 
interface and helpers
  a9ff5f12cff6cd06f74ecf387ac5468984c94c6fRemove obsolete TYPE_FLAG_... 
values
  c413c44801e449f1f0b9828b81770e752b8219afRemove TYPE_NOSIGN "char" hack
  49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6Add missing format for built-in 
floating-point types
  9b790ce7227fa346d08a41462119e9a3e93f5e80Add gdbarch callback to provide 
formats for debug info float types
  00d5215ecec4fa0a78dcc37fec9425593753eb66Support 128-bit IEEE 
floating-point types on Intel and Power

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

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

[Touch-packages] [Bug 1640290] Re: Update Qt to 5.7.1

2016-12-14 Thread Flames_in_Paradise

It's there (much earlier than anybody thought):

https://blog.qt.io/blog/2016/12/14/qt-5-7-1-released/ (Dec.14th)

This is just for the records, I personally am not impatient. Wishing
you, Timo, a nice year's ending – knowing that you are quite occupied.

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

Title:
  Update Qt to 5.7.1

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  Tracking bug.

  https://people.canonical.com/~ubuntu-archive/transitions/html/html
  /qtbase-abi-5-7-1.html

  Debian successfully completed the 5.7 transition.

  Ubuntu PPA to be populated: https://bileto.ubuntu.com/#/ticket/1985
  More information: https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1643708] Re: Add SPNEGO special case for NTLMSSP+MechListMIC

2016-12-14 Thread Joshua R. Poulson

[Test Case]

create a file with some credentials:

$ echo F23:guest:guest > ~/ntlmcreds.txt
$ export NTLM_USER_FILE=~/ntlmcreds.txt
$ python
import gssapi

spnego = gssapi.raw.oids.OID.from_int_seq('1.3.6.1.5.5.2')
c = gssapi.creds.Credentials(mechs=[spnego], usage='initiate')
tname = gssapi.raw.names.import_name("F23/server", 
name_type=gssapi.raw.types.NameType.hostbased_service)
ac = gssapi.creds.Credentials(mechs=[spnego], usage='accept')

seci = gssapi.SecurityContext(creds=c, name=tname, mech=spnego, 
usage='initiate')
seca = gssapi.SecurityContext(creds=ac, usage='accept')
it = seci.step(token=None)
ot = seca.step(token=it)
it = seci.step(token=ot)
ot = seca.step(token=it)
it = seci.step(token=ot)

e = seci.wrap("Secrets", True)
o = seca.unwrap(e.message)

o.message
'Secrets'

So far I checked with GDB that the seq numbers were reset after the
MEchListMIC operation happened and started again from 0.

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

Title:
  Add SPNEGO special case for NTLMSSP+MechListMIC

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Incomplete
Status in krb5 source package in Xenial:
  Incomplete
Status in krb5 source package in Yakkety:
  Incomplete

Bug description:
  MS-SPNG section 3.3.5.1 documents an odd behavior the SPNEGO layer
  needs to implement specifically for the NTLMSSP mechanism.  This is
  required for compatibility with Windows services.

  Upstream commit:
  https://github.com/krb5/krb5/commit/cb96ca52a3354e5a0ea52e12495ff375de54f9b7

  We've run into this issue with Linux to Windows negotiation with
  encrypted http using GSSAPI.

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

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

[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars

2016-12-14 Thread Ralf Hersel

Error still in OTA-14
- signed certificate
- simple passwort
- no problems with log-in from Firefox 50.1.0 on Linux PC
Ubuntu Touch: Error message: Invalid host URL

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

Title:
  can't connect with owncloud calendars

Status in Canonical System Image:
  Fix Released
Status in Ubuntu Calendar App:
  New
Status in account-plugins package in Ubuntu:
  Fix Released

Bug description:
  Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar 
App
  The httpS certificate is official, up to date and not self-signed
  I use 7 calendars in my ownCloud-calendar-app.
  (yes, username and password is correct)

  This I tried:

  https://mydomain/owncloud/(suggested minimal path on the phone)
  Error message: Invalid username or password

  https://mydomain/owncloud/remote.php/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/   --> (This is the primary caldav 
address suggested by ownCloud calendar-app)
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/
  Error message: Invalid host URL

  
  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/
  Error message: Invalid host URL
  --> This direct path to one of my calendars I use for example to connect my 
different calendars with Thunderbird lightning (its working)

  I tried all with and without ending "/"

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

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

[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars

2016-12-14 Thread Ralf Hersel

I've created aa account for testing purpose:

URL: https://ralfhersel.ocloud.de/index.php/login
Use: ralfhersel
Password: bmbwbmbw
Primary CalDav Adress: https://ralfhersel.ocloud.de/remote.php/dav/

Please use it only for testing with regard to this bug, thanks.

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

Title:
  can't connect with owncloud calendars

Status in Canonical System Image:
  Fix Released
Status in Ubuntu Calendar App:
  New
Status in account-plugins package in Ubuntu:
  Fix Released

Bug description:
  Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar 
App
  The httpS certificate is official, up to date and not self-signed
  I use 7 calendars in my ownCloud-calendar-app.
  (yes, username and password is correct)

  This I tried:

  https://mydomain/owncloud/(suggested minimal path on the phone)
  Error message: Invalid username or password

  https://mydomain/owncloud/remote.php/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/   --> (This is the primary caldav 
address suggested by ownCloud calendar-app)
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/
  Error message: Invalid host URL

  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/
  Error message: Invalid host URL

  
  https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/
  Error message: Invalid host URL
  --> This direct path to one of my calendars I use for example to connect my 
different calendars with Thunderbird lightning (its working)

  I tried all with and without ending "/"

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

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

[Touch-packages] [Bug 1639478] Re: Merge with Debian 0.48.0

** Changed in: poppler (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Merge with Debian 0.48.0

Status in poppler package in Ubuntu:
  Fix Committed

Bug description:
  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.

  https://people.canonical.com/~ubuntu-
  archive/transitions/html/poppler.html

  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.

  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===

  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS

  poppler (0.48.0-2) unstable; urgency=medium

    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)

   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100

  poppler (0.48.0-1) experimental; urgency=medium

    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same

   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

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

[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

** Changed in: oxide
   Status: Confirmed => In Progress

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

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  In Progress
Status in Oxide 1.19 series:
  Confirmed
Status in Oxide 1.20 series:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

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

[Touch-packages] [Bug 1650022] [NEW] We need a "close" action for killing an app in a trust prompt

Public bug reported:

The original designs for trust prompts included a close action in the
header to close apps that were opened in a trust session.  This is
particularly important when apps might not behave well or hang, there is
no way out.  The close action is like a back button to take you back out
of the app.

We're close to landing trust session support in content-hub, where we'll
open source apps for content picking in a trust prompt.  We've found
apps that have a tendency to hang, leaving the user no way out besides
killing both the source and destination apps.  Clearly those apps need
some fixing, but we need to give the user an easy way out.

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

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

Title:
  We need a "close" action for killing an app in a trust prompt

Status in unity8 package in Ubuntu:
  New

Bug description:
  The original designs for trust prompts included a close action in the
  header to close apps that were opened in a trust session.  This is
  particularly important when apps might not behave well or hang, there
  is no way out.  The close action is like a back button to take you
  back out of the app.

  We're close to landing trust session support in content-hub, where
  we'll open source apps for content picking in a trust prompt.  We've
  found apps that have a tendency to hang, leaving the user no way out
  besides killing both the source and destination apps.  Clearly those
  apps need some fixing, but we need to give the user an easy way out.

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

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

[Touch-packages] [Bug 1618900] Re: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

** Description changed:

+ [Impact]
+ There are some race conditions in unattended-upgrades when it is used in 
shutdown mode. It is possible that the network has already been brought down or 
for a local file system, like /var/, to be unmounted before the 
unattended-upgrades script is run.  This then causes the updates not to be 
installed thereby making systems less secure - if security updates are enabled.
+ 
+ [Test Case]
+ Because this is a race condition, I haven't actually been able to recreate 
the bug.  However, the fix is straightforward and testing for regressions 
should be sufficient.
+ 
+ 1) On a freshly installed system.
+ 2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that 
+ Unattended-Upgrade::InstallOnShutdown "true"; is not commented out.
+ 3) Reboot and watch updates being installed
+ 4) Verify updates were installed by reviewing 
/var/log/unattended-upgrades/unattended-upgrades.log
+ 5) Uncomment -updates in 50unattended-upgrades
+ 
+ Repeats steps 3 and 4 again. There isn't any need to run unattended-
+ upgrades in *not* shutdown mode because we have only modified the
+ systemd service file.
+ 
+ [Regression Potential]
+ There is little chance of a regression, but because of the change (and this 
feature now working better) its possible the shutdown process will take longer 
and surprise users.
+ 
+ Original Description
+ 
+ 
  Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we 
encounter the following systemd dependencies issues :
  - The network is often down when unattended-upgrades is running, so packages 
can not be downloaded (can be mitigated by using 
APT::Periodic::Download-Upgradeable-Packages "1";) :
- => ERROR An error occurred: 'Could not resolve host: .fr'
- => ERROR The URI 
'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb'
 failed to download, aborting
+ => ERROR An error occurred: 'Could not resolve host: .fr'
+ => ERROR The URI 
'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb'
 failed to download, aborting
  - Important mountpoints like /boot are unmounted before unattended-upgrades 
is running, so newer kernels can not be installed properly (ramdisk and grub 
configuration can not be generated)

** Changed in: unattended-upgrades (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: unattended-upgrades (Ubuntu Yakkety)
   Status: Triaged => In Progress

** Changed in: unattended-upgrades (Ubuntu Yakkety)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Yakkety:
  In Progress

Bug description:
  [Impact]
  There are some race conditions in unattended-upgrades when it is used in 
shutdown mode. It is possible that the network has already been brought down or 
for a local file system, like /var/, to be unmounted before the 
unattended-upgrades script is run.  This then causes the updates not to be 
installed thereby making systems less secure - if security updates are enabled.

  [Test Case]
  Because this is a race condition, I haven't actually been able to recreate 
the bug.  However, the fix is straightforward and testing for regressions 
should be sufficient.

  1) On a freshly installed system.
  2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that 
  Unattended-Upgrade::InstallOnShutdown "true"; is not commented out.
  3) Reboot and watch updates being installed
  4) Verify updates were installed by reviewing 
/var/log/unattended-upgrades/unattended-upgrades.log
  5) Uncomment -updates in 50unattended-upgrades

  Repeats steps 3 and 4 again. There isn't any need to run unattended-
  upgrades in *not* shutdown mode because we have only modified the
  systemd service file.

  [Regression Potential]
  There is little chance of a regression, but because of the change (and this 
feature now working better) its possible the shutdown process will take longer 
and surprise users.

  Original Description
  

  Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we 
encounter the following systemd dependencies issues :
  - The network is often down when unattended-upgrades is running, so packages 
can not be downloaded (can be mitigated by using 
APT::Periodic::Download-Upgradeable-Packages "1";) :
  => ERROR An error occurred: 'Could not resolve host: .fr'
  => ERROR The URI 
'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb'

[Touch-packages] [Bug 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software

** Tags added: rls-z-incoming

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

Title:
  Unable to automatically remove packages that become unused in
  conjunction with updating by other software

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  When using default settings for unattended-upgrades i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false"; 
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; 
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  U-U is unable to remove packages that become unused in conjunction with 
updating by other software such as update-manager or apt full-upgrade. This is 
because U-U compares the list of unneeded packages before and after it upgrades 
packages to detect which packages are new unused ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used

** Tags added: rls-z-incoming

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

Title:
  Marks unneeded packages as manually installed, if --dry-run is used

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  
  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  Option --dry-run given, *not* performing real actions
  Packages that will be upgraded:
  marking linux-headers-4.2.0-16-generic for remove
  marking linux-headers-4.2.0-16 for remove
  marking linux-image-4.2.0-16-generic for remove
  marking linux-image-extra-4.2.0-16-generic for remove
  Packages that are auto removed: 'linux-headers-4.2.0-16-generic 
linux-headers-4.2.0-16 linux-image-4.2.0-16-generic 
linux-image-extra-4.2.0-16-generic'
  /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove 
linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all 
linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64
  /usr/bin/dpkg --status-fd 11 --configure --pending
  Packages were successfully auto-removed
  InstCount=0 DelCount=4 BrokenCount=0

  $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux-
  headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-
  image-4.2.0-16-generic:amd64

  $ sudo unattended-upgrade --dry-run -d
  Initial blacklisted packages:
  Initial whitelisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=wily-security']
  pkgs that look like they should be upgraded:
  Fetched 0 B in 0s (0 B/s)
  fetch.run() result: 0
  blacklist: []
  whitelist: []
  No packages found that can be upgraded unattended and no pending auto-removals

  Expect the packages to remain automatically installed after each `sudo
  unattended-upgrade --dry-run -d`.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unattended-upgrades 0.86.2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Feb 12 13:58:29 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-24 (18 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 
2016-02-12T13:53:13.426454

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

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

[Touch-packages] [Bug 1649453] Re: systemd starts postfix before resolver

2016-12-14 Thread Greg Black

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

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

Title:
  systemd starts postfix before resolver

Status in postfix package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Postfix starts before systemd-resolved.service, resulting in postfix
  reporting that it can't find MX records for outgoing mail, as shown in
  the trace below:

  $ systemd-analyze critical-chain postfix.service systemd-resolved.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  postfix.service +1ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms
  systemd-resolved.service +268ms
  └─network.target @5.811s
└─NetworkManager.service @5.690s +91ms
  └─dbus.service @5.627s
└─basic.target @5.597s
  └─sockets.target @5.597s
└─snapd.socket @5.597s +269us
  └─sysinit.target @5.596s
└─systemd-timesyncd.service @5.420s +175ms
  └─systemd-tmpfiles-setup.service @5.408s +8ms
└─local-fs.target @5.390s
  └─zfs-mount.service @3.879s +1.511s
└─zfs-import-cache.service @2.539s +1.303s
  └─systemd-udev-settle.service @256ms +2.252s
└─systemd-udev-trigger.service @208ms +47ms
  └─systemd-udevd-control.socket @148ms
└─-.mount @122ms
  └─system.slice @124ms
└─-.slice @122ms

  The postfix service needs to start after systemd-resolved.service.

  $ lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  $ apt-cache policy systemd
  systemd:
Installed: 231-9ubuntu1
Candidate: 231-9ubuntu1
Version table:
   *** 231-9ubuntu1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive 
yakkety-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   231-9git1 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages

  $ apt-cache policy postfix
  postfix:
Installed: 3.1.0-5
Candidate: 3.1.0-5
Version table:
   *** 3.1.0-5 500
  500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 
Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

** Branch linked: lp:apport

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

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

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

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

2016-12-14 Thread Steve Beattie

** Information type changed from Private Security to Public Security

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

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

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

[Touch-packages] [Bug 1648806] Re: Arbitrary code execution through crafted CrashDB or Package/Source fields in .crash files

2016-12-14 Thread Martin Pitt

New upstream release with the fixes:
https://launchpad.net/apport/trunk/2.20.4

Note that Brian committed some changes to trunk in the last 1.5 hours,
so we had some mid-air collection. I force-pushed trunk and will put
back his commits on top.

** Changed in: apport
   Status: In Progress => Fix Released

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

Title:
  Arbitrary code execution through crafted CrashDB or Package/Source
  fields in .crash files

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Precise:
  Fix Released
Status in apport source package in Trusty:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Yakkety:
  New
Status in apport source package in Zesty:
  Fix Committed

Bug description:
  Forwarding private (encrypted) mail from Donncha O'Cearbhaill
  :

  = 8< ==
  Hi Martin,

  I have been auditing the Apport software in my free time and
  unfortunately I have found some serious security issues.

  Untrusted files can be passed to apport-gtk as it is registered as the
  default file handler for "text/x-apport" files. The mime-type includes
  .crash files but also any unknown file type which begins with
  "ProblemType: ". An attacker could social engineer a victim into opening
  a malicious Apport crash file simply by clicking on it.

  In apport/ui.py, Apport is reading the CrashDB field and then it then
  evaluates the field as Python code if it begins with a "{". This is very
  dangerous as it can allow remote attackers to execute arbitrary Python code.

  The vulnerable code was introduce on 2012-08-22 in Apport revision
  2464
  (http://bazaar.launchpad.net/~apport-hackers/apport/trunk/files/2464).
  This code was first included in release 2.6.1. All Ubuntu Desktop
  versions after 12.05 (Precise) include this vulnerable code by default.

  An easy fix would be to parse the value as JSON instead of eval()'ing
  it.

  There is also a path traversal issue where the Package or SourcePackage
  fields are not sanitized before being used to build a path to the
  package specific hook files in the /usr/share/apport/package-hooks/
  directory.

  By setting "Package: ../../../../proc/self/cwd/Downloads/rce-hook.py" a
  remote attacker could exploit this bug to execute Python scripts that
  have be placed in the user's Downloads directory.

  Would you like to apply for a CVE for this issues or should I? I'd like
  to see these issue fixed soon so that Ubuntu users can be kept safe. I'm
  planning to publish a blog post about these issues but I'll wait until
  patched version of Apport are available in the repositories.

  Please let me know if you have any questions.

  Kind Regards,
  Donncha
  = 8< ==

  I just talked to Donna on Jabber, and he plans to disclose that in
  around a week.

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

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

[Touch-packages] [Bug 1650036] [NEW] Some mkv files report error

2016-12-14 Thread flocculant

Public bug reported:

Playing some video files - especially mkv files sees totem report
Internal Data Stream error

Grabbed
http://trailers.divx.com/divx_prod/profiles/WiegelesHeliSki_DivXPlus_19Mbps.mkv
to test.

running totem from terminal gets:

totem

(totem:12124): Gtk-WARNING **: Failed to get the GNOME session proxy:
The name org.gnome.SessionManager is not owned

(totem:12124): Gtk-WARNING **: Calling org.xfce.Session.Manager.Inhibit
failed: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method
"Inhibit" with signature "susu" on interface "org.xfce.Session.Manager"
doesn't exist


(totem:12124): Totem-WARNING **: Failed to reset the playback rate to 1.0

(totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(totem:12124): GLib-GObject-CRITICAL **:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed

(totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(totem:12124): GLib-GObject-CRITICAL **:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed

(totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(totem:12124): GLib-GObject-CRITICAL **:
g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
(instance)' failed

(totem:12124): Totem-CRITICAL **: totem_object_empty_menu_section:
assertion 'TOTEM_IS_OBJECT (totem)' failed

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libgstreamer1.0-0 1.10.2-1
ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8
Uname: Linux 4.9.0-10-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Dec 14 21:57:45 2016
InstallationDate: Installed on 2016-06-11 (186 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Some mkv files report error

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Playing some video files - especially mkv files sees totem report
  Internal Data Stream error

  Grabbed
  
http://trailers.divx.com/divx_prod/profiles/WiegelesHeliSki_DivXPlus_19Mbps.mkv
  to test.

  running totem from terminal gets:

  totem

  (totem:12124): Gtk-WARNING **: Failed to get the GNOME session proxy:
  The name org.gnome.SessionManager is not owned

  (totem:12124): Gtk-WARNING **: Calling
  org.xfce.Session.Manager.Inhibit failed:
  GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Inhibit"
  with signature "susu" on interface "org.xfce.Session.Manager" doesn't
  exist

  
  (totem:12124): Totem-WARNING **: Failed to reset the playback rate to 1.0

  (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (totem:12124): GLib-GObject-CRITICAL **:
  g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
  (instance)' failed

  (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (totem:12124): GLib-GObject-CRITICAL **:
  g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
  (instance)' failed

  (totem:12124): GLib-GObject-WARNING **: invalid (NULL) pointer
  instance

  (totem:12124): GLib-GObject-CRITICAL **:
  g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE
  (instance)' failed

  (totem:12124): Totem-CRITICAL **: totem_object_empty_menu_section:
  assertion 'TOTEM_IS_OBJECT (totem)' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: libgstreamer1.0-0 1.10.2-1
  ProcVersionSignature: Ubuntu 4.9.0-10.11-generic 4.9.0-rc8
  Uname: Linux 4.9.0-10-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Dec 14 21:57:45 2016
  InstallationDate: Installed on 2016-06-11 (186 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1650036/+subscriptions

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

[Touch-packages] [Bug 1593583] Re: Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety-proposed_InRelease

We are testing this exact case in the test suite, and it ran
successfully for 1.2.18, hence verification-done.

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

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

Title:
  Invalid 'Date' entry in Release file
  /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety-
  proposed_InRelease

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  New

Bug description:
  Continuously get that warning when using synaptic to reload the
  sources. This happen with apt 1.3-exp2 only.

  This seems a regression as per that old report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809329

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3~exp2
  ProcVersionSignature: Ubuntu 4.6.0-7.8-generic 4.6.0
  Uname: Linux 4.6.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jun 17 08:19:22 2016
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

  For the SRU:

  [Impact]
  Prevent adding this regression to 1.2.16
  [Test case]
  Parse (Release file with) date where hour is single digit
  [Regression potential]
  Should be very low, we are running this in yakkety too, and in Debian since 
quite some time.

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

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

[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-12-14 Thread Chris Coulson

** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

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

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

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

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

2016-12-14 Thread Anders Kaseorg

Or virtual machines: a VM running in virt-manager on a zesty host can’t
resolve CNAMEs (not even a zesty VM with libnss-resolve inside!).

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

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

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Triaged

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

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

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

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

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

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

[Touch-packages] [Bug 1650007] Re: Consider changing Google API key

** Package changed: ubuntu-system-settings-online-accounts (Ubuntu) =>
account-plugins (Ubuntu)

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

Title:
  Consider changing Google API key

Status in account-plugins package in Ubuntu:
  New

Bug description:
  evolution-data-server (e-d-s) 3.20 before 3.20.6 and 3.22 before
  3.22.2 had bugs that caused users using Google services to experience
  daily limit timeouts and authentication errors. Unfortunately, users
  using older versions are causing those problems for everyone that
  still uses the affected API key. Therefore GNOME is updating the API
  key used by GNOME Online Accounts. For more info, see LP: #1649995 and
  https://bugzilla.gnome.org/774202

  - I don't know yet if e-d-s before 3.20 is also affected. I asked but
  you're welcome to ask the Evolution devs yourself.
  https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61

  - Upstream evolution has two ways to configure a Google account: GNOME
  Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd
  way. (I think e-d-s will need to switch to a new Google API key too
  but that hasn't happened yet.)

  - For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP:
  #1639926) to be pushed to yakkety-updates and fully 100% phased before
  publishing the new key.

  - Therefore, assuming Ubuntu Online Accounts is affected, I suggest
  you consider changing the Google API key used in Ubuntu 16.10 and
  above. Once we figure out if e-d-s needs to be updated for 16.04 (and
  possibly earlier releases), I believe we'll need to update the key
  there too.

  - On the other hand, since we control Ubuntu updates (unlike GNOME
  which has not control over who uses what version of their stuff) maybe
  we don't need to change the key after all. Maybe we just need to push
  the e-d-s SRUs as security updates to ensure people use the fixed
  versions?

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

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

[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

2016-12-14 Thread Chris Coulson

** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

** Also affects: oxide/1.20
   Importance: Undecided
   Status: New

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

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  Confirmed
Status in Oxide 1.19 series:
  Confirmed
Status in Oxide 1.20 series:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

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

[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-12-14 Thread Chris Coulson

** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

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

Title:
  Webview appears to think it's in focus when typing in the addressbar

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

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

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

[Touch-packages] [Bug 1650007] Re: Consider changing Google API key

** Description changed:

- I don't know yet if e-d-s before 3.20 is also affected. I asked but
you're welcome to ask the Evolution devs yourself.
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61

- For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP:
#1639926) to be pushed to yakkety-updates and fully 100% phased before
publishing the new key.

- Therefore, assuming Ubuntu Online Accounts is affected, I suggest you
- consider changing the Google API key used in Ubuntu 16.10 and above. (We
- might also need to make these changes to 16.04 LTS too.)
+ consider changing the Google API key used in Ubuntu 16.10 and above.
+ Once we figure out if e-d-s needs to be updated for 16.04 (and possibly
+ earlier releases), I believe we'll need to update the key there too.
+
+ - On the other hand, since we control Ubuntu updates (unlike GNOME which
+ has not control over who uses what version of their stuff) maybe we
+ don't need to change the key after all. Maybe we just need to push the
+ e-d-s SRUs as security updates to ensure people use the fixed versions?

Title:
Consider changing Google API key

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
New

- I don't know yet if e-d-s before 3.20 is also affected. I asked but
you're welcome to ask the Evolution devs yourself.
https://bugzilla.gnome.org/show_bug.cgi?id=771547#c61

- Upstream evolution has two ways to configure a Google account: GNOME
Online Accounts and e-d-s. I assume Ubuntu Online Accounts is a 3rd
way. (I think e-d-s will need to switch to a new Google API key too
but that hasn't happened yet.)

- For Ubuntu 16.10, we need the latest evolution-data-server SRU (LP:
#1639926) to be pushed to yakkety-updates and fully 100% phased before
publishing the new key.

- Therefore, assuming Ubuntu Online Accounts is affected, I suggest
you consider changing the Google API key used in Ubuntu 16.10 and
above. Once we figure out if e-d-s needs to be updated for 16.04 (and
possibly earlier releases), I believe we'll need to update the key
there too.

- On the other hand, since we control Ubuntu updates (unlike GNOME
which has not control over who uses what version of their stuff) maybe
we don't need to change the key after all. Maybe we just need to push
the e-d-s SRUs as security updates to ensure people use the fixed
versions?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1650007/+subscriptions

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

[Touch-packages] [Bug 1639926] Re: Update evolution-data-server to 3.22.3

** Description changed:

Impact
==
This is the second evolution SRU for yakkety. This update includes the new
bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update
evolution to 3.22.3 (LP: #1639942)

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

Low. There are a fair amount of changes in this update, but they are all
targeted towards fixing bugs. This is the same release that other GNOME 3.22
distros ship. This may be the last official 3.22 release for the Evolution
stack.

Other Info
==
- Note that there is an issue with Google authentication affecting at least
3.20 and 3.22.0. It might still be present in this release.
+ Note that there is an issue with Google authentication affecting at least
3.20 and 3.22.0. The underlying issue should be fixed with this update (it was
partially fixed with 3.22.1 already in yakkety-updates). Unfortunately, anyone
anywhere using older still-broken versions of e-d-s still break authentication
for everyone else using the same API key!

- I was a bit confused trying to read the evolution mailing list and some
- of the bug reports. It's possible that other people using older versions
- of evolution are causing the Google to block the shared API key because
- of too many authentication errors. If that's so, we can hope distros and
- users update promptly. Or we could ship an Ubuntu-specific key.
+ Because of this, GNOME is updating the key used by GNOME Online Accounts
+ (LP: #1649995). The key used by e-d-s might need to be updated too. And
+ maybe the key used by Ubuntu Online Accounts (LP: #1650007). This is
+ because there are 2 or 3 different ways to use a Google account with
+ Evolution. You only need to update the key for the Google authentication
+ method you use.

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

Title:
Update evolution-data-server to 3.22.3

Status in evolution-data-server package in Ubuntu:
Fix Released
Status in evolution-data-server source package in Yakkety:
In Progress

Bug description:
Impact
==
This is the second evolution SRU for yakkety. This update includes the new
bugfix releases 3.22.2 and 3.22.3. Updating e-d-s is required to update
evolution to 3.22.3 (LP: #1639942)

https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22
https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22

Test Case
=
After installing the update, restart your computer. (Is there a flag
evolution-data-server should set to prompt the user to do this?)

Run several eds-using apps like Evolution, GNOME Calendar and verify
that they continue to run at least as well as before this update.

Regression Potential

Other Info
==
Note that there is an issue with Google authentication affecting at least
3.20 and 3.22.0. The underlying issue should be fixed with this update (it was
partially fixed with 3.22.1 already in yakkety-updates). Unfortunately, anyone
anywhere using older still-broken versions of e-d-s still break authentication
for everyone else using the same API key!

Because of this, GNOME is updating the key used by GNOME Online
Accounts (LP: #1649995). The key used by e-d-s might need to be
updated too. And maybe the key used by Ubuntu Online Accounts (LP:
#1650007). This is because there are 2 or 3 different ways to use a
Google account with Evolution. You only need to update the key for the
Google authentication method you use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+subscriptions

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

[Touch-packages] [Bug 1649995] Re: Replace Google API key used by GNOME services

** Description changed:

  Impact
  ==
- Some bugs in evolution-data-server were causing daily limit errors for those 
using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example).
+ Some bugs in evolution-data-server (e-d-s) were causing daily limit errors 
for those using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example). Unfortunately, it looks like users using 
older versions of e-d-s are causing those errors to affect everyone using e-d-s 
since they are using the same API key. It's very difficult for GNOME to push 
everyone to use an updated version of their software.
  
- This update changes the API key used by those using the GNOME Online
- Accounts feature.
+ Therefore, this update changes the API key used by those using the GNOME
+ Online Accounts feature for Google services.
  
  Test Case
  =
  Restart your computer after applying the updates.
  
  Then use Evolution with a Google account configured by gnome-control-
  center's Online Accounts. The easiest way to configure that correctly is
  to use Ubuntu GNOME.
  
  Make sure that Evolution works without getting authentication errors
  with your Google services.
  
  Regression Potential
  
  I think the only possibility for regression is if GNOME did not configure the 
key correctly with Google's developer platform.
  
  Other Info
  ==
  This update depends on the pending evolution-data-server 3.22.3 SRU (LP: 
#1639926) since we need to make sure the user has a fixed version of 
evolution-data-server so we don't taint the new keys too!
  
  Also, Evolution has two ways to use Google services: 1) GNOME Online
  Accounts 2) evolution-data-server has its own Google authentication
  method. The evolution-data-server key probably will similarly need to be
  updated.

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

Title:
  Replace Google API key used by GNOME services

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnome-online-accounts source package in Yakkety:
  New

Bug description:
  Impact
  ==
  Some bugs in evolution-data-server (e-d-s) were causing daily limit errors 
for those using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example). Unfortunately, it looks like users using 
older versions of e-d-s are causing those errors to affect everyone using e-d-s 
since they are using the same API key. It's very difficult for GNOME to push 
everyone to use an updated version of their software.

  Therefore, this update changes the API key used by those using the
  GNOME Online Accounts feature for Google services.

  Test Case
  =
  Restart your computer after applying the updates.

  Then use Evolution with a Google account configured by gnome-control-
  center's Online Accounts. The easiest way to configure that correctly
  is to use Ubuntu GNOME.

  Make sure that Evolution works without getting authentication errors
  with your Google services.

  Regression Potential
  
  I think the only possibility for regression is if GNOME did not configure the 
key correctly with Google's developer platform.

  Other Info
  ==
  This update depends on the pending evolution-data-server 3.22.3 SRU (LP: 
#1639926) since we need to make sure the user has a fixed version of 
evolution-data-server so we don't taint the new keys too!

  Also, Evolution has two ways to use Google services: 1) GNOME Online
  Accounts 2) evolution-data-server has its own Google authentication
  method. The evolution-data-server key probably will similarly need to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1649995/+subscriptions

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

[Touch-packages] [Bug 1641905] Re: Minor unit Test regression in 1.2.15

Confirming fixed in 1.2.18

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

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

Title:
  Minor unit Test regression in 1.2.15

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed

Bug description:
  In 1.2.15 the unit tests (which run at build time) fail with an error
  message in the atomic files test, because I picked a commit that
  improved the error handling a bit (a previous error now propagates
  into further calls):

  /<>/test/libapt/fileutl_test.cc:376: Failure
  Value of: f.Close()
Actual: false
  Expected: true

  I'll revert that for 1.2.16, as it depends on another fix, and I'm not
  sure I really want those two in there.

  [Impact]
  * Causes unit test failure, but might not have real effects

  [Test Case]
  * Check that build output (which runs unit tests) contains no failure

  [Regression Potential]
  * None, we are just reverting a commit from 1.2.15, so we have the same as in 
1.2.14

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

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

[Touch-packages] [Bug 1649662] Re: resizing a gtk+3/mir app makes it unusable - pixels get stretched and input stops working

2016-12-14 Thread dinamic

it's the same on 16.04 + overlay ppa

** Description changed:

- ubuntu 17.04 unity8 + proposed
+ ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]
  
  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"
  
  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)
  
  see attached screenshot

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

Title:
  resizing a gtk+3/mir app makes it unusable - pixels get stretched and
  input stops working

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

Bug description:
  ubuntu 17.04 unity8 + proposed and 16.04 + overlay PPA
  mir 0.25
  miral 0.25
  unity8/zesty-proposed,now 8.15+17.04.20161207.1-0ubuntu1 amd64 
[installed,automatic]

  steps:
  1)run gedit, nautilus, sol or whatever gtk+3 app ("ubuntu-app-launch sol" for 
ex). if you are not sure how to launch a gtk3 app run 
"ubuntu-app-launch-appids" first to see the appids and then "ubuntu-app-launch 
"

  2) resize the window (the context gets stretched in a weird way and
  input doesn't work anymore)

  see attached screenshot

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

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

[Touch-packages] [Bug 1649995] Re: Replace Google API key used by GNOME services

** Bug watch added: GNOME Bug Tracker #774202
   https://bugzilla.gnome.org/show_bug.cgi?id=774202

** Also affects: gnome-online-accounts via
   https://bugzilla.gnome.org/show_bug.cgi?id=774202
   Importance: Unknown
   Status: Unknown

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

Title:
  Replace Google API key used by GNOME services

Status in gnome-online-accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnome-online-accounts source package in Yakkety:
  New

Bug description:
  Impact
  ==
  Some bugs in evolution-data-server were causing daily limit errors for those 
using Google services with evolution-data-server and apps that use it 
(Evolution is a prominent example).

  This update changes the API key used by those using the GNOME Online
  Accounts feature.

  Test Case
  =
  Restart your computer after applying the updates.

  Then use Evolution with a Google account configured by gnome-control-
  center's Online Accounts. The easiest way to configure that correctly
  is to use Ubuntu GNOME.

  Make sure that Evolution works without getting authentication errors
  with your Google services.

  Regression Potential
  
  I think the only possibility for regression is if GNOME did not configure the 
key correctly with Google's developer platform.

  Other Info
  ==
  This update depends on the pending evolution-data-server 3.22.3 SRU (LP: 
#1639926) since we need to make sure the user has a fixed version of 
evolution-data-server so we don't taint the new keys too!

  Also, Evolution has two ways to use Google services: 1) GNOME Online
  Accounts 2) evolution-data-server has its own Google authentication
  method. The evolution-data-server key probably will similarly need to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1649995/+subscriptions

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

[Touch-packages] [Bug 1649964] [NEW] POWER9 128-bit iEEE float point support in GDB

2016-12-14 Thread bugproxy

Public bug reported:

It is missing the 128-bit IEEE floating-point types support in GDB

These are the commit ids from the patchset already included on upstream
GDB, they should be available on next gdb release:

5f3bceb68dd211be977eb61d5f1ea68e7de51b7aFix typo in ada_language_arch_info
ae438bc5c06b770c00f37e4ed244707ce3ab9ff4Fix TYPE_SPECIFIC_FIELD for types 
created via arch_type
88dfca6c43c11dea69db24cfb87e6821e63e29b2Add some missing arch_..._type 
helpers
19f392bc2a93d9e64d063b884cd6eca547c8dad0Unify init_type and arch_type 
interface and helpers
a9ff5f12cff6cd06f74ecf387ac5468984c94c6fRemove obsolete TYPE_FLAG_... values
c413c44801e449f1f0b9828b81770e752b8219afRemove TYPE_NOSIGN "char" hack
49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6Add missing format for built-in 
floating-point types
9b790ce7227fa346d08a41462119e9a3e93f5e80Add gdbarch callback to provide 
formats for debug info float types
00d5215ecec4fa0a78dcc37fec9425593753eb66Support 128-bit IEEE floating-point 
types on Intel and Power

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-145026 severity-critical 
targetmilestone-inin1704

** Tags added: architecture-ppc64le bugnameltc-145026 severity-critical
targetmilestone-inin1704

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

** Package changed: ubuntu => gdb (Ubuntu)

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

Title:
  POWER9 128-bit iEEE float point support in GDB

Status in gdb package in Ubuntu:
  New

Bug description:
  It is missing the 128-bit IEEE floating-point types support in GDB

  These are the commit ids from the patchset already included on
  upstream GDB, they should be available on next gdb release:

  5f3bceb68dd211be977eb61d5f1ea68e7de51b7aFix typo in ada_language_arch_info
  ae438bc5c06b770c00f37e4ed244707ce3ab9ff4Fix TYPE_SPECIFIC_FIELD for types 
created via arch_type
  88dfca6c43c11dea69db24cfb87e6821e63e29b2Add some missing arch_..._type 
helpers
  19f392bc2a93d9e64d063b884cd6eca547c8dad0Unify init_type and arch_type 
interface and helpers
  a9ff5f12cff6cd06f74ecf387ac5468984c94c6fRemove obsolete TYPE_FLAG_... 
values
  c413c44801e449f1f0b9828b81770e752b8219afRemove TYPE_NOSIGN "char" hack
  49f190bcb7f074ea2e27d4e967e4fae9ed7dafb6Add missing format for built-in 
floating-point types
  9b790ce7227fa346d08a41462119e9a3e93f5e80Add gdbarch callback to provide 
formats for debug info float types
  00d5215ecec4fa0a78dcc37fec9425593753eb66Support 128-bit IEEE 
floating-point types on Intel and Power

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

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

[Touch-packages] [Bug 1635856] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1635856/+attachment/4791729/+files/ThreadStacktrace.txt

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

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

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

Title:
  cupsd 2.2.0-2 crashed with SIGABRT in __malloc_assert()

Status in cups package in Ubuntu:
  New

Bug description:
  I am unable to print after a smooth upgrade from 16.04 to 16.10, as
  the cupsd service would not start. The installed version of cups-
  daemon is 2.2.0-2.  I am using Ubuntu release 16.10.

  
  Syslog shows:

  Oct 22 18:36:46 mcarro-ThinkPad-X1-Carbon-3rd cupsd[20036]: cupsd:
  malloc.c:2880: mremap_chunk: Assertion `((size + offset) & (GLRO
  (dl_pagesize) - 1)) == 0' failed.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: cups-daemon 2.2.0-2
  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
  CrashCounter: 1
  Date: Sat Oct 22 09:35:50 2016
  ExecutablePath: /usr/sbin/cupsd
  InstallationDate: Installed on 2015-06-15 (495 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO 20BSCTO1WW
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cupsd (enforce)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=b5bda038-97c0-40f3-b9ba-67c06b05ae03 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=b5bda038-97c0-40f3-b9ba-67c06b05ae03 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups
  StacktraceTop:
   __malloc_assert (assertion=assertion@entry=0x7f62b27fa308 "((size + offset) 
& (GLRO (dl_pagesize) - 1)) == 0", file=file@entry=0x7f62b27f6e2e "malloc.c", 
line=line@entry=2880, function=function@entry=0x7f62b27fae28 <__func__.11331> 
"mremap_chunk") at malloc.c:301
   mremap_chunk (p=p@entry=0x5653d935dab0, new_size=new_size@entry=8288) at 
malloc.c:2880
   __GI___libc_realloc (oldmem=0x5653d935dac0, bytes=8275) at malloc.c:3060
   cupsFilePrintf () from /usr/lib/x86_64-linux-gnu/libcups.so.2
   ?? ()
  Title: cupsd crashed with SIGABRT in __malloc_assert()
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (7 days ago)
  UserGroups:
   
  dmi.bios.date: 05/08/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET29W (1.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1649959] Re: unattended upgrade of apt kills running apt-daily job

2016-12-14 Thread Adam Conrad

Hello Chaskiel, or anyone else affected,

Accepted apt into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.3.3 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

Title:
  unattended upgrade of apt kills running apt-daily job

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Causes automatic upgrades by unattended-upgrades to be interrupted if apt is 
configured, leaving the system in a partially configured state.

  [Test case]
  Install apt - make sure the apt-daily.service is not restarted (this systemd 
service runs unattended-upgrades)

  [Regression Potential] 
  It's only overriding dh_systemd_start to not be called for the service, so I 
don't see any possibility for regressions.

  [Original Bug report]
  This morning, I discovered that my new xenial system had attempted an 
unattended upgrade overnight but the upgrade was incomplete. It attempted to 
upgrade
  apt apt-transport-https apt-utils firefox firefox-locale-en 
flashplugin-installer libapt-inst2.0 libapt-pkg5.0 libgme0

  but the unattended-upgrades-dpkg.log log terminates after apt is
  configured.

  I had to dpkg --configure --pending and apt-get -f install to get apt back 
into working order.
  There were no errors, crashes or cores logged.

  The journal indicates that apt-daily.service stopped and restarted around the 
time of the upgrade, so I am assuming that is the problem (that systemd killed 
the update session as the result of an update to the unit files)
  ---
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-12-06 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NonfreeKernelModules: openafs
  Package: apt 1.3.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Tags:  yakkety
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1500751] Re: Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

** Tags removed: verification-needed

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

Title:
  Cryptsetup Keyboard not working on Xubuntu 3.19.0-30

Status in cryptsetup package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Trusty:
  Invalid
Status in initramfs-tools source package in Trusty:
  Fix Released
Status in cryptsetup source package in Vivid:
  Invalid
Status in initramfs-tools source package in Vivid:
  Won't Fix

Bug description:
  I am running Xubuntu 15.04 and just upgraded to the latest kernel (3.19.0-30).
  After upgrading the boot time is longer (what is negligible) but the more 
severe error is, that I cannot enter my passphrase when I see the crypt dialog.
  I just see the dialog to enter my passphrase, but when I try to enter it, 
nothing appears in the textfield. I tried with the builtin laptop keyboard but 
also with an external USB keyboard.

  I thought about supplying more information, but things like the syslog
  are not helping apparently (I was not able to boot until the syslog
  would capture information...). If you need anything I can provide, I
  gladly help.

  [Test case]
  1. On an affected system boot into kernel 3.19.0-30

  [Solution]
  The "solution" for now is booting the older Kernel 3.19.0-28 (which isn't a 
real solution).

  PS.: Bugs like the following are either not applicable or the solution is not 
working for me:
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/229732
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1359689
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1238194

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

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

[Touch-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field

2016-12-14 Thread przekop

Hello
I can confirm this bug with Polish characters on current version of Evince in 
Ubuntu 14.04 and 16.04
Same with documents created with Acrobat PDFMaker or LibreOffice Writer.
I found Master PDF Editor which works fine. I can fill forms and save pdf 
properly.

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

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

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

[Touch-packages] [Bug 1649959] Re: unattended upgrade of apt kills running apt-daily job

We know. This is fixed in zesty-proposed (in 1.4~beta1 actually). It
will be backported into 1.3.3 later this month.

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

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

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

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

** Changed in: apt (Ubuntu Yakkety)
   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/1649959

Title:
  unattended upgrade of apt kills running apt-daily job

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Yakkety:
  Confirmed

Bug description:
  This morning, I discovered that my new xenial system had attempted an 
unattended upgrade overnight but the upgrade was incomplete. It attempted to 
upgrade
  apt apt-transport-https apt-utils firefox firefox-locale-en 
flashplugin-installer libapt-inst2.0 libapt-pkg5.0 libgme0

  but the unattended-upgrades-dpkg.log log terminates after apt is
  configured.

  I had to dpkg --configure --pending and apt-get -f install to get apt back 
into working order.
  There were no errors, crashes or cores logged.

  The journal indicates that apt-daily.service stopped and restarted around the 
time of the upgrade, so I am assuming that is the problem (that systemd killed 
the update session as the result of an update to the unit files)
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-12-06 (7 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NonfreeKernelModules: openafs
  Package: apt 1.3.2ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Tags:  yakkety
  Uname: Linux 4.8.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1649673] Re: Add peekier as possible search engine

2016-12-14 Thread Emanuele Sorce

Thanks! I will try to implement it.

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

Title:
  Add peekier as possible search engine

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Is a good search engine, is not a full-of-ad or a google wrapper.
  Consider adding it

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

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

[Touch-packages] [Bug 1639478] Re: Merge with Debian 0.48.0

2016-12-14 Thread Michael Terry

Thanks jbicha!  Though since your work, a new ubuntu patch got added to
poppler.  So I just redid the merge and uploaded.

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

Title:
  Merge with Debian 0.48.0

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  I successfully test-built poppler 0.48 on zesty. I did not test-build
  the rdepends.

  https://people.canonical.com/~ubuntu-
  archive/transitions/html/poppler.html

  I dropped the change to not build-depend on openjpeg2; the (universe)
  build-depends is fine since we do still disable openjpeg2.

  Changes since Ubuntu version 0.44.0-3ubuntu2
  ===

  https://cgit.freedesktop.org/poppler/poppler/tree/NEWS

  poppler (0.48.0-2) unstable; urgency=medium

    * Upload to unstable. (See #839869)
    * autopkgtest: build the qt5 test with -std=c++11, required with Qt5 >= 5.6.
    * Backport upstream commit 5d15a52aade68c618c356fe403ca500e74917ef7 to 
remove
  an extra '%' in an error message of pdfseparate; patch
  upstream_pdfseparate-remove-extra-in-error-message.patch. (Closes: 
#835202)

   -- Pino Toscano   Sat, 05 Nov 2016 08:29:43 +0100

  poppler (0.48.0-1) experimental; urgency=medium

    * New upstream release:
  - fixes UTF-16 decoding of document outline title (Closes: #702082)
  - fixes crashes in PDF documents (Closes: #830565)
    * Rename packages according to the new SONAMEs:
  - libpoppler61 -> libpoppler64
    * Update copyright.
    * Bump the libglib2.0-dev (build-)dependency to 2.41, as noted in the
  upstream build system.
    * Update symbols files.
    * Bump shlibs for libpoppler-cpp0v5 to >= 0.46.0, following the new APIs
  added.
    * Install the GObject introspection data in a multi-arch directory:
  - bump the libgirepository1.0-dev, and gobject-introspection to
    >= 1.42.0-2~, as providing a fixed dh_girepository
  - update gir1.2-poppler-0.18.install
  - mark gir1.2-poppler-0.18 as Multi-Arch: same

   -- Pino Toscano   Sat, 08 Oct 2016 20:14:42 +0200

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

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

[Touch-packages] [Bug 1645698] Re: [SRU] network-manager 1.2.4

2016-12-14 Thread Michael Terry

** Also affects: network-manager (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: (unassigned) => Aron Xu (happyaron)

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

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

Title:
  [SRU] network-manager 1.2.4

Status in network-manager package in Ubuntu:
  Invalid
Status in network-manager source package in Xenial:
  Triaged

Bug description:
  [Impact]

  This SRU would try to have the latest upstream point release of 1.2.x
  land in Xenial, which is the successor of the current 1.2.2 version,
  fixing quite some bugs that's suitable to land in the sable branch.

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leak in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This version has been in yakkety for sometime, and there's no report
  of regressions until now.

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

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

[Touch-packages] [Bug 1635856] StacktraceSource.txt