Re: [Touch-packages] [Bug 1500242] Re: Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Uranicus]

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

Title:
  Bluetooth device (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

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

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

-- 
Mailing list: https://launchpad.net/~touch-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: [systemd] SIGPWR doesn't always lead to shutdown

[Stéphane Graber]

Hmm, that journal log looks like it could be a lxcfs problem though I don't 
remember seeing problems on shutdown in the past...
We did have a rather bad bug at startup a little while back though.

-- 
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:
  [systemd] SIGPWR doesn't always lead to shutdown

Status in lxd package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

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/lxd/+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 1311752] Re: Keep file chooser on top of the mediaplayer window

[Jean-Baptiste Lallement]

** Changed in: mediaplayer-app (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Keep file chooser on top of the mediaplayer window

Status in mediaplayer-app package in Ubuntu:
  Invalid

Bug description:
  The file selector is a modal window but can be moved behind its parent
  window. In this case, the file selector receive the events but is
  invisible.

  TEST CASE:
  1. Launch the media player with a video
  2. Open the file selector dialog by tapping on the button at the bottom right 
of the main window
  3. Click on the main window

  ACTUAL RESULT
  The file selector dialog moves behind the mediaplayer, becomes invisible and 
it is not possible to interact with the media player.

  EXPECTED RESULT
  The file selector stays on top.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mediaplayer-app 0.20.5+14.04.20140331-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 23 17:39:36 2014
  InstallationDate: Installed on 2014-04-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: mediaplayer-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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: [systemd] SIGPWR doesn't always lead to shutdown

[Sven R. Kunze]

>>> uname -a
Linux mexico 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
>>> lxc exec test -- uname -a
Linux test 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux


journalctl only shows messages related to container startup:


>>> lxc exec test -- journalctl
-- Logs begin at Mon 2015-11-30 21:03:37 UTC, end at Mon 2015-11-30 21:03:53 
UTC. --
Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) 
is currently using 8.0M.
   Maximum allowed usage is set to 
799.2M.
   Leaving at least 1.1G free (of 
currently available 7.7G of space).
   Enforced usage limit is thus 799.2M.
Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) 
is currently using 8.0M.
   Maximum allowed usage is set to 
799.2M.
   Leaving at least 1.1G free (of 
currently available 7.7G of space).
   Enforced usage limit is thus 799.2M.
Nov 30 21:03:37 test systemd-journal[223]: Journal started
Nov 30 21:03:37 test systemd-remount-fs[108]: /bin/mount for / exited with exit 
status 1.
Nov 30 21:03:37 test systemd-remount-fs[108]: mount: can't find 
LABEL=cloudimg-rootfs
Nov 30 21:03:37 test mount[133]: mount: permission denied
Nov 30 21:03:37 test loadkeys[145]: Couldn't get a file descriptor referring to 
the console
Nov 30 21:03:37 test apparmor[157]: lxc
Nov 30 21:03:37 test apparmor[157]: * Not starting AppArmor in container
Nov 30 21:03:37 test apparmor[157]: ...done.
Nov 30 21:03:37 test systemd[1]: console-setup.service: Main process exited, 
code=exited, status=1/FAILURE
Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed to kill control 
group: Invalid argument
Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed to kill control 
group: Invalid argument
Nov 30 21:03:37 test systemd[1]: Failed to start Set console keymap.
Nov 30 21:03:37 test systemd[1]: console-setup.service: Unit entered failed 
state.
Nov 30 21:03:37 test systemd-journal[223]: Forwarding to syslog missed 1 
messages.
Nov 30 21:03:37 test systemd[1]: console-setup.service: Failed with result 
'exit-code'.
Nov 30 21:03:37 test systemd[1]: Started LSB: AppArmor initialization.
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill 
control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill 
control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill 
control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: plymouth-read-write.service: Failed to kill 
control group: Invalid argument
Nov 30 21:03:37 test systemd[1]: Started Tell Plymouth To Write Out Runtime 
Data.
Nov 30 21:03:37 test systemd[1]: Started Load/Save Random Seed.
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control 
group: Invalid argument
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control 
group: Invalid argument
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control 
group: Invalid argument
Nov 30 21:03:37 test systemd[1]: dns-clean.service: Failed to kill control 
group: Invalid argument
Nov 30 21:03:37 test systemd[1]: Started Clean up any mess left by 0dns-up.
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on 
/lxc/test/system.slice/resolvconf.service: Permission denied
Nov 30 21:03:37 test systemd[1]: Starting Nameserver information manager...
Nov 30 21:03:37 test sh[185]: Segmentation fault (core dumped)
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on 
/lxc/test/system.slice/systemd-journal-flush.service: Permission denied
Nov 30 21:03:37 test systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on 
/lxc/test/system.slice/systemd-random-seed.service: Permission denied
Nov 30 21:03:37 test systemd-journal[223]: Runtime journal (/run/log/journal/) 
is currently using 8.0M.
   Maximum allowed usage is set to 
799.2M.
   Leaving at least 1.1G free (of 
currently available 7.7G of space).
   Enforced usage limit is thus 799.2M.
Nov 30 21:03:37 test systemd[1]: Started Flush Journal to Persistent Storage.
Nov 30 21:03:37 test systemd[1]: Started Nameserver information manager.
Nov 30 21:03:37 test systemd[1]: Failed to reset devices.list on 
/lxc/test/system.slice/systemd-journal-flush.service: Permission denied

-- 
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:
 

[Touch-packages] [Bug 1519499] Re: [systemd] SIGPWR doesn't always lead to shutdown

[Sven R. Kunze]

> We've seen some weird behavior with systemd on some specific kernel
releases in the past.

Not sure if that info helps: I have been installing several different
kernels in the mean time; all of them share the same behavior.

-- 
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:
  [systemd] SIGPWR doesn't always lead to shutdown

Status in lxd package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

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/lxd/+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 1518759] Re: package lightdm 1.16.5-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lightdm 1.16.5-0ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  I was trying to update terminator using the following commands

  sudo add-apt-repository ppa:gnome-terminator
  sudo apt-get update
  sudo apt-get install terminator

  Having said that I'm not sure this directly related.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Mon Nov 23 09:25:00 2015
  DuplicateSignature: package:lightdm:1.16.5-0ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-06-26 (514 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: lightdm
  Title: package lightdm 1.16.5-0ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-10-28 (25 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-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: [systemd] SIGPWR doesn't always lead to shutdown

[Sven R. Kunze]

Also note: confirmed for lxd==0.23

-- 
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:
  [systemd] SIGPWR doesn't always lead to shutdown

Status in lxd package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New

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/lxd/+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 1434517] Re: 480p and 1080p video appear to use the same bitrate

[Bill Filler]

I can confirm similar results recorded on Krilin:

1080p:
1920x1080
31fps
6617kbps
8.7mb filesize

480p:
640x480
31 fps
6452kbps
8.3mb filesize

@jamesh
What would you recommend for the settings at the lower resolution? What bitrate 
would be expected?


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

** No longer affects: camera-app

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => High

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

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

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

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

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

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

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

Title:
  480p and 1080p video appear to use the same bitrate

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

Bug description:
  I just recorded two 10 second videos of the the same object using my
  Nexus 4, one using the 1080p setting and the other 480p.  Both videos
  came out at roughly 8MB, each with approximately a 6.3 Mb/s video bit
  rate and 96 kb/s audio bit rate.

  This seems a bit weird to me: the only reason I can think of to offer
  multiple resolutions is to let the user pick the quality / storage
  space trade off they want.  If the lower resolution videos take up
  just as much space as the high resolution ones, then this doesn't make
  sense.

  I am running build 143 on a Nexus 4, which looks to have camera-app
  3.0.0.516 installed:

  current build number: 143
  device name: mako
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-03-20 07:05:06
  version version: 143
  version ubuntu: 20150320
  version device: 20150210
  version custom: 20150320

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

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

[Touch-packages] [Bug 1512257] Re: Photos made with back camera sometimes are unavailable in gallery

[Michi Henning]

I've opened a separate bug for gallery app:
https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1521365

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

Title:
  Photos made with back camera sometimes are unavailable in gallery

Status in Canonical System Image:
  Incomplete
Status in camera-app package in Ubuntu:
  Triaged
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  [Using Aquaris E.4.5]

  Sometimes when I take a picture with the back camera it will appear with a 
"music icon" in the gallery (making it impossible to view)
  Also, pictures made with the front camera works fine.

  So I must restart my device to make the front camera work again.

  Here is a screen capture of what I see in my gallery...

  Thanks!

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

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

[Touch-packages] [Bug 1521365] [NEW] Crashes and missing thumbnails

[Michi Henning]

Public bug reported:

I've transferred the info for this from here because, apparently, the
original bug report was encountering two separate
problems:https://bugs.launchpad.net/canonical-devices-system-
image/+bug/1512257

I can reproduce this with rc-proposed build 278 on Mako. The gallery app
shows nothing (just white background) where a thumbnail should be. Pawel
saw the same thing and posted a screenshot here:

http://imgur.com/a/j2yoW

To reproduce, start out with a clean cache (thumbnailer-admin clear) and
an empty photo roll, and with neither gallery nor camera running.

Take twenty pictures with the camera.

Start the gallery app from the launcher. For me everything works fine at
this point, thumbnails show up as expected.

Go back to the camera app (via launcher). Take ten more shots.

Go back to the gallery (via launcher). At this point, the gallery app
showed the problem briefly and then crashed, so I re-started the app.
After doing that, it showed the thumbnails correctly.

Go back to the camera app, take ten more pictures, back to gallery-app,
etc. Eventually, the problem will show up (if the gallery app doesn't
crash).

I have verified from the thumbnailer trace that, each time I return to
the gallery app, the app asks for thumbnails for the newly-added images
(plus a bunch of others), and the thumbnailer correctly returns those,
so this is not a thumbnailer problem.

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

** Affects: thumbnailer (Ubuntu)
 Importance: Undecided
 Status: Triaged

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

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

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

Title:
  Crashes and missing thumbnails

Status in gallery-app package in Ubuntu:
  New
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  I've transferred the info for this from here because, apparently, the
  original bug report was encountering two separate
  problems:https://bugs.launchpad.net/canonical-devices-system-
  image/+bug/1512257

  I can reproduce this with rc-proposed build 278 on Mako. The gallery
  app shows nothing (just white background) where a thumbnail should be.
  Pawel saw the same thing and posted a screenshot here:

  http://imgur.com/a/j2yoW

  To reproduce, start out with a clean cache (thumbnailer-admin clear)
  and an empty photo roll, and with neither gallery nor camera running.

  Take twenty pictures with the camera.

  Start the gallery app from the launcher. For me everything works fine
  at this point, thumbnails show up as expected.

  Go back to the camera app (via launcher). Take ten more shots.

  Go back to the gallery (via launcher). At this point, the gallery app
  showed the problem briefly and then crashed, so I re-started the app.
  After doing that, it showed the thumbnails correctly.

  Go back to the camera app, take ten more pictures, back to gallery-
  app, etc. Eventually, the problem will show up (if the gallery app
  doesn't crash).

  I have verified from the thumbnailer trace that, each time I return to
  the gallery app, the app asks for thumbnails for the newly-added
  images (plus a bunch of others), and the thumbnailer correctly returns
  those, so this is not a thumbnailer problem.

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

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

[Touch-packages] [Bug 1442670] Re: Ubuntu Phone BQ: Camera makes blur images

[Bill Filler]

** No longer affects: camera-app

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

Title:
  Ubuntu Phone BQ: Camera makes blur images

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

Bug description:
  Hi!
  A lot of times the camera is getting a really bad images (blur effect) in all 
resolutions.

  And yes, I click previously for a focus.

  I'm sending you an example: That picture looked perfect in the mobile,
  but in the PC is really bad :(

  Thanks in advance!

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

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

[Touch-packages] [Bug 1357345] Re: tar: untaring with --recursive-unlink ends with an empty directory

[Yannick Duchêne]

In case someone is interested in this bug, what I remember I noticed
later, is that `tar` extract a directory, then delete it, then try to
add files in the just deleted directory (which turns to be wrong,
obviously), then sometime recreate the directory, which ends to be
empty.

Someone should care, as `tar` is a core functionality.

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

Title:
  tar: untaring with --recursive-unlink ends with an empty directory

Status in tar package in Ubuntu:
  New

Bug description:
  Using tar version 1.26-4ubuntu1 from Ubuntu 12.04 (I'm submitting this
  case here, as I can't tell if it's specific to the tar shipped with
  Ubuntu or a bug with all tar, and this concerns Ubuntu base packages
  anyway).

  Using the attached archive file, running this:

  /bin/tar --extract --auto-compress --exclude-backups --exclude-caches
  --exclude-vcs --preserve-permissions --recursive-unlink --totals
  --unlink-first --verbose --file Sphinx.tar.xz; ls Sphinx

  … I get an empty directory, although the output says it extracted many
  things.

  This seems to be related to a buggy `--recursive-unlink` option, as
  this one works:

  /bin/tar --extract --auto-compress --exclude-backups --exclude-caches
  --exclude-vcs --preserve-permissions --totals --unlink-first --verbose
  --file Sphinx.tar.xz; ls Sphinx

  … the directory is not empty any‑more.

  I get this unexpected behaviour with this archive only, not with
  others.

  My guess is that it's due to the order in which the entries appears in
  the tar file. Indeed, the Sphinx top level directory is listed last,
  and its content before it, so tar extract its content then delete all
  the directory to recreate the directory, emptied.

  I can't believe this is the expected behaviour.

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

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

[Touch-packages] [Bug 1521334] [NEW] /usr/sbin/NetworkManager:11:on_bss_proxy_acquired:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding network-manager.  This problem was most recently seen with
version 1.0.4-0ubuntu6, the problem page at
https://errors.ubuntu.com/problem/543d9936b26016ef701d965488404ed34e4f0c79
contains more details.

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


** Tags: vivid wily xenial

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

Title:
  
/usr/sbin/NetworkManager:11:on_bss_proxy_acquired:g_task_return_now:g_task_return:init_second_async_cb:g_task_return_now

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.0.4-0ubuntu6, the problem page at
  https://errors.ubuntu.com/problem/543d9936b26016ef701d965488404ed34e4f0c79
  contains more details.

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

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

[Touch-packages] [Bug 1521333] [NEW] /usr/bin/ubuntu-download-manager:11:Ubuntu::DownloadManager::Daemon::FileDownload::resumeTransfer:Ubuntu::Transfers::Queue::updateCurrentTransfer:Ubuntu::Transfers

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding ubuntu-download-manager.  This problem was most recently seen
with version 1.1+15.04.20150922.4-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/709958dd21a360799114eb96c71c73e114d166d0
contains more details.

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


** Tags: vivid

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

Title:
  /usr/bin/ubuntu-download-
  
manager:11:Ubuntu::DownloadManager::Daemon::FileDownload::resumeTransfer:Ubuntu::Transfers::Queue::updateCurrentTransfer:Ubuntu::Transfers::Queue::onManagedTransferStateChanged:QtPrivate::QSlotObjectBase::call:QMetaObject::activate

Status in ubuntu-download-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding ubuntu-download-manager.  This problem was most recently
  seen with version 1.1+15.04.20150922.4-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/709958dd21a360799114eb96c71c73e114d166d0
  contains more details.

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

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

[Touch-packages] [Bug 1521331] [NEW] /usr/bin/history-daemon:11:QListData::detach_grow:QList:QList:QtVersit::VersitUtils::changeCodec:QtVersit::VersitUtils::newlineList

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding history-service.  This problem was most recently seen with
version 0.1+15.04.20151103-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/59588e680ea4e28fe71e5ed7fabc20ec59abdc55
contains more details.

** Affects: history-service (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: vivid

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

Title:
  /usr/bin/history-
  
daemon:11:QListData::detach_grow:QList:QList:QtVersit::VersitUtils::changeCodec:QtVersit::VersitUtils::newlineList

Status in history-service package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding history-service.  This problem was most recently seen with
  version 0.1+15.04.20151103-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/59588e680ea4e28fe71e5ed7fabc20ec59abdc55
  contains more details.

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

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

Re: [Touch-packages] [Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

[Barry Warsaw]

On Nov 30, 2015, at 08:51 PM, Bryan Quigley wrote:

>@barry..  Maybe do LiveCD tests on both of them to see if it's a
>configuration issue or if it might be hardware related.

I'd be very surprised if it was hardware, but I can try it.  I never had this
problem on this machine until this morning's dist-upgrade.

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

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Latest libnss3 upgrade have broken all the browser's queries; no
  matter of which is used. For example: url auto-completion fails

  ERR_SSL_PROTOCOL_ERROR
  Unable to make a secure connection to the server. This may be a problem with 
the server or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.21-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-0.8-generic 4.3.0
  Uname: Linux 4.3.0-0-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 27 13:50:26 2015
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1478693] Re: Camera app creates broken image files with HDR

[Bill Filler]

** Summary changed:

- Camera app creates broken image files
+ Camera app creates broken image files with HDR

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

** No longer affects: camera-app

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

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => High

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

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

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

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

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

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

Title:
  Camera app creates broken image files with HDR

Status in Canonical System Image:
  Triaged
Status in camera-app package in Ubuntu:
  Triaged

Bug description:
  I took some photos with the phone’s camera (Aquaris E4.5). While it
  previously worked, this time a series of three photos produced broken
  files which could not be read by the phone (photos scope, gallery) nor
  by external image viewers.

  HDR was switched on, and I suspect it *might* have to do something
  with it, but that’s just a guess.

  I attach a broken sample file.

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

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

[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

[Alexander Skiba]

Short version: backports won't work.

Slightly longer version: It's not in trusty-backports, it's not in 
vivid-(updates|backports), it is however in wily.
(Yes, I am aware that it's not an LTS and therefore not ideal, I have the same 
situation at work.) Information retrieved on 2015-11-30.

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies "true";'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

  but nothing happens (note the line "Packages that are auto removed: ''
  ":

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  Checking: bc ([""])
  Checking: grub-common ([""])
  Checking: grub-pc ([""])
  Checking: grub-pc-bin ([""])
  Checking: grub2-common ([""])
  Checking: iproute ([""])
  Checking: landscape-common ([""])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS

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

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

[Touch-packages] [Bug 1475895] Re: Camera froze taking picture and would no longer show a preview

[Bill Filler]

** No longer affects: camera-app

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

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

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

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

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

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

Title:
  Camera froze taking picture and would no longer show a preview

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

Bug description:
  MX4 running 59 from rc-proposed

  Zoom fully, took 1 picture which worked fine, took a second picture and the 
view froze, and the picture was not taken.
  Stopped the app.
  Started the camera again, the view is black and the controls cause the camera 
to freeze.
  A reboot cleared it.

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

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

[Touch-packages] [Bug 1521186] Re: "Media Player" should be translatable on Sound Indicator

[Pat McGowan]

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

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

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

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

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

Title:
  "Media Player" should be translatable on Sound Indicator

Status in Canonical System Image:
  In Progress
Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  "Media Player" should be translatable on Sound Indicator, see attached
  screenshot.

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

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

[Touch-packages] [Bug 1520916] Re: downward motion ("terminate") in application stack sometimes hard to execute

[Pat McGowan]

Marking incomplete as have not seen similar reports

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

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

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

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

Title:
  downward motion ("terminate") in application stack sometimes hard to
  execute

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

Bug description:
  In the "stack" of applications (task list) accessible by swiping from
  the right edge, it is possible to "leaf" through the tasks with a
  left-right motion, and to terminate tasks by dragging the downwards.

  However, on occasion, it seems to be very hard to "grab" a task to
  drag it downwards.

  Strangely enough, this doesn't happen consistently.

  Last it happened to me, I accidentally opened the camera app, and when
  wanting to close it, I couldn't drag it down, however I could drag
  down the other running apps that were running at the time without
  problems.

  When I re-attempted the same thing just as I am typing this up, I
  noticed that even dragging down the camera app now works fine. Not
  sure what changed...

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

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

[Touch-packages] [Bug 1513310] Re: The "Delete media" pop up window does not rotate with the screen in camera app.

[Bill Filler]

** No longer affects: camera-app

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

Title:
  The "Delete media" pop up window does not rotate with the screen in
  camera app.

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

Bug description:
  current build number: 154
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-11-04 07:38:22
  version version: 154
  version ubuntu: 20151104
  version device: 20151016-0b38025
  version custom: 20150925-900-8-47

  Precondition:
  1.Some photos or video are saved in the device.
  2.Set Rotation lock as Off state.

  Steps:
  1.Launch camera->Swipe the screen,one picture or video will display.
  2.Tap the menu button and select "Delete",the pop up window "Delete media" 
displays.
  3.Rotate the screen and check the UI.

  Actual result:The pop up window does not rotate and the picture or video 
rotates.
  Expect result:The pop up window should also rotate.

  Comments:In addition,after tapping the menu button,if you select
  "Share" and enter "Share to "interface,rotate the screen,the screen
  also does not rotate.

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

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

[Touch-packages] [Bug 1424740] Re: During video recording flash assisting light turns off after focusing

[Bill Filler]

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

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => High

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

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

** No longer affects: camera-app

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

Title:
  During video recording flash assisting light turns off after focusing

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

Bug description:
  From Zygmunt Krynicki:

  Steps to reproduce:

  1 turn on camera application
  2 switch to video recording mode
  3 swipe from the bottom and turn on LED light
  4 tap to focus
  5 light turns off unexpectedly

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

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

[Touch-packages] [Bug 1512257] Re: Photos made with back camera sometimes are unavailable in gallery

[Bill Filler]

@nicola
Do you happen to have HDR turned on in camera-app? (swipe up from bottom edge 
will reveal the option to set HDR mode)

@michi
I think the problem you are describing is something different and we should 
file a separate bug. I believe Nicola's problem is the images are actually 
getting corrupt whereas your problem is a bug with gallery.

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

** No longer affects: camera-app

** No longer affects: gallery-app (Ubuntu)

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

** Changed in: camera-app (Ubuntu)
   Importance: Undecided => High

** Changed in: camera-app (Ubuntu)
 Assignee: (unassigned) => Florian Boucault (fboucault)

** Changed in: camera-app (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Photos made with back camera sometimes are unavailable in gallery

Status in Canonical System Image:
  Incomplete
Status in camera-app package in Ubuntu:
  Triaged
Status in thumbnailer package in Ubuntu:
  Triaged

Bug description:
  [Using Aquaris E.4.5]

  Sometimes when I take a picture with the back camera it will appear with a 
"music icon" in the gallery (making it impossible to view)
  Also, pictures made with the front camera works fine.

  So I must restart my device to make the front camera work again.

  Here is a screen capture of what I see in my gallery...

  Thanks!

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

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

[Touch-packages] [Bug 1466427] Re: User agent string claims it's running Ubuntu 14.04

[Timo Jyrinki]

Also, Chromium 35 is from 2014 so sites block the browser because of
that. It should reflect the version Oxide is based on.

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

Title:
  User agent string claims it's running Ubuntu 14.04

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.04 r35

  1. Go to a page that reports your user agent string, for example
   or .

  What you see: Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4)
  AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36

  What you should see: The UA string should not say "Ubuntu 14.04".

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

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

[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts

[Magdalena Mirowicz]

@flocculant Thanks for flagging this. Could you report the second issue
(mentioned in last comment) as a separate bug?

Thank you

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

Title:
  New font uses Arabic-sized figures in Latin contexts

Status in Ubuntu Font Family:
  New
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Upgrade of ubuntu fonts  causes fonts to look as in attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 28 12:34:43 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-10-29 (30 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions

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

[Touch-packages] [Bug 1511063] Re: Scopes freeze after few times slide on Bq 4.5

[Pawel Stolowski]

Ok, the real problem is this scope has debug mode enabled in the ini file:
ScopeRunner=./qtc_device_debughelper.py scope 
com.ubuntu.developer.boghison.mixcloud_mixcloudscope 
/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner '' %S 
DebugMode=true

which pretty much disables all the timeouts we have in the middleware
(so that scopes can be debugged with SDK & gdb, client doesn't throw
after scope execution is paused). Scopes should never be released in
such state to the store (store should prevent this IMO). It would also
be nice if we could deal with it somehow.

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

Title:
  Scopes freeze after few times slide on Bq 4.5

Status in unity-scopes-api package in Ubuntu:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  BQ 4.5 Ubuntu-touch OTA7 (Ubuntu 15.04 r26)

  
  After a few slides on the scopes, it freezes the scopes in the middle of 2 
scopes 
  unity left bar can still be moved, but when launching apps from the left bar
  nothing happens to the freezed scopes screen, only rebooting the phone fixes 
it.

  when i remove some scopes from favorites  it freezes on other scopes

  Let me know wich logs i can attach to this bug to make debug easier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1511063/+subscriptions

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

[Touch-packages] [Bug 1512924] Re: Timestamps not localized in notifications

[Richard Somlói]

It looks good with the latest rc-proposed image.

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

Title:
  Timestamps not localized in notifications

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Test case.
  - Flash the phone (krillin, with an external card inserted).
  - Select Spanish.
  - Reboot it.
  - Open the messaging menu.

  Expected result.
  - The storage notification timestamp is localized.

  Actual result.
  - Timestamp is shown in English.

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

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

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

[Touch-packages] [Bug 1510510] Re: Error with geotagging (fixed position defined as geotag)

[Ugo Riboni]

** Changed in: camera-app (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Error with geotagging (fixed position defined as geotag)

Status in camera-app:
  Triaged
Status in Canonical System Image:
  Triaged
Status in camera-app package in Ubuntu:
  In Progress

Bug description:
  When tacking photographs using camera-app, I experience various
  problems with geotagging. Sometimes I don't get any geotag (picture
  1.jpg) and most of the time I got a wrong geocoding, that is always
  the same, and some place I never went to (2.jpg, 3.jpg are examples of
  photos with known places to demonstrate that, Versailles castle
  orangeraie and Eiffel tower in France).

  If more info/tests are needed, don't hesitate to ask.

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

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

[Touch-packages] [Bug 1444857] Re: [enhancement] Allow clients to specify buffering mode for their surfaces

[Alexandros Frantzis]

This will be provided by the new buffer semantics.

** Changed in: mir
   Status: In Progress => New

** Changed in: mir
 Assignee: Alexandros Frantzis (afrantzis) => (unassigned)

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

Title:
  [enhancement] Allow clients to specify buffering mode for their
  surfaces

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Allow clients to specify the buffering mode for their surfaces, so
  that they can optimize for latency or fluidity, depending on the
  expected rendering performance (e.g., if it's expected to occasionally
  miss vsyncs) of the application.

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

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

[Touch-packages] [Bug 1514329] Re: Applications should be able to setup and subscribe to geo fence events

[Launchpad Bug Tracker]

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

** Changed in: location-service (Ubuntu)
   Status: New => Confirmed

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

Title:
  Applications should be able to setup and subscribe to geo fence events

Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Right now, applications are not able to specify that they would like
  to be notified whenever either:

(1.) The location of the device significantly changes.
(2.) The device enters a pre-defined geo rectangle.

  Enabling such use-cases would allow for power-efficient
  implementations of common positioning use-cases.

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

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

[Touch-packages] [Bug 1521010] Re: Can't download files

[Olivier Tilloy]

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

** This bug has been marked a duplicate of bug 1354391
   [browser] Can't download random files

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

Title:
  Can't download files

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Original comment:
  "Had a zip app installed just for the record. Anyways I was downloading a 
file with the browser and all i get is "Sorry, there aren't currently any apps 
installed that can handle this type of content" come on that's just silly! 
Having to whip out wget to dl a file is just frustrating."

  Possible bug?
  I'm not sure if this is intentional or if it is a bug with the browser app, 
even though I have an app that can handle zip files all I can do is cancel when 
i get the message "Sorry, there aren't currently any apps installed that can 
handle this type of content" no download at all I can do is press cancel or 
resort to copy url and run wget in terminal app. I'm not sure if this is 
intentional or a bug, but I assume it is a bug latest stable OTA nexus 4.

  Reproduce:

  Attempt to download a zip file or any other file.

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

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

[Touch-packages] [Bug 1389698] Re: Favoriting QtCreator-ran scope results in blank dash

[Benjamin Zeller]

I can not reproduce this with the current rc-proposed image. Is this
still a problem?

** Changed in: qtcreator-plugin-ubuntu (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Favoriting QtCreator-ran scope results in blank dash

Status in qtcreator-plugin-ubuntu package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Opinion

Bug description:
  Unity8 on mako rtm #6 won't load any scope installed in the system. Sometimes 
it stays on the loading screen with the activity indicator spinning, or it may 
also end up with the white/grey background, but no scopes are loaded.
  I can't use the phone right now, since I can't launch apps from the app 
scope. The left panel works, though.
  This all started after I played a bit with QtCreator because I'm developing a 
scope for the contest.
  I don't know exactly which files to attach, meanwhile there's 
~/.cache/upstart/scope-register.log.
  Tell me if you need more information.

  Thanks in advance for the help,
  Giulio

  Potential steps to reproduce:
  - run a custom scope from QtCreator
  - add that scope to favorites
  - close QtCreator

  This seems to leave the phone in a state where it can't load the
  scopes any more. The below helps to clear this again:

  $ gsettings reset com.canonical.Unity.Dash favorite-scopes

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

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

[Touch-packages] [Bug 1505597] Re: IconAndLink.qml:39:5: QML QQuickImage: Invalid image provider: image://scaling/1//

[Benjamin Zeller]

Adding ubuntu-ui-toolkit to the affected packages. 
This should be fixed in the toolkit ultimately because mixing different QML 
toolkits will be common
at least on desktop (using Qt Controls)

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

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

Title:
  IconAndLink.qml:39:5: QML QQuickImage: Invalid image provider:
  image://scaling/1//

Status in qtcreator-plugin-ubuntu package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  I'm seeing a huge amount of image loading errors of the type

  file:///usr/ubuntu-sdk-
  ide/share/qtcreator/welcomescreen/widgets/IconAndLink.qml:39:5: QML
  QQuickImage: Invalid image provider: image://scaling/1//usr/ubuntu-
  sdk-
  ide/share/qtcreator/welcomescreen/widgets/images/icons/onlineCommunity.png

  with different filenames.

  Note: QT_DEVICE_PIXEL_RATIO=2

  The bug fix is to add

  import Ubuntu.Components 1.2

  to

  /usr/ubuntu-sdk-ide/share/qtcreator/welcomescreen/widgets/IconAndLin
  k.qml

  Otherwise there is a race in loading the image provider depending on
  other code. This is expected because the loader is part of the UITK.

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

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

[Touch-packages] [Bug 1478321] Re: Weird battery values bq Aquaris 4.5

[Matthew Paul Thomas]

The screenshot is not of indicator-power, it is of System Settings.

If the value is jumping in the System Settings graph, it can't be a bug
in indicator-power.

The question then is whether it is a problem in upower, which provides
the charging information, or in System Settings, which graphs the
information provided.

If the battery indicator shows the same percentage, the problem is not
in System Settings, it is in upower.

** Package changed: indicator-power (Ubuntu) => upower (Ubuntu)

** Changed in: upower (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Weird battery values bq Aquaris 4.5

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  Many times it happens that the percentage of the battery shown is not
  the real one.

  Yesterday evening I had a big problem where the phone suddenly went
  from 20% to 0% and it shut itself down.

  This is shown in the battery history graph, that I attach.

  As you can see there are various vertical lines, clearly indicating
  that the value jumps from  one point to the other.

  This is a big problem, because if one sees that the phone has still
  20% of battery, one thinks that it still has 1/5 of its life span
  before dying.

  It is not the first time that this happens to me and others, and I
  believe that anyone experiencing this should attach a picture of it,
  so that eventually we might be able to resolve it, maybe with some
  kind of approximations.

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

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

[Touch-packages] [Bug 1464145] Re: The pause button doesn't display complete

[Sebastien Bacher]

Thanks, the style of the UI changed and the issues seems resolved, could
you try again and confirm if that's the case for you as well?

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

** Changed in: mediaplayer-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  The pause button doesn't display complete

Status in mediaplayer-app package in Ubuntu:
  Incomplete

Bug description:
  $ system-image-cli -i
   current build number: 29
   device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
   last update: 2015-06-10 15:42:15
   version version: 29
   version ubuntu: 20150610
   version device: 20150529-8e13c5f
   version custom: 20150528-722-29-15-vivid
  Reproduce Steps:

  1,Play video or music use phone
  2,Check the pause button carefully 

  Expect Result 
   
  The pause button should be display complete

  Actual Result

  The pause button don't display complete

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

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

[Touch-packages] [Bug 1440325] Re: Media player doesnt show subtitles

[Sebastien Bacher]

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Media player doesnt show subtitles

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  When playing a video theres no option to show subtitles.

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

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

[Touch-packages] [Bug 1417950] [NEW] Wrongly reported "video not supported"

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

For some videos a window showing a "Video format not supported" message
is shown. However, after pressing "Close" the video is shown normally,
so the message is wrong.

A couple of videos where this has been noticed:

http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/BigBuckBunny_DivX_HD720p_ASP.divx
(video and audio are played here)

http://samplemedia.linaro.org/Mmtest/media_api/video/H263_56_AMRNB_6.3gp
(video is supported, but AMR audio not yet, that might be related to the bug)

$ system-image-cli -i
current build number: 80
device name: mako
channel: ubuntu-touch/vivid-proposed
last update: 2015-01-28 13:36:03
version version: 80
version ubuntu: 20150128
version device: 20150126
version custom: 20150128

** Affects: media-hub
 Importance: Undecided
 Status: Invalid

** Affects: mediaplayer-app (Ubuntu)
 Importance: High
 Status: Triaged

** Affects: ubuntu-rtm
 Importance: Undecided
 Status: Confirmed

-- 
Wrongly reported "video not supported"
https://bugs.launchpad.net/bugs/1417950
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1427816] [NEW] Pause icon on toolbar does not switch to play icon when headphones are disconnected and playback is auto-paused

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1. Play a video with mediaplayer-app from the video scope.
2. Plug in pair of headphones.
3. Unplug the headphones and notice that playback automatically pauses.
4. The play/pause icon in the toolbar remains showing the pause icon when it 
should have switched to showing the play icon.

Bug is on RTM stable build #19.

** Affects: mediaplayer-app (Ubuntu)
 Importance: Low
 Assignee: Jim Hodapp (jhodapp)
 Status: Fix Released

-- 
Pause icon on toolbar does not switch to play icon when headphones are 
disconnected and playback is auto-paused
https://bugs.launchpad.net/bugs/1427816
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1517107] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1517107

Title:
  $PATH is getting clobbered when starting a container with Upstart

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC 1.1 and higher mangles the process env to be able to re-title 
itself, breaking the environment for sub-processes in the process
  Test case: Spawn a container and check /proc/self/environ
  Regression potential: Worst case scenario is we stamp on a different part of 
the process memory leading to similar but different breakage. It's been tested 
not to be the case though, change comes from upstream.

  == Original bug report ==
  I have a script using the Python3 LXC API that starts up a container.  If I 
use an Upstart job to call the script, the $PATH env var is getting clobbered 
and the container fails to start.

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

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

[Touch-packages] [Bug 1441068] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1441068

Title:
  lxc-destroy fails on btrfs subvolumes

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  $ sudo lxc-destroy -n adt-vivid
  [sudo] password for martin: 
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs
  lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying 
rootfs for adt-vivid
  Destroying adt-vivid failed

  This is because the container rootfs has a btrfs subvolume:

  ID 557 gen 97073 top level 266 path @srv/lxc/adt-
  vivid/rootfs/var/lib/machines

  After "sudo btrfs subvolume delete /srv/lxc/adt-
  vivid/rootfs/var/lib/machines" I can remove the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:51:51 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1497420] Re: systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxcfs package in Ubuntu:
  Fix Released
Status in cgmanager source package in Vivid:
  New
Status in lxc source package in Vivid:
  Fix Released
Status in lxcfs source package in Vivid:
  New
Status in cgmanager source package in Wily:
  New
Status in lxc source package in Wily:
  Fix Released
Status in lxcfs source package in Wily:
  New
Status in docker package in Debian:
  Fix Released

Bug description:
  Once systemd 226 is installed in an unprivileged Debian Sid container,
  lxc-attach no-longer functions:

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  % journalctl -u cgmanager | tail -n 1
  Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: 
pid 21918 (uid 1000 gid 1000) may not write to 
/run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks

  
  Full walkthrough:

  % lxc-create -n siddy -t download -- -d debian -r sid -a amd64
  Using image from local cache
  Unpacking the rootfs
  ...

  % lxc-start -n siddy
  % lxc-attach -n siddy

  root@siddy:/# apt-get update
  Get:1 http://http.debian.net sid InRelease [253 kB]
  ...
  Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB]

  Fetched 13.2 MB in 3s (3789 kB/s) 
 
  Reading package lists... Done

  
  root@siddy:/# apt-get install systemd
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libsystemd0
  Suggested packages:
systemd-ui systemd-container
  Recommended packages:
libpam-systemd dbus
  The following packages will be upgraded:
libsystemd0 systemd
  2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded.
  Need to get 3668 kB of archives.
  After this operation, 1100 kB disk space will be freed.
  Do you want to continue? [Y/n] 
  Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB]
  Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB]
  ...
  Setting up systemd (226-2) ...
  Installing new version of config file 
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.login1.conf ...
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid 
argument)
  The value of the capability argument is not permitted for a file. Or the file 
is not a regular (non-symlink) file
  Failed to execute operation: File exists
  Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 
...

  root@siddy:/# exit

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error 

[Touch-packages] [Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.0.8-0ubuntu0.3

---
lxc (1.0.8-0ubuntu0.3) trusty; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)

lxc (1.0.8-0ubuntu0.2) trusty; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.0.8-0ubuntu0.1) trusty; urgency=medium

  * New upstream bugfix release. (MRE tracking bug: LP: #1514623)
(LP: #1429140)
- Changelog at: https://linuxcontainers.org/lxc/news/
  * Drop proxy detection from the autopkgtest exercise script.
  * Add patch:
- 0001-Trusty-Swap-out-the-CVE-2015-1335-fix-with-the-trust.patch
  This is a patch by Serge Hallyn to cope with the trusty 3.13 kernel.
  It updates the upstream CVE fix to the version which trusty ended
  up with after the few round of fixes.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:42:07
-0500

** Changed in: lxc (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1335

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

Title:
  LXC's preserve_ns fails on < 3.8 kernels

Status in Canonical System Image:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
  Test case: Try starting an LXC container on an affected kernel
  Regression potential: Can't really get any worse. Change has been reviewed 
and tested upstream.

  == Original bug report ==
  ubuntu-touch/devel-proposed/mako 350

  After flashing the device the boot hangs on the vendor logo.
  There is no crash file on the device but it seems that the android container 
fails to start.

  There is the following error in syslog
  Nov 17 08:33:15 ubuntu-phablet kernel: [8.694826] init: 
lxc-android-config main process (918) terminated with status 255

  and in upstart/android.log:
    lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
    lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
    lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

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

[Touch-packages] [Bug 1510619] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1510619

Title:
  Wily: add machine fails using kvm and lxcbr0

Status in juju-core:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  Juju fails to start a machine after add-machine takes place.

  My environments.yaml:

  local:
type: local
container: kvm
network-bridge: lxcbr0

  Status output:

  ubuntu@ancient-spot:~$ juju status
  environment: local
  machines:
"0":
  agent-state: started
  agent-version: 1.24.7.1
  dns-name: localhost
  instance-id: localhost
  series: wily
  state-server-member-status: has-vote
"1":
  agent-state: pending
  instance-id: ubuntu-local-machine-1
  series: wily
  hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M

  debug log:

  http://paste.ubuntu.com/12980615/

  
  I never see anything in the logs which indicate machine-1 is being deployed 
or what else could be going on with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions

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

[Touch-packages] [Bug 1514623] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1514623

Title:
  New upstream bugfix release 1.0.8 (LXC MRE)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  We have released LXC 1.0.8 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

[Touch-packages] [Bug 1502756] Re: Media player crashes when volume is increased on Headphones

[Krishna]

Device: BQ Aquaris E5
Version: Saw this issue on both OTA 7 & OTA 8

Yes, this issue similar to bug #1504065.

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

Title:
  Media player crashes when volume is increased on Headphones

Status in mediaplayer-app package in Ubuntu:
  Incomplete

Bug description:
  When on earphones I tried increasing the volume to maximum, I get a
  kind of popup in the background and immediately gets superseded by  a
  message "High volume may damage your hearing" and then the media
  player crashes. I cannot play any video again until I either restart
  my phone or goto Music app then accept the popup and increase the
  volume.

  After using the phone for a week, I encountered this scenario at least
  5 times.

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

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

[Touch-packages] [Bug 1517107] Re: $PATH is getting clobbered when starting a container with Upstart

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  $PATH is getting clobbered when starting a container with Upstart

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC 1.1 and higher mangles the process env to be able to re-title 
itself, breaking the environment for sub-processes in the process
  Test case: Spawn a container and check /proc/self/environ
  Regression potential: Worst case scenario is we stamp on a different part of 
the process memory leading to similar but different breakage. It's been tested 
not to be the case though, change comes from upstream.

  == Original bug report ==
  I have a script using the Python3 LXC API that starts up a container.  If I 
use an Upstart job to call the script, the $PATH env var is getting clobbered 
and the container fails to start.

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

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

[Touch-packages] [Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3

---
lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.10.2) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.10.1) wily-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1441068, LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:40:28
-0500

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

Title:
  Wily: add machine fails using kvm and lxcbr0

Status in juju-core:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  Juju fails to start a machine after add-machine takes place.

  My environments.yaml:

  local:
type: local
container: kvm
network-bridge: lxcbr0

  Status output:

  ubuntu@ancient-spot:~$ juju status
  environment: local
  machines:
"0":
  agent-state: started
  agent-version: 1.24.7.1
  dns-name: localhost
  instance-id: localhost
  series: wily
  state-server-member-status: has-vote
"1":
  agent-state: pending
  instance-id: ubuntu-local-machine-1
  series: wily
  hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M

  debug log:

  http://paste.ubuntu.com/12980615/

  
  I never see anything in the logs which indicate machine-1 is being deployed 
or what else could be going on with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions

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

[Touch-packages] [Bug 1517107] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1517107

Title:
  $PATH is getting clobbered when starting a container with Upstart

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC 1.1 and higher mangles the process env to be able to re-title 
itself, breaking the environment for sub-processes in the process
  Test case: Spawn a container and check /proc/self/environ
  Regression potential: Worst case scenario is we stamp on a different part of 
the process memory leading to similar but different breakage. It's been tested 
not to be the case though, change comes from upstream.

  == Original bug report ==
  I have a script using the Python3 LXC API that starts up a container.  If I 
use an Upstart job to call the script, the $PATH env var is getting clobbered 
and the container fails to start.

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

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

[Touch-packages] [Bug 1521262] Re: Clock size in panel is smaller when showing only the time than when also showing date

[Will Cooke]

Clock and date showing "normal" font size

** Attachment added: "clock_and_date.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1521262/+attachment/4527651/+files/clock_and_date.png

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

Title:
  Clock size in panel is smaller when showing only the time than when
  also showing date

Status in ubuntu-font-family-sources package in Ubuntu:
  New

Bug description:
  After the Ubuntu font upgrade the clock in the panel seems to be
  smaller than it was.

  If I switch the clock to also show the date then the font size goes
  back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 30 16:40:07 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-11-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1521262/+subscriptions

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

[Touch-packages] [Bug 1413333] Re: mediaplayer-app should close after certain error dialogs are cleared by the user

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  mediaplayer-app should close after certain error dialogs are cleared
  by the user

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  After trying to play a .wmv with mediaplayer-app, it currently
  presents the error dialog that says "Video format not supported."
  After the user presses "Close", mediaplayer-app should quit. It should
  also do this for the message "Fail to open the source video." error.

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

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

[Touch-packages] [Bug 1377918] Re: Typo in string: There are not the appropriate permissions to play a media resource.

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Typo in string: There are not the appropriate permissions to play a
  media resource.

Status in Ubuntu UX:
  New
Status in mediaplayer-app package in Ubuntu:
  In Progress

Bug description:
  "There are not the appropriate permissions to play a media resource."
  src/qml/player/VideoPlayer.qml:241

  This is not an English sentence. Maybe you mean the following?

  "You don't have the appropriate permissions to play a media resource."

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

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

[Touch-packages] [Bug 1312659] Re: [desktop] Toolbar is not easy to reveal

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  [desktop] Toolbar is not easy to reveal

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  When running the application in desktop mode there are several
  problems with the toolbar.

  1) When opening the application the toolbar is hidden and difficult to
  reveal (it reveals with a click on the main frame, which is not
  consistent with the rest of the applications). It should be shown by
  default.

  2) When a file is stopped the toolbar should show, hiding when a file
  is playing.

  3) Moving the cursor (or touching the screen) while a file is playing,
  should be enough to reveal the toolbar

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

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

[Touch-packages] [Bug 1521262] [NEW] Clock size in panel is smaller when showing only the time than when also showing date

[Will Cooke]

Public bug reported:

After the Ubuntu font upgrade the clock in the panel seems to be smaller
than it was.

If I switch the clock to also show the date then the font size goes back
to normal.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 30 16:40:07 2015
Dependencies:
 
InstallationDate: Installed on 2015-11-11 (19 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
PackageArchitecture: all
SourcePackage: ubuntu-font-family-sources
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-font-family-sources (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Clock size in panel is smaller when showing only the time than when
  also showing date

Status in ubuntu-font-family-sources package in Ubuntu:
  New

Bug description:
  After the Ubuntu font upgrade the clock in the panel seems to be
  smaller than it was.

  If I switch the clock to also show the date then the font size goes
  back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 30 16:40:07 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-11-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1521262/+subscriptions

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

[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts

[Iain Lane]

Then it's a problem with the regular font itself and not Arabic, thanks
for confirming.

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

Title:
  New font uses Arabic-sized figures in Latin contexts

Status in Ubuntu Font Family:
  New
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Upgrade of ubuntu fonts  causes fonts to look as in attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 28 12:34:43 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-10-29 (30 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions

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

[Touch-packages] [Bug 1521262] Re: Clock size in panel is smaller when showing only the time than when also showing date

[Will Cooke]

Clock on its own with smaller font

** Attachment added: "clock_only.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1521262/+attachment/4527650/+files/clock_only.png

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

Title:
  Clock size in panel is smaller when showing only the time than when
  also showing date

Status in ubuntu-font-family-sources package in Ubuntu:
  New

Bug description:
  After the Ubuntu font upgrade the clock in the panel seems to be
  smaller than it was.

  If I switch the clock to also show the date then the font size goes
  back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.84~mono0.83+arabicfontconfig-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov 30 16:40:07 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-11-11 (19 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1521262/+subscriptions

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

[Touch-packages] [Bug 1415075] Re: Poor English for some of the error dialog messages

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Poor English for some of the error dialog messages

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  The following English error dialog messages are poor English and
  should be fixed as follows:

  1. "Fail to open the source video." -> "Failure to open source media."

  2. "Video format not supported." -> "Media format is not supported."

  3. "There are not the appropriate permissions to play a media
  resource." -> "Insufficient permissions to play the media resource."

  4. "Fail to connect with playback backend." -> "Failure to connect to
  playback backend."

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

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

[Touch-packages] [Bug 1341956] Re: test_no_video_dialog_visible fails on utopic

[Sebastien Bacher]

** Changed in: mediaplayer-app
   Status: In Progress => Fix Released

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

Title:
  test_no_video_dialog_visible fails on utopic

Status in mediaplayer-app:
  Fix Released
Status in mediaplayer-app package in Ubuntu:
  Fix Released

Bug description:
  This test is failing for me and for jenkins.

  _StringException: Empty attachments:
process-stdout

  process-return-code: {{{-15}}}
  process-stderr: {{{
  Testability driver loaded. Wire protocol version is "1.4".
  File not found:  QUrl( "file:///usr/share/mediaplayer-app/videos/" )  true 
false
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  UCUriHandler: Empty "APP_ID" environment variable, ignoring.

  ** (mediaplayer-app:5395): WARNING **: Unable to register app: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID
  }}}

  test-log: {{{
  15:02:25.603 INFO globals:58 - 

  15:02:25.603 INFO globals:59 - Starting test 
mediaplayer_app.tests.test_player.TestPlayer.test_no_video_dialog_visible (with 
mouse)
  15:02:25.603 DEBUG globals:158 - Starting: ['/usr/bin/recordmydesktop', 
'--no-sound', '--no-frame', '-o', 
'/var/local/autopilot//artifacts/mediaplayer_app.tests.test_player.TestPlayer.test_no_video_dialog_visible
 (with mouse).ogv']
  15:02:25.605 ERROR content:49 - Could not add content object 'None' due to IO 
Error: [Errno 13] Permission denied: '/var/log/syslog'
  15:02:25.739 INFO testcase:258 - Attempting to launch application 
'mediaplayer-app' with arguments '-w /usr/share/mediaplayer-app/videos/' as a 
normal process
  15:02:25.756 INFO _launcher:255 - Launching process: 
['/usr/bin/mediaplayer-app', '-testability', '-w', 
'/usr/share/mediaplayer-app/videos/']
  15:02:27.528 DEBUG dbus:433 - Selecting objects of type QQuickView with 
attributes: {}
  15:02:37.603 INFO _launcher:368 - waiting for process to exit.
  15:02:37.604 INFO _launcher:391 - Killing process 5395
  }}}

  Traceback (most recent call last):
File 
"/usr/lib/python2.7/dist-packages/mediaplayer_app/tests/test_player.py", line 
27, in setUp
  self.main_window.get_qml_view().visible, Eventually(Equals(True)))
File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 406, in 
assertThat
  raise mismatch_error
  MismatchError: After 10.0 seconds test on QQuickView.visible failed: True != 
dbus.Boolean(False, variant_level=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediaplayer-app/+bug/1341956/+subscriptions

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

[Touch-packages] [Bug 1520568] Re: All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

[Chad Miller]

Thank you bq.

Hrm, it's error -12218 SSL_ERROR_ENCRYPTION_FAILURE

"Bulk data encryption algorithm failed in selected cipher suite."


** Changed in: nss (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  All queries fails when 'google' is used: ERR_SSL_PROTOCOL_ERROR

Status in chromium-browser package in Ubuntu:
  New
Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Latest libnss3 upgrade have broken all the browser's queries; no
  matter of which is used. For example: url auto-completion fails

  ERR_SSL_PROTOCOL_ERROR
  Unable to make a secure connection to the server. This may be a problem with 
the server or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libnss3 2:3.21-1ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-0.8-generic 4.3.0
  Uname: Linux 4.3.0-0-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov 27 13:50:26 2015
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1356826] Re: [Feature] Content hub integration as a destination of videos

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  [Feature] Content hub integration as a destination of videos

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Media player should integrate with content hub so that:
  1. Apps that want to export a video through content hub will be able to send 
it to media player.
  2. When opening media player without a video, media player can present the 
ContentPeerPicker to let the user choose a video and play it, instead of 
showing an error message.

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

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

[Touch-packages] [Bug 1356826] Re: [Feature] Content hub integration as a destination of videos

[Launchpad Bug Tracker]

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

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

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

Title:
  [Feature] Content hub integration as a destination of videos

Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  Media player should integrate with content hub so that:
  1. Apps that want to export a video through content hub will be able to send 
it to media player.
  2. When opening media player without a video, media player can present the 
ContentPeerPicker to let the user choose a video and play it, instead of 
showing an error message.

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

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

[Touch-packages] [Bug 1427816] Re: Pause icon on toolbar does not switch to play icon when headphones are disconnected and playback is auto-paused

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

** Changed in: mediaplayer-app (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Pause icon on toolbar does not switch to play icon when headphones are
  disconnected and playback is auto-paused

Status in mediaplayer-app package in Ubuntu:
  Fix Released

Bug description:
  1. Play a video with mediaplayer-app from the video scope.
  2. Plug in pair of headphones.
  3. Unplug the headphones and notice that playback automatically pauses.
  4. The play/pause icon in the toolbar remains showing the pause icon when it 
should have switched to showing the play icon.

  Bug is on RTM stable build #19.

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

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

[Touch-packages] [Bug 1481236] Re: There is a whole grey/blue page after video is playing out

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Medium => Low

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

Title:
  There is a whole grey/blue page after video is playing out

Status in camera-app:
  Invalid
Status in mediaplayer-app package in Ubuntu:
  Confirmed

Bug description:
  current build number: 80
  device name: arale
  channel: ubuntu-touch/devel-proposed/meizu.en
  last update: 2015-08-03 07:55:29
  version version: 80
  version ubuntu: 20150802
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

  Steps:
  1.Go to camera app
  2.Take a video from camera
  3.Swipe to the left and open the photoroll
  4.Play the video you just took
  5.After playing to its end the video will pause, press the screen 
  Expectation:
  It will be no change in the screen 

  Actual result:
  After step 5. the whole screen change to grey or blue

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

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

[Touch-packages] [Bug 1417950] Re: Wrongly reported "video not supported"

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => High

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

Title:
  Wrongly reported "video not supported"

Status in Media Hub:
  Invalid
Status in mediaplayer-app package in Ubuntu:
  Triaged
Status in Ubuntu RTM:
  Confirmed

Bug description:
  For some videos a window showing a "Video format not supported"
  message is shown. However, after pressing "Close" the video is shown
  normally, so the message is wrong.

  A couple of videos where this has been noticed:

  
http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/BigBuckBunny_DivX_HD720p_ASP.divx
  (video and audio are played here)

  http://samplemedia.linaro.org/Mmtest/media_api/video/H263_56_AMRNB_6.3gp
  (video is supported, but AMR audio not yet, that might be related to the bug)

  $ system-image-cli -i
  current build number: 80
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2015-01-28 13:36:03
  version version: 80
  version ubuntu: 20150128
  version device: 20150126
  version custom: 20150128

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1417950/+subscriptions

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

[Touch-packages] [Bug 1502756] Re: Media player crashes when volume is increased on Headphones

[Sebastien Bacher]

is the player really crashing or do you get bug #1504065 where the popup
stops the playing of the video?

** Changed in: mediaplayer-app (Ubuntu)
   Status: New => Incomplete

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

Title:
  Media player crashes when volume is increased on Headphones

Status in mediaplayer-app package in Ubuntu:
  Incomplete

Bug description:
  When on earphones I tried increasing the volume to maximum, I get a
  kind of popup in the background and immediately gets superseded by  a
  message "High volume may damage your hearing" and then the media
  player crashes. I cannot play any video again until I either restart
  my phone or goto Music app then accept the popup and increase the
  volume.

  After using the phone for a week, I encountered this scenario at least
  5 times.

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

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

[Touch-packages] [Bug 1485228] [NEW] Video not working when streaming to mediaplayer-app

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Video is not working (but audio is) when streaming to MX4 Ubuntu edition
using mediaplayer-app

I stream a film from an ubuntu server with vlc using the command:
vlc --intf ncurses file:///media/tvmedia/"film.avi" --sout 
'#transcode{vcodec=h264,acodec=mp3,ab=128,channels=2,samplerate=44100}:http{mux=ffmpeg{mux=flv},dst=:8081/}'
 --sout-keep

I can watch the stream on any computer but when I try to watch it on an Meizu 
MX4, Ubuntu Touch,  using the command "ubuntu-app-launch mediaplayer-app 
http://192.168.1.9:8081; the following happens:
- The mediaplayer starts
- The screen goes black
- When I touch the screen I get the controls at the bottom
- I hear the audio fine as the video plays
- The screen stays black

I have installed gstreamer1.0-libav

$system-image-cli --info
current build number: 3
device name: arale
channel: ubuntu-touch/stable/meizu.en
last update: 2015-07-26 09:51:33
version version: 3
version ubuntu: 20150720
version device: 20150709-8965e37
version custom: 20150716-819-8-42

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

** Affects: mediaplayer-app (Ubuntu)
 Importance: High
 Status: New

** Affects: media-hub (Ubuntu)
 Importance: High
 Status: New

** Affects: media-hub (Ubuntu RTM)
 Importance: High
 Status: New

-- 
Video not working when streaming to mediaplayer-app
https://bugs.launchpad.net/bugs/1485228
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1518331] [NEW] Media player pauses playback when loosing focus

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

While testing Unity8 in desktop mode on Nexus 4, "convergence"... I
noticed that apps do not get suspended when they are not selected, as
they do on the phone... this is great, and required for convergence,
obviously.  However, the Media Player does stop playing when it looses
focus, it appears to pause playback, rather than get suspended depending
on focus, so I think this is a flaw in the app, not the system.

** Affects: mediaplayer-app (Ubuntu)
 Importance: Low
 Status: New

-- 
Media player pauses playback when loosing focus
https://bugs.launchpad.net/bugs/1518331
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1518332] Re: Media player not registered with file manager as a handler for .MP4 files....

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** 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 mediaplayer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1518332

Title:
  Media player not registered with file manager as a handler for .MP4
  files

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

Bug description:
  I would expect to be able to open a .MP4 video from the file manager,
  and have it play in Media Player... but the it seems that Media Player
  is not an option for playback, only Gallery, which is not terribly
  suitable.

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

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

[Touch-packages] [Bug 1521256] [NEW] package apport 2.19.2-0ubuntu8 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

[Charly Bimminger]

Public bug reported:

I test Ubuntu virtual!
I don't really know ubuntu!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.19.2-0ubuntu8
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic i686
ApportVersion: 2.19.2-0ubuntu8
Architecture: i386
CrashReports: 600:0:115:348597:2015-11-24 23:36:18.742644071 +0100:2015-11-24 
23:36:19.742644071 +0100:/var/crash/apport.0.crash
Date: Tue Nov 24 23:36:19 2015
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
InstallationDate: Installed on 2015-10-27 (33 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151027)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.0.10.2ubuntu1
SourcePackage: apport
Title: package apport 2.19.2-0ubuntu8 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 2 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 xenial

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

Title:
  package apport 2.19.2-0ubuntu8 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 2 zurück

Status in apport package in Ubuntu:
  New

Bug description:
  I test Ubuntu virtual!
  I don't really know ubuntu!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.19.2-0ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic i686
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: i386
  CrashReports: 600:0:115:348597:2015-11-24 23:36:18.742644071 +0100:2015-11-24 
23:36:19.742644071 +0100:/var/crash/apport.0.crash
  Date: Tue Nov 24 23:36:19 2015
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 2 zurück
  InstallationDate: Installed on 2015-10-27 (33 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20151027)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: apport
  Title: package apport 2.19.2-0ubuntu8 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 2 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1518331] Re: Media player pauses playback when loosing focus

[Sebastien Bacher]

Thanks, sounds like something that should be fixed for convergence

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => Low

** Also affects: mediaplayer-app
   Importance: Undecided
   Status: New

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

Title:
  Media player pauses playback when loosing focus

Status in mediaplayer-app:
  New
Status in mediaplayer-app package in Ubuntu:
  New

Bug description:
  While testing Unity8 in desktop mode on Nexus 4, "convergence"... I
  noticed that apps do not get suspended when they are not selected, as
  they do on the phone... this is great, and required for convergence,
  obviously.  However, the Media Player does stop playing when it looses
  focus, it appears to pause playback, rather than get suspended
  depending on focus, so I think this is a flaw in the app, not the
  system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mediaplayer-app/+bug/1518331/+subscriptions

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

[Touch-packages] [Bug 1470332] Re: pause the video then slide the progress bar, continue play the video , the progress bar jump back a little.

[Sebastien Bacher]

Thanks, that's still an issue on current rc-proposed on a bq device,
it's not always doing it but often enough

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

** Changed in: mediaplayer-app (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  pause the video then slide the progress bar,continue play the video
  ,the  progress bar jump back a little.

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

Bug description:
  system-image-cli -i
  current build number: 41
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-07-01 10:28:01
  version version: 41
  version ubuntu: 20150630
  version device: 20150608-6e66f3c
  version custom: 20150602-731-5-32

  reproduce steps:
  1.play a video by mediaplayer
  2.pause the  video slide the progress bar
  3.continue play the progress bar again

  expect result:
  the progress bar continue to go forward

  actually result:
  after continue play the video the progress bar jump back a little.

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

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

[Touch-packages] [Bug 1518332] [NEW] Media player not registered with file manager as a handler for .MP4 files....

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I would expect to be able to open a .MP4 video from the file manager,
and have it play in Media Player... but the it seems that Media Player
is not an option for playback, only Gallery, which is not terribly
suitable.

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

-- 
Media player not registered with file manager as a handler for .MP4 files  
https://bugs.launchpad.net/bugs/1518332
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1506511] [NEW] Second video playback results in white screen when replaying from indicator-sound

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Test case.
- Record a short video (10 seconds) with the camera.
- Open video scope.
- Play recorded video in mediaplayer.
- After the video finishes playing, tap "play" in mediaplayer
  - The video must playback a second time.
- When the video is finished, open the indicator sound.
- Tap play control in indicator sound.

Expected result.
- Video starts playing, but a white image is displayed. Sound is reproduced.

Tested in arale with silo 55 (which is landing and will be available in
a later image).

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

** Affects: canonical-devices-system-image
 Importance: Undecided
 Assignee: John McAleely (john.mcaleely)
 Status: Confirmed

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

** Affects: ubuntu-ux
 Importance: High
 Assignee: James Mulholland (jamesjosephmulholland)
 Status: Triaged

** Affects: qtubuntu-media (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtubuntu-media (Ubuntu RTM)
 Importance: Undecided
 Status: New


** Tags: qa-silo
-- 
Second video playback results in white screen when replaying from 
indicator-sound
https://bugs.launchpad.net/bugs/1506511
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1481236] [NEW] There is a whole grey/blue page after video is playing out

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

current build number: 80
device name: arale
channel: ubuntu-touch/devel-proposed/meizu.en
last update: 2015-08-03 07:55:29
version version: 80
version ubuntu: 20150802
version device: 20150709-8965e37
version custom: 20150716-819-8-42

Steps:
1.Go to camera app
2.Take a video from camera
3.Swipe to the left and open the photoroll
4.Play the video you just took
5.After playing to its end the video will pause, press the screen 
Expectation:
It will be no change in the screen 

Actual result:
After step 5. the whole screen change to grey or blue

** Affects: camera-app
 Importance: Undecided
 Status: Invalid

** Affects: mediaplayer-app (Ubuntu)
 Importance: Low
 Status: Confirmed

-- 
There is a whole grey/blue page after video is playing out
https://bugs.launchpad.net/bugs/1481236
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1514344] Re: Upstream remaining bits and port to upstream QDeclarativePlaylist version

[Jim Hodapp]

Currently iterating with upstream to get this completed. The last major
bit is to get the syncControls() changes to pass the upstream unit test
from this patch: https://codereview.qt-project.org/#/c/127157/

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

Title:
  Upstream remaining bits and port to upstream QDeclarativePlaylist
  version

Status in Canonical System Image:
  Confirmed
Status in qtmultimedia-opensource-src package in Ubuntu:
  Triaged
Status in qtmultimedia-opensource-src package in Ubuntu RTM:
  In Progress

Bug description:
  Currently the qtmultimedia in stable overlay PPA contains several
  additions and changes compared to upstream qtmultimedia (5.6/5.7):
  https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-009/+files/qtmultimedia-opensource-
  src_5.4.1-1ubuntu18.debian.tar.xz

  The remaining additions should be upstreamed at https://codereview.qt-
  project.org/#/q/project:qt/qtmultimedia,n,z

  After the upstreaming is complete, since our version has changes that
  are different in upstream, our components should be ported to the
  upstream API instead.

  Qt Multimedia in Ubuntu should be updated respectively for versions
  5.4.1 (overlay) and 5.5.1 (xenial/PPA), with backports from latest
  upstream.

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

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

[Touch-packages] [Bug 1485228] Re: Video not working when streaming to mediaplayer-app

[Sebastien Bacher]

** Project changed: mediaplayer-app => mediaplayer-app (Ubuntu)

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

Title:
  Video not working when streaming to mediaplayer-app

Status in Canonical System Image:
  Incomplete
Status in media-hub package in Ubuntu:
  New
Status in mediaplayer-app package in Ubuntu:
  New
Status in media-hub package in Ubuntu RTM:
  New

Bug description:
  Video is not working (but audio is) when streaming to MX4 Ubuntu
  edition using mediaplayer-app

  I stream a film from an ubuntu server with vlc using the command:
  vlc --intf ncurses file:///media/tvmedia/"film.avi" --sout 
'#transcode{vcodec=h264,acodec=mp3,ab=128,channels=2,samplerate=44100}:http{mux=ffmpeg{mux=flv},dst=:8081/}'
 --sout-keep

  I can watch the stream on any computer but when I try to watch it on an Meizu 
MX4, Ubuntu Touch,  using the command "ubuntu-app-launch mediaplayer-app 
http://192.168.1.9:8081; the following happens:
  - The mediaplayer starts
  - The screen goes black
  - When I touch the screen I get the controls at the bottom
  - I hear the audio fine as the video plays
  - The screen stays black

  I have installed gstreamer1.0-libav

  $system-image-cli --info
  current build number: 3
  device name: arale
  channel: ubuntu-touch/stable/meizu.en
  last update: 2015-07-26 09:51:33
  version version: 3
  version ubuntu: 20150720
  version device: 20150709-8965e37
  version custom: 20150716-819-8-42

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

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

[Touch-packages] [Bug 1415075] [NEW] Poor English for some of the error dialog messages

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The following English error dialog messages are poor English and should
be fixed as follows:

1. "Fail to open the source video." -> "Failure to open source media."

2. "Video format not supported." -> "Media format is not supported."

3. "There are not the appropriate permissions to play a media resource."
-> "Insufficient permissions to play the media resource."

4. "Fail to connect with playback backend." -> "Failure to connect to
playback backend."

** Affects: mediaplayer-app (Ubuntu)
 Importance: Low
 Status: New

-- 
Poor English for some of the error dialog messages
https://bugs.launchpad.net/bugs/1415075
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1518332] Re: Media player not registered with file manager as a handler for .MP4 files....

[Launchpad Bug Tracker]

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

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

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

Title:
  Media player not registered with file manager as a handler for .MP4
  files

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

Bug description:
  I would expect to be able to open a .MP4 video from the file manager,
  and have it play in Media Player... but the it seems that Media Player
  is not an option for playback, only Gallery, which is not terribly
  suitable.

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

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

[Touch-packages] [Bug 1520772] Re: New font uses Arabic-sized figures in Latin contexts

[flocculant]

@laney - did that, no change, rebooted just in case, still no change

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

Title:
  New font uses Arabic-sized figures in Latin contexts

Status in Ubuntu Font Family:
  New
Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  Upgrade of ubuntu fonts  causes fonts to look as in attachments

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov 28 12:34:43 2015
  Dependencies:
   
  InstallationDate: Installed on 2015-10-29 (30 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/1520772/+subscriptions

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

[Touch-packages] [Bug 1377918] [NEW] Typo in string: There are not the appropriate permissions to play a media resource.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

"There are not the appropriate permissions to play a media resource."
src/qml/player/VideoPlayer.qml:241

This is not an English sentence. Maybe you mean the following?

"You don't have the appropriate permissions to play a media resource."

** Affects: mediaplayer-app (Ubuntu)
 Importance: Low
 Assignee: Jeffrey Flaker (jflaker)
 Status: In Progress

-- 
Typo in string: There are not the appropriate permissions to play a media 
resource.
https://bugs.launchpad.net/bugs/1377918
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mediaplayer-app in Ubuntu.

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

[Touch-packages] [Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  LXC's preserve_ns fails on < 3.8 kernels

Status in Canonical System Image:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
  Test case: Try starting an LXC container on an affected kernel
  Regression potential: Can't really get any worse. Change has been reviewed 
and tested upstream.

  == Original bug report ==
  ubuntu-touch/devel-proposed/mako 350

  After flashing the device the boot hangs on the vendor logo.
  There is no crash file on the device but it seems that the android container 
fails to start.

  There is the following error in syslog
  Nov 17 08:33:15 ubuntu-phablet kernel: [8.694826] init: 
lxc-android-config main process (918) terminated with status 255

  and in upstart/android.log:
    lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
    lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
    lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

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

[Touch-packages] [Bug 1514623] Re: New upstream bugfix release 1.0.8 (LXC MRE)

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.0.8-0ubuntu0.3

---
lxc (1.0.8-0ubuntu0.3) trusty; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)

lxc (1.0.8-0ubuntu0.2) trusty; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.0.8-0ubuntu0.1) trusty; urgency=medium

  * New upstream bugfix release. (MRE tracking bug: LP: #1514623)
(LP: #1429140)
- Changelog at: https://linuxcontainers.org/lxc/news/
  * Drop proxy detection from the autopkgtest exercise script.
  * Add patch:
- 0001-Trusty-Swap-out-the-CVE-2015-1335-fix-with-the-trust.patch
  This is a patch by Serge Hallyn to cope with the trusty 3.13 kernel.
  It updates the upstream CVE fix to the version which trusty ended
  up with after the few round of fixes.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:42:07
-0500

** Changed in: lxc (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-1335

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

Title:
  New upstream bugfix release 1.0.8 (LXC MRE)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  We have released LXC 1.0.8 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the eigth upstream bugfix release to hit trusty. The
  upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Xenial is now on LXC 1.1.5 (and 1.1.5 will hit vivid and wily as SRU)
  which bugfixes for 1.0.8 have been taken from.

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

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

[Touch-packages] [Bug 1497420] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1497420

Title:
  systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxcfs package in Ubuntu:
  Fix Released
Status in cgmanager source package in Vivid:
  New
Status in lxc source package in Vivid:
  Fix Released
Status in lxcfs source package in Vivid:
  New
Status in cgmanager source package in Wily:
  New
Status in lxc source package in Wily:
  Fix Released
Status in lxcfs source package in Wily:
  New
Status in docker package in Debian:
  Fix Released

Bug description:
  Once systemd 226 is installed in an unprivileged Debian Sid container,
  lxc-attach no-longer functions:

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  % journalctl -u cgmanager | tail -n 1
  Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: 
pid 21918 (uid 1000 gid 1000) may not write to 
/run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks

  
  Full walkthrough:

  % lxc-create -n siddy -t download -- -d debian -r sid -a amd64
  Using image from local cache
  Unpacking the rootfs
  ...

  % lxc-start -n siddy
  % lxc-attach -n siddy

  root@siddy:/# apt-get update
  Get:1 http://http.debian.net sid InRelease [253 kB]
  ...
  Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB]

  Fetched 13.2 MB in 3s (3789 kB/s) 
 
  Reading package lists... Done

  
  root@siddy:/# apt-get install systemd
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libsystemd0
  Suggested packages:
systemd-ui systemd-container
  Recommended packages:
libpam-systemd dbus
  The following packages will be upgraded:
libsystemd0 systemd
  2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded.
  Need to get 3668 kB of archives.
  After this operation, 1100 kB disk space will be freed.
  Do you want to continue? [Y/n] 
  Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB]
  Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB]
  ...
  Setting up systemd (226-2) ...
  Installing new version of config file 
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.login1.conf ...
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid 
argument)
  The value of the capability argument is not permitted for a file. Or the file 
is not a regular (non-symlink) file
  Failed to execute operation: File exists
  Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 
...

  root@siddy:/# exit

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net]
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 18 20:19:58 2015
  SourcePackage: lxc
  UpgradeStatus: Upgraded to wily on 2015-08-28 (20 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: 

[Touch-packages] [Bug 1466458] Re: template 'none' doesn't work with lxc-create

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  template 'none' doesn't work with lxc-create

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  Hi,

  The man page lxc-create(1) says that with the '-t' option to specify a
  template '"none" can be used to force lxc-create to skip rootfs
  creation'.  This does not appear to work.

  root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none
  lxc_container: lxccontainer.c: get_template_path: 867 No such file or 
directory - bad template: none
  lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none
  lxc_container: lxc_create.c: main: 271 Error creating container test.lol

  There is no template in the templates dir corresponding to the 'none'
  template.  I've looked through the upstream tarballs from releases
  0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in
  any.  Might be just a documentation mistake, I guess.  Could be a
  missing template, or maybe 'none' has a special meaning to the lxc-
  create binary; I haven't looked yet.

  I'll dig a little further.

  I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 .

  thanks,
  Kevin

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:56:34 2015
  InstallationDate: Installed on 2012-01-13 (1251 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

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

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

[Touch-packages] [Bug 1504496] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504496

Title:
  package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Committed

Bug description:
  A dist-upgrade failed in the maintainer scripts while trying to
  restart the lxc networking, I think:

  Reading package lists... Done
  The following NEW packages will be installed:
linux-image-3.19.0-31-generic{a} linux-image-extra-3.19.0-31-generic{a} 
linux-signed-image-3.19.0-31-generic{a} 
  The following packages will be upgraded:
juju juju-core juju-local liblxc1 linux-image-generic linux-libc-dev 
linux-signed-image-generic 
lxc lxc-templates mutt python3-lxc 
  The following packages are RECOMMENDED but will NOT be installed:
citadel-mta courier-mta dma dma:i386 esmtp-run exim4-daemon-heavy 
exim4-daemon-light 
lsb-invalid-mta masqmail msmtp-mta nullmailer opensmtpd postfix qmail-run 
sendmail-bin ssmtp 
xmail 
  11 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B/90.5 MB of archives. After unpacking 259 MB will be used.
  Do you want to continue? [Y/n/?] 
  (Reading database ... 357199 files and directories currently installed.)
  Preparing to unpack .../python3-lxc_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking python3-lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../lxc-templates_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking lxc-templates (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../liblxc1_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking liblxc1 (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Preparing to unpack .../lxc_1.1.4-0ubuntu0.1_amd64.deb ...
  Unpacking lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
  Selecting previously unselected package linux-image-3.19.0-31-generic.
  Preparing to unpack .../linux-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb 
...
  Done.
  Unpacking linux-image-3.19.0-31-generic (3.19.0-31.36) ...
  Selecting previously unselected package linux-image-extra-3.19.0-31-generic.
  Preparing to unpack 
.../linux-image-extra-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
  Unpacking linux-image-extra-3.19.0-31-generic (3.19.0-31.36) ...
  Preparing to unpack .../linux-image-generic_3.19.0.31.30_amd64.deb ...
  Unpacking linux-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
  Preparing to unpack .../linux-libc-dev_3.19.0-31.36_amd64.deb ...
  Unpacking linux-libc-dev:amd64 (3.19.0-31.36) over (3.19.0-30.34) ...
  Selecting previously unselected package linux-signed-image-3.19.0-31-generic.
  Preparing to unpack 
.../linux-signed-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
  Unpacking linux-signed-image-3.19.0-31-generic (3.19.0-31.36) ...
  Preparing to unpack .../linux-signed-image-generic_3.19.0.31.30_amd64.deb ...
  Unpacking linux-signed-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
  Preparing to unpack .../mutt_1.5.23-3ubuntu1_amd64.deb ...
  Unpacking mutt (1.5.23-3ubuntu1) over (1.5.23-3) ...
  Preparing to unpack .../juju-core_1.24.6-0ubuntu1~15.04.1_amd64.deb ...
  Unpacking juju-core (1.24.6-0ubuntu1~15.04.1) over 
(1.23.2-0ubuntu1~14.10.1~juju1) ...
  Preparing to unpack .../juju_1.24.6-0ubuntu1~15.04.1_all.deb ...
  Unpacking juju (1.24.6-0ubuntu1~15.04.1) over (1.23.2-0ubuntu1~14.10.1~juju1) 
...
  Preparing to unpack .../juju-local_1.24.6-0ubuntu1~15.04.1_all.deb ...
  Unpacking juju-local (1.24.6-0ubuntu1~15.04.1) over 
(1.23.2-0ubuntu1~14.10.1~juju1) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for doc-base (0.10.6) ...
  Processing 1 changed doc-base file...
  Registering documents with scrollkeeper...
  Processing triggers for gnome-menus (3.10.1-0ubuntu5) ...
  Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
  Processing triggers for bamfdaemon (0.5.1+15.04.20150202-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.58ubuntu1) ...
  Setting up liblxc1 (1.1.4-0ubuntu0.1) ...
  Setting up python3-lxc (1.1.4-0ubuntu0.1) ...
  Setting up lxc (1.1.4-0ubuntu0.1) ...
  Installing new 

[Touch-packages] [Bug 1517107] Re: $PATH is getting clobbered when starting a container with Upstart

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3

---
lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.10.2) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.10.1) wily-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1441068, LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:40:28
-0500

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

Title:
  $PATH is getting clobbered when starting a container with Upstart

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC 1.1 and higher mangles the process env to be able to re-title 
itself, breaking the environment for sub-processes in the process
  Test case: Spawn a container and check /proc/self/environ
  Regression potential: Worst case scenario is we stamp on a different part of 
the process memory leading to similar but different breakage. It's been tested 
not to be the case though, change comes from upstream.

  == Original bug report ==
  I have a script using the Python3 LXC API that starts up a container.  If I 
use an Upstart job to call the script, the $PATH env var is getting clobbered 
and the container fails to start.

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

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

[Touch-packages] [Bug 1504065] Re: Cannot play videos when a wired headphone is connected

[Launchpad Bug Tracker]

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 mediaplayer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1504065

Title:
  Cannot play videos when a wired headphone is connected

Status in Canonical System Image:
  New
Status in The Sound Menu:
  New
Status in mediaplayer-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When having a wired headset connected to the device, video playback
  keeps on being paused as soon as playback is started. Looks like some
  snap-decision notification is shown, but it's too short time to read
  what it actually says because it disappears again when the playback
  stops again.

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

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

[Touch-packages] [Bug 1436723] Re: Regression: Nested LXC is broken on Vivid

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

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

Title:
  Regression: Nested LXC is broken on Vivid

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released

Bug description:
  The nested LXC functionality seems to be broken on Vivid, at least
  with the following setup:

  Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC)

  What happens:

  The Inner LXC start command fails when trying to start with: 
http://pastebin.ubuntu.com/10682639/
  ( 631 cgroup error?  100 cgroups with this name already running seems to be 
the revelant error message).

  What is expected to happen:

  The inner LXC start command is expected to succeed and result in a
  running nested container.

  Steps to reproduce:

  - Install vivid server daily, update.
  - sudo apt-get install lxc
  - sudo lxc-create -n outer -t ubuntu -- --release trusty 
--mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER
  - sudo su
  - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> 
/var/lib/lxc/outer/config
  - exit
  - sudo lxc-start -n outer
  - (SSH to outer)
  - sudo apt-get update && sudo apt-get dist-upgrade
  - sudo apt-get install lxc
  - sudo lxc-create -n inner -t ubuntu -- --release trusty 
--mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER
  - sudo lxc-start -n inner

  Fails with: http://pastebin.ubuntu.com/10682639/
  Enabling debug logs for this action yields: 
http://pastebin.ubuntu.com/10682658/

  Control: The exact same scenario works on trusty and utopic. Tested by
  spinning up server installs (from isos) in KVMs and verifying
  manually.

  Any further log or information available on request, including KVM
  images demonstrating the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar 26 08:43:56 2015
  InstallationDate: Installed on 2015-03-12 (13 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1497420] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1497420

Title:
  systemd 226 (moving pid 1 into /init.scope cgroup) breaks lxc-attach

Status in cgmanager package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxcfs package in Ubuntu:
  Fix Released
Status in cgmanager source package in Vivid:
  New
Status in lxc source package in Vivid:
  Fix Released
Status in lxcfs source package in Vivid:
  New
Status in cgmanager source package in Wily:
  New
Status in lxc source package in Wily:
  Fix Released
Status in lxcfs source package in Wily:
  New
Status in docker package in Debian:
  Fix Released

Bug description:
  Once systemd 226 is installed in an unprivileged Debian Sid container,
  lxc-attach no-longer functions:

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  % journalctl -u cgmanager | tail -n 1
  Sep 18 20:20:44 astoria cgmanager[1169]: cgmanager:per_ctrl_move_pid_main: 
pid 21918 (uid 1000 gid 1000) may not write to 
/run/cgmanager/fs/none,name=systemd//user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope/tasks

  
  Full walkthrough:

  % lxc-create -n siddy -t download -- -d debian -r sid -a amd64
  Using image from local cache
  Unpacking the rootfs
  ...

  % lxc-start -n siddy
  % lxc-attach -n siddy

  root@siddy:/# apt-get update
  Get:1 http://http.debian.net sid InRelease [253 kB]
  ...
  Get:7 http://http.debian.net sid/non-free amd64 Packages [91.3 kB]

  Fetched 13.2 MB in 3s (3789 kB/s) 
 
  Reading package lists... Done

  
  root@siddy:/# apt-get install systemd
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libsystemd0
  Suggested packages:
systemd-ui systemd-container
  Recommended packages:
libpam-systemd dbus
  The following packages will be upgraded:
libsystemd0 systemd
  2 upgraded, 0 newly installed, 0 to remove and 47 not upgraded.
  Need to get 3668 kB of archives.
  After this operation, 1100 kB disk space will be freed.
  Do you want to continue? [Y/n] 
  Get:1 http://http.debian.net/debian/ sid/main libsystemd0 amd64 226-2 [242 kB]
  Get:2 http://http.debian.net/debian/ sid/main systemd amd64 226-2 [3426 kB]
  ...
  Setting up systemd (226-2) ...
  Installing new version of config file 
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh ...
  Installing new version of config file 
/etc/dbus-1/system.d/org.freedesktop.login1.conf ...
  addgroup: The group `systemd-journal' already exists as a system group. 
Exiting.
  Failed to set capabilities on file `/usr/bin/systemd-detect-virt' (Invalid 
argument)
  The value of the capability argument is not permitted for a file. Or the file 
is not a regular (non-symlink) file
  Failed to execute operation: File exists
  Removing obsolete conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 
...

  root@siddy:/# exit

  % lxc-attach -n siddy
  lxc-attach: cgmanager.c: lxc_cgmanager_enter: 698 call to 
cgmanager_move_pid_abs_sync failed: invalid request
  lxc-attach: cgmanager.c: cgm_attach: 1460 Failed to enter group 
/user.slice/user-1000.slice/session-1.scope/lxc/siddy/init.scope
  lxc-attach: attach.c: lxc_attach: 909 error communicating with child process

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lxc 1.1.3-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/lxc/lxc-net]
  ProcVersionSignature: Ubuntu 4.2.0-10.11-generic 4.2.0
  Uname: Linux 4.2.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 18 20:19:58 2015
  SourcePackage: lxc
  UpgradeStatus: Upgraded to wily on 2015-08-28 (20 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: 

[Touch-packages] [Bug 1466458] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1466458

Title:
  template 'none' doesn't work with lxc-create

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  Hi,

  The man page lxc-create(1) says that with the '-t' option to specify a
  template '"none" can be used to force lxc-create to skip rootfs
  creation'.  This does not appear to work.

  root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none
  lxc_container: lxccontainer.c: get_template_path: 867 No such file or 
directory - bad template: none
  lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none
  lxc_container: lxc_create.c: main: 271 Error creating container test.lol

  There is no template in the templates dir corresponding to the 'none'
  template.  I've looked through the upstream tarballs from releases
  0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in
  any.  Might be just a documentation mistake, I guess.  Could be a
  missing template, or maybe 'none' has a special meaning to the lxc-
  create binary; I haven't looked yet.

  I'll dig a little further.

  I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 .

  thanks,
  Kevin

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:56:34 2015
  InstallationDate: Installed on 2012-01-13 (1251 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

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

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

[Touch-packages] [Bug 1516971] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1516971

Title:
  LXC's preserve_ns fails on < 3.8 kernels

Status in Canonical System Image:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
  Test case: Try starting an LXC container on an affected kernel
  Regression potential: Can't really get any worse. Change has been reviewed 
and tested upstream.

  == Original bug report ==
  ubuntu-touch/devel-proposed/mako 350

  After flashing the device the boot hangs on the vendor logo.
  There is no crash file on the device but it seems that the android container 
fails to start.

  There is the following error in syslog
  Nov 17 08:33:15 ubuntu-phablet kernel: [8.694826] init: 
lxc-android-config main process (918) terminated with status 255

  and in upstart/android.log:
    lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
    lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
    lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1510619] Re: Wily: add machine fails using kvm and lxcbr0

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  Wily: add machine fails using kvm and lxcbr0

Status in juju-core:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  Juju fails to start a machine after add-machine takes place.

  My environments.yaml:

  local:
type: local
container: kvm
network-bridge: lxcbr0

  Status output:

  ubuntu@ancient-spot:~$ juju status
  environment: local
  machines:
"0":
  agent-state: started
  agent-version: 1.24.7.1
  dns-name: localhost
  instance-id: localhost
  series: wily
  state-server-member-status: has-vote
"1":
  agent-state: pending
  instance-id: ubuntu-local-machine-1
  series: wily
  hardware: arch=amd64 cpu-cores=1 mem=512M root-disk=8192M

  debug log:

  http://paste.ubuntu.com/12980615/

  
  I never see anything in the logs which indicate machine-1 is being deployed 
or what else could be going on with it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1510619/+subscriptions

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

[Touch-packages] [Bug 1516971] Re: LXC's preserve_ns fails on < 3.8 kernels

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3

---
lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.10.2) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.10.1) wily-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1441068, LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:40:28
-0500

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

Title:
  LXC's preserve_ns fails on < 3.8 kernels

Status in Canonical System Image:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  == SRU ==
  Rationale: LXC no longer starts on kernels > 3.2 and < 3.8
  Test case: Try starting an LXC container on an affected kernel
  Regression potential: Can't really get any worse. Change has been reviewed 
and tested upstream.

  == Original bug report ==
  ubuntu-touch/devel-proposed/mako 350

  After flashing the device the boot hangs on the vendor logo.
  There is no crash file on the device but it seems that the android container 
fails to start.

  There is the following error in syslog
  Nov 17 08:33:15 ubuntu-phablet kernel: [8.694826] init: 
lxc-android-config main process (918) terminated with status 255

  and in upstart/android.log:
    lxc-start 1447749195.286 ERRORlxc_start - start.c:preserve_ns:149 - 
No such file or directory - failed to open '/proc/1055/ns/mnt'
    lxc-start 1447749195.286 ERRORlxc_start - start.c:lxc_spawn:993 - 
failed to store namespace references
    lxc-start 1447749195.408 ERRORlxc_start - start.c:__lxc_start:1192 
- failed to spawn 'android'
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:344 - 
The container failed to start.
    lxc-start 1447749195.758 ERRORlxc_start_ui - lxc_start.c:main:348 - 
Additional information can be obtained by setting the --logfile and 
--logpriority options.

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

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

[Touch-packages] [Bug 1504065] Re: Cannot play videos when a wired headphone is connected

[Launchpad Bug Tracker]

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

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

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

Title:
  Cannot play videos when a wired headphone is connected

Status in Canonical System Image:
  New
Status in The Sound Menu:
  New
Status in mediaplayer-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When having a wired headset connected to the device, video playback
  keeps on being paused as soon as playback is started. Looks like some
  snap-decision notification is shown, but it's too short time to read
  what it actually says because it disappears again when the playback
  stops again.

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

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

[Touch-packages] [Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

** Changed in: lxc (Ubuntu Vivid)
   Status: Fix Committed => Fix Released

** Changed in: lxc (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  lxc-destroy fails on btrfs subvolumes

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  $ sudo lxc-destroy -n adt-vivid
  [sudo] password for martin: 
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs
  lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying 
rootfs for adt-vivid
  Destroying adt-vivid failed

  This is because the container rootfs has a btrfs subvolume:

  ID 557 gen 97073 top level 266 path @srv/lxc/adt-
  vivid/rootfs/var/lib/machines

  After "sudo btrfs subvolume delete /srv/lxc/adt-
  vivid/rootfs/var/lib/machines" I can remove the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:51:51 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1441068] Re: lxc-destroy fails on btrfs subvolumes

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3

---
lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.10.2) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.10.1) wily-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1441068, LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:40:28
-0500

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

Title:
  lxc-destroy fails on btrfs subvolumes

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  $ sudo lxc-destroy -n adt-vivid
  [sudo] password for martin: 
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var/lib
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs/var
  lxc_container: utils.c: _recursive_rmdir_onedev: 147 _recursive_rmdir_onedev: 
failed to delete /srv/lxc/adt-vivid/rootfs
  lxc_container: lxccontainer.c: container_destroy: 2050 Error destroying 
rootfs for adt-vivid
  Destroying adt-vivid failed

  This is because the container rootfs has a btrfs subvolume:

  ID 557 gen 97073 top level 266 path @srv/lxc/adt-
  vivid/rootfs/var/lib/machines

  After "sudo btrfs subvolume delete /srv/lxc/adt-
  vivid/rootfs/var/lib/machines" I can remove the container.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  7 11:51:51 2015
  EcryptfsInUse: Yes
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxc.conf: lxc.lxcpath = /srv/lxc

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

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

[Touch-packages] [Bug 1503330] Re: New upstream bugfix release 1.1.4 (LXC MRE)

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.04.3

---
lxc (1.1.5-0ubuntu0.15.04.3) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.04.2) vivid-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.04.1) vivid-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1436723, LP: #1441068, LP: #1504496,
 LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:41:23
-0500

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

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

Title:
  New upstream bugfix release 1.1.4 (LXC MRE)

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released

Bug description:
  We have released LXC 1.1.4 upstream:
  https://linuxcontainers.org/lxc/news

  This will be the first and last upstream bugfix release to hit vivid.
  The upstream changes are detailed at the URL above.

  The MRE was reviewed by Martin Pitt here:
  https://lists.ubuntu.com/archives/technical-
  board/2014-April/001869.html

  As for testing, this version went through both automated testing (all
  the tests present in lxc-tests + the python3 API tests) as well as
  manual testing done by myself, LXC contributors and LXC users who've
  been building the git stable branch for a while now.

  Until now, vivid was on a patched version of 1.1.2, basically 1.1.2 +
  security updates. LXC 1.1.4 contains all those same security updates,
  a bunch more bugfixes (160 or so when combining 1.1.3 and 1.1.4
  together). This also makes the LXC in both vivid and wily to be
  identical, simplifying maintenance until vivid goes EOL.

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

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

[Touch-packages] [Bug 1515463] Re: Broken juju LXC deployments

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 1.1.5-0ubuntu0.15.10.3

---
lxc (1.1.5-0ubuntu0.15.10.3) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix preserve_ns to work on < 3.8 kernels. (LP: #1516971)
- Fix process title rewrite to not mangle the environment. (LP: #1517107)

lxc (1.1.5-0ubuntu0.15.10.2) wily-proposed; urgency=medium

  * Cherry-pick from upstream:
- Fix ubuntu-cloud template to detect compression algorithm instead
  of hardcoding xz. Also update list of supported releases and use trusty
  as the fallback release. (LP: #1515463)
  * Update lxc-tests description to make it clear that this package is
meant to be used by developers and by automated testing.

lxc (1.1.5-0ubuntu0.15.10.1) wily-proposed; urgency=medium

  * New upstream bugfix release (MRE) (1.1.5)
(LP: #1497420, LP: #1441068, LP: #1466458, LP: #1510619)
  * Drop proxy detection from the autopkgtest exercise script.

 -- Stéphane Graber   Wed, 18 Nov 2015 13:40:28
-0500

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

Title:
  Broken juju LXC deployments

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released
Status in lxc source package in Xenial:
  Fix Released

Bug description:
  I've just tried using juju to deploy to a container with trusty-
  proposed repo enabled, and I get an error message about 'failed to
  retrieve the template to clone'.  The underlying error appears to be:

tar --numeric-owner -xpJf 
/var/cache/lxc/cloud-trusty/ubuntu-14.04-server-cloudimg-amd64-root.tar.gz;
xz: (stdin): File format not recognized; tar: Child returned status 1; tar:
Error is not recoverable: exiting now;

  This seems to be fairly obvious, trying to use xz on a tar.gz file is
  never going to work.

  The change appears to be from
  https://github.com/lxc/lxc/commit/27c278a76931bfc4660caa85d1942ca91c86e0bf,
  it assumes everything passed into it will be a .tar.xz file.

  This appears to be a conflict between the template expecting a .tar.xz
  file, and juju providing it a .tar.gz file.  You can see what juju is
  providing from:

$ ubuntu-cloudimg-query trusty released amd64 --format %{url}

https://cloud-images.ubuntu.com/server/releases/trusty/release-20151105/ubuntu-14.04-server-cloudimg-amd64.tar.gz

  From the juju deployed host:
  $ apt-cache policy lxc-templates
  lxc-templates:
Installed: 1.0.8-0ubuntu0.1
Candidate: 1.0.8-0ubuntu0.1
Version table:
   *** 1.0.8-0ubuntu0.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  From the host running juju:
  $ apt-cache policy juju-core
  juju-core:
Installed: 1.22.8-0ubuntu1~14.04.1
Candidate: 1.25.0-0ubuntu1~14.04.1~juju1
Version table:
   1.25.0-0ubuntu1~14.04.1~juju1 0
  500 http://ppa.launchpad.net/juju/proposed/ubuntu/ trusty/main amd64 
Packages
   *** 1.22.8-0ubuntu1~14.04.1 0
  400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 
Packages
  100 /var/lib/dpkg/status

  All machine involved are running trusty:

  $ lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  Please let me know if you need any more information.

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

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

[Touch-packages] [Bug 1466458] Update Released

[Stéphane Graber]

The verification of the Stable Release Update for lxc 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 lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1466458

Title:
  template 'none' doesn't work with lxc-create

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Vivid:
  Fix Released
Status in lxc source package in Wily:
  Fix Released

Bug description:
  Hi,

  The man page lxc-create(1) says that with the '-t' option to specify a
  template '"none" can be used to force lxc-create to skip rootfs
  creation'.  This does not appear to work.

  root@somehost:/var/lib/lxc# lxc-create -n test.lol -t none
  lxc_container: lxccontainer.c: get_template_path: 867 No such file or 
directory - bad template: none
  lxc_container: lxccontainer.c: lxcapi_create: 1264 bad template: none
  lxc_container: lxc_create.c: main: 271 Error creating container test.lol

  There is no template in the templates dir corresponding to the 'none'
  template.  I've looked through the upstream tarballs from releases
  0.5.0, 0.6.0, ... , 1.0.0, 1.1.0, and there is no 'none' template in
  any.  Might be just a documentation mistake, I guess.  Could be a
  missing template, or maybe 'none' has a special meaning to the lxc-
  create binary; I haven't looked yet.

  I'll dig a little further.

  I'm using lxc 1.0.7-0ubuntu0.1 on Ubuntu 14.04 .

  thanks,
  Kevin

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lxc 1.1.2-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun 18 11:56:34 2015
  InstallationDate: Installed on 2012-01-13 (1251 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: lxc
  UpgradeStatus: Upgraded to vivid on 2015-05-14 (34 days ago)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

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

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