[Bug 1428490] Re: AppArmor vs unix socket inside LXC containers

[John Johansen]

Toby,

what distro, release and kernel are you using?

And would you be willing to try a custom test kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1428490

Title:
  AppArmor vs unix socket inside LXC containers

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1428490] Re: AppArmor vs unix socket inside LXC containers

[John Johansen]

Toby,

what distro, release and kernel are you using?

And would you be willing to try a custom test kernel?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1428490

Title:
  AppArmor vs unix socket inside LXC containers

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1539491] Re: Update to 2016a

[Andrei Urvantcev]

Debian already built a package:
https://packages.debian.org/en/sid/tzdata

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539491

Title:
  Update to 2016a

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1526322] Re: Lock screen shows unnecessary warning about numlock

[Egmont Koblinger]

I see no rationale behind anyone every trying to move the cursor (left,
right, home, end...) while typing their password.

Typing digits as part of the password is a reasonable thing.

_If_ there's a warning at all (which I agree with the original report
that doesn't make too much sense and just adds unnecessary noise) then
the warning should be presented when NumLock is _OFF_.

Also, lightdm (or whichever the default login manager is) should be made
consistent, currently that one doesn't display a warning on numlock.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1526322

Title:
  Lock screen shows unnecessary warning about numlock

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Timo Aaltonen]

Redhat is not the upstream

And since it's fixed in xenial I'm closing this. Upgrade or bisect the
driver and propose patches.

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507255

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1427275] Re: clean cloud images of python2

[Matthias Klose]

vim is now built for python3. added some -py2 variants for those who
need them.


** Changed in: vim (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1427275

Title:
  clean cloud images of python2

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1427275] Re: clean cloud images of python2

[Matthias Klose]

vim is now built for python3. added some -py2 variants for those who
need them.


** Changed in: vim (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427275

Title:
  clean cloud images of python2

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547249] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:__gnu_cxx::__exchange_and_add:__gnu_cxx::__exchange_and_add_dispatch:std::string::_Rep::_M_dispose:std::basic_string:oxide::ResourceD

[Timo Jyrinki]

oxide::ResourceDispatcherHostDelegate::DownloadStarting

** Package changed: qtdeclarative-opensource-src (Ubuntu) => oxide-qt
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547249

Title:
  /usr/lib/arm-linux-
  
gnueabihf/qt5/bin/qmlscene:11:__gnu_cxx::__exchange_and_add:__gnu_cxx::__exchange_and_add_dispatch:std::string::_Rep::_M_dispose:std::basic_string:oxide::ResourceDispatcherHostDelegate::DownloadStarting

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547361] [NEW] test

[maozhou]

Public bug reported:

test bug report

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547361

Title:
  test

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547360] [NEW] Unity 8 doesnt respect Qt::CursorShape

[Dubstar_04]

Public bug reported:

Unity 8 doesn't respect the cursor shape and the cursor remains a
standard Qt::ArrowCursor regardless of what it is set to.

http://doc.qt.io/qt-5/qt.html#CursorShape-enum

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547360

Title:
  Unity 8 doesnt respect Qt::CursorShape

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547356] [NEW] cant finish wily update it says missing small mirrors

[ross]

Public bug reported:

rther information:

ProblemType: Bug
DistroRelease: Zorin OS 10
Package: ubuntu-release-upgrader-core 1:15.04.14.1 [origin: unknown]
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CrashDB: ubuntu
Date: Fri Feb 19 01:10:33 2016
InstallationDate: Installed on 2015-07-31 (202 days ago)
InstallationMedia: Zorin 9 trusty - Release amd64 (20140729)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to vivid on 2016-02-19 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2016-02-19 01:08:22.084195
 Log time: 2016-02-19 01:08:35.126430
 Log time: 2016-02-19 01:09:17.843566
 Log time: 2016-02-19 01:10:39.787156
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade third-party-packages vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547356

Title:
  cant finish wily update it says missing small mirrors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1543151] Re: Xorg assert failure: *** Error in `/usr/lib/xorg/Xorg': free(): corrupted unsorted chunks: 0x0000560822eb9960 ***

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1543180, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566894/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566897/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566904/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566906/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566907/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566908/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1543151/+attachment/4566909/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1543180

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1543151

Title:
  Xorg assert failure: *** Error in `/usr/lib/xorg/Xorg': free():
  corrupted unsorted chunks: 0x560822eb9960 ***

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547356] Re: cant finish wily update it says missing small mirrors

[ross]

rther information:
shit fuked pc wont let me paste error report Y? do fukers xpect us to know 
geekenese wtf jus send me the whatever i need a driver i constantly get bit 
torrentz its the main reason to own pc 

** Attachment added: "idk how to use or install"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1547356/+attachment/4575277/+files/ubuntu-release-upgrader_15.10.13.tar%20%281%29.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547356

Title:
  cant finish wily update it says missing small mirrors

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1542323] Re: thunar crashed with SIGSEGV in thunar_file_compare_by_name()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1495409, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564504/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564506/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564509/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564510/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564511/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564512/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1542323/+attachment/4564513/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1495409

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542323

Title:
  thunar crashed with SIGSEGV in thunar_file_compare_by_name()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547097] Re: Sync php-imagick 3.4.0~rc6-1 (universe) from Debian unstable (main)

[Stefan Winter]

php-imagick is a useful and important package. Right now, if a project
wants to make use of it on a xenial server, one is forced to downgrade
to php5 (because there is php5-imagick but no php7.0-imagick). I would
love to upgrade to php7, but this missing package is holding me back.
The 3.4.0rc versions support php7, so there's no reason to hold back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547097

Title:
  Sync php-imagick 3.4.0~rc6-1 (universe) from Debian unstable (main)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547097] Re: Sync php-imagick 3.4.0~rc6-1 (universe) from Debian unstable (main)

[Launchpad Bug Tracker]

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

** Changed in: php-imagick (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547097

Title:
  Sync php-imagick 3.4.0~rc6-1 (universe) from Debian unstable (main)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1546847] Re: Fonts-droid has been deprecated and removed

[zhangchao]

fonts-noto-cjk is too big to copy in initrd，
 use fonts-droid-fallback ，when   fonts-droid  changed its name

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546847

Title:
  Fonts-droid has been deprecated and removed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547355] [NEW] Anthy doesn't work properly after using google translate

[Samantha]

Public bug reported:

I expected that switching from google translate on firefox or chrome to
a text editor, anthy would continue to underline words and convert roman
text to hiragana and kanji

instead... after using google translate, the anthy icon still shows in
the panel, but text is not underlined or converted to japanese.
(although the bug is a bit intermittent and happens about 50% of the
time, so try it two or three times to see what I mean)

Open a text application, e.g. Writer or Anki or Pluma Text Editor or Skype.
press Ctrl Space. Anthy is now on and shows in the panel (on mint)
Type something and hit space.

NOw switch to firefox or chrome and open translate.google.com
type some　gobbledy-gook (e.g ldgk) and hit space.
Now switch back to the text editor. 
Anthy symbol still shows in the panel　but typing is in english.
Switch back to the browser and its in Japanese again. 

Description:Linux Mint 17.3 Rosa (but its the same on trusty-tahr)
anthy:
  Installed: 9100h-23ubuntu2
  Candidate: 9100h-23ubuntu2
  Version table:
 *** 9100h-23ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: anthy 9100h-23ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Feb 19 17:23:27 2016
InstallationDate: Installed on 2016-02-19 (0 days ago)
InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151128
SourcePackage: anthy
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug rosa

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547355

Title:
  Anthy doesn't work properly after using google translate

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

[Tore Anderson]

After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have
found that the problem is caused by the removal of the file
/lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the
following:

#
# udev rules for multipathing.
# The persistent symlinks are created with the kpartx rules
#

# socket for uevents
RUN+="socket:/org/kernel/dm/multipath_event"

# Coalesce multipath devices before multipathd is running (initramfs, early
# boot)
ACTION=="add|change", SUBSYSTEM=="block", RUN+="/sbin/multipath -v0 /dev/$name"

If this file is manually reinstated (either to /lib/udev/rules.d or
/etc/udev/rules.d), boot is again successful (even with the latest
-3ubuntu7.9 multipath-tools package).

I see from the changelog that the removal was intentional:

  * debian/rules: don't ship 95-multipath.rules udev rules anymore; they are
not necessary with multipath-tools listening for udev events directly.
  * debian/multipath.udev: removed.

However, in order for this to actually work with multipath-backed "auto"
filesystems in /etc/fstab, it seems necessary to ensure that multipathd
is started before mountall runs. I am not entirely certain how to
accomplish this, though, as mountall is started from Upstart while
multipath-tools is stuck using a legacy SysV-init, and I do not know if
it is possible to enforce service ordering between the two init systems.
For what it's worth, renaming /etc/rcS.d/S21-multipath-tools-boot as
etc/rcS.d/S00-multipath-tools-boot does not work around the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1547353] Re: package duplicity 0.6.23-1ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[Apport retracing service]

** Tags removed: need-duplicate-check

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547353

Title:
  package duplicity 0.6.23-1ubuntu4.1 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 127

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547353] [NEW] package duplicity 0.6.23-1ubuntu4.1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[abhi]

Public bug reported:

kindly fix this issue

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: duplicity 0.6.23-1ubuntu4.1
ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
Uname: Linux 3.19.0-49-generic x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Fri Feb 19 12:36:00 2016
DuplicateSignature: package:duplicity:0.6.23-1ubuntu4.1:subprocess installed 
pre-removal script returned error exit status 127
ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
InstallationDate: Installed on 2016-02-12 (6 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.11
SourcePackage: duplicity
Title: package duplicity 0.6.23-1ubuntu4.1 failed to install/upgrade: 
subprocess installed pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547353

Title:
  package duplicity 0.6.23-1ubuntu4.1 failed to install/upgrade:
  subprocess installed pre-removal script returned error exit status 127

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

[Tore Anderson]

After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have
found that the problem is caused by the removal of the file
/lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the
following:

#
# udev rules for multipathing.
# The persistent symlinks are created with the kpartx rules
#

# socket for uevents
RUN+="socket:/org/kernel/dm/multipath_event"

# Coalesce multipath devices before multipathd is running (initramfs, early
# boot)
ACTION=="add|change", SUBSYSTEM=="block", RUN+="/sbin/multipath -v0 /dev/$name"

If this file is manually reinstated (either to /lib/udev/rules.d or
/etc/udev/rules.d), boot is again successful (even with the latest
-3ubuntu7.9 multipath-tools package).

I see from the changelog that the removal was intentional:

  * debian/rules: don't ship 95-multipath.rules udev rules anymore; they are
not necessary with multipath-tools listening for udev events directly.
  * debian/multipath.udev: removed.

However, in order for this to actually work with multipath-backed "auto"
filesystems in /etc/fstab, it seems necessary to ensure that multipathd
is started before mountall runs. I am not entirely certain how to
accomplish this, though, as mountall is started from Upstart while
multipath-tools is stuck using a legacy SysV-init, and I do not know if
it is possible to enforce service ordering between the two init systems.
For what it's worth, renaming /etc/rcS.d/S21-multipath-tools-boot as
etc/rcS.d/S00-multipath-tools-boot does not work around the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1546847] Re: Fonts-droid has been deprecated and removed

[zhangchao]

** Summary changed:

- Fonts-droid has been deprecated and removed,Use fonts-noto instead of 
Fonts-droid
+ Fonts-droid has been deprecated and removed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546847

Title:
  Fonts-droid has been deprecated and removed

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1440564] Re: please use Python3 for all scripts

[Didier Roche]

LGTM, thanks Barry!
+1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440564

Title:
  please use Python3 for all scripts

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545854] Re: [MIR] build dependency of iptables

[Matthias Klose]

Override component to main
libnftnl 1.0.5+snapshot20151106-1ubuntu3 in xenial: universe/misc -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial amd64: 
universe/libdevel/extra/100% -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial arm64: 
universe/libdevel/extra/100% -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial armhf: 
universe/libdevel/extra/100% -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial i386: 
universe/libdevel/extra/100% -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial powerpc: 
universe/libdevel/extra/100% -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial ppc64el: 
universe/libdevel/extra/100% -> main
libnftnl-dev 1.0.5+snapshot20151106-1ubuntu3 in xenial s390x: 
universe/libdevel/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial amd64: 
universe/libs/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial arm64: 
universe/libs/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial armhf: 
universe/libs/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial i386: 
universe/libs/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial powerpc: 
universe/libs/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial ppc64el: 
universe/libs/extra/100% -> main
libnftnl4 1.0.5+snapshot20151106-1ubuntu3 in xenial s390x: 
universe/libs/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial amd64: 
universe/debug/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial arm64: 
universe/debug/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial armhf: 
universe/debug/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial i386: 
universe/debug/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial powerpc: 
universe/debug/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial ppc64el: 
universe/debug/extra/100% -> main
libnftnl4-dbg 1.0.5+snapshot20151106-1ubuntu3 in xenial s390x: 
universe/debug/extra/100% -> main
22 publications overridden.


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545854

Title:
  [MIR] build dependency of iptables

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547223] Re: linux-raspi2: 4.4.0-1001.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-development-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547223

Title:
  linux-raspi2: 4.4.0-1001.2 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1547223/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545854] Re: [MIR] build dependency of iptables

[Matthias Klose]

Override component to main
mxml 2.9-0ubuntu2 in xenial: universe/libdevel -> main
libmxml-dev 2.9-0ubuntu2 in xenial amd64: universe/libdevel/optional/100% -> 
main
libmxml-dev 2.9-0ubuntu2 in xenial arm64: universe/libdevel/optional/100% -> 
main
libmxml-dev 2.9-0ubuntu2 in xenial armhf: universe/libdevel/optional/100% -> 
main
libmxml-dev 2.9-0ubuntu2 in xenial i386: universe/libdevel/optional/100% -> main
libmxml-dev 2.9-0ubuntu2 in xenial powerpc: universe/libdevel/optional/100% -> 
main
libmxml-dev 2.9-0ubuntu2 in xenial ppc64el: universe/libdevel/optional/100% -> 
main
libmxml-dev 2.9-0ubuntu2 in xenial s390x: universe/libdevel/optional/100% -> 
main
libmxml1 2.9-0ubuntu2 in xenial amd64: universe/libs/optional/100% -> main
libmxml1 2.9-0ubuntu2 in xenial arm64: universe/libs/optional/100% -> main
libmxml1 2.9-0ubuntu2 in xenial armhf: universe/libs/optional/100% -> main
libmxml1 2.9-0ubuntu2 in xenial i386: universe/libs/optional/100% -> main
libmxml1 2.9-0ubuntu2 in xenial powerpc: universe/libs/optional/100% -> main
libmxml1 2.9-0ubuntu2 in xenial ppc64el: universe/libs/optional/100% -> main
libmxml1 2.9-0ubuntu2 in xenial s390x: universe/libs/optional/100% -> main
15 publications overridden.


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545854

Title:
  [MIR] build dependency of iptables

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547281] Re: ofonod crashed with SIGSEGV in ofono_modem_remove()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1538300, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575096/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575098/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575100/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575101/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575102/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575103/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1547281/+attachment/4575104/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1538300

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547281

Title:
  ofonod crashed with SIGSEGV in ofono_modem_remove()

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1437931] Re: starting stellarium causes system crash

[Ingo Haase]

Same here on a freshly installed Ubuntu 15.10 (i5, Intel HD 5500
graphics).  CTRL+ALT+Backspace won't work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1437931

Title:
  starting stellarium causes system crash

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547190] Re: LXD Power8 container hangs and slow creation

[Stéphane Graber]

ubuntu@1ss-ppc64el:~/go/src/github.com/lxc/lxd$ time lxc launch trusty blah
Starting blah

real0m0.907s
user0m0.012s
sys 0m0.000s

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547190

Title:
  LXD Power8 container hangs and slow creation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1507427] Re: python-greenio: FTBFS: RuntimeError: generator raised StopIteration

[Bug Watch Updater]

** Changed in: python-greenio (Debian)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1507427

Title:
  python-greenio: FTBFS: RuntimeError: generator raised StopIteration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1460242] Re: documentation: apt-keys via http allows man-in-the-middle-attacks

[Thomas Mayer]

For copy-pasteable add-apt-repository commands on the website I filed a
new issue for launchpad itself:
https://bugs.launchpad.net/launchpad/+bug/1547343

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460242

Title:
  documentation: apt-keys via http allows man-in-the-middle-attacks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547344] [NEW] lldb executable not properly installed on Xenial

[Marc-Andre Laperle]

Public bug reported:

It looks like lldb is not installed properly on 16.04 (Xenial). After
installing the "lldb" package, the executable is not found.

$ lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
$ sudo apt-get install lldb
Reading package lists... Done
Building dependency tree   
Reading state information... Done
lldb is already the newest version (1:3.8-33ubuntu3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ readlink -f /usr/bin/lldb
/usr/lib/llvm-3.8/bin/lldb-3.8.0
$ ls -l /usr/lib/llvm-3.8/bin/lldb-3.8.0
ls: cannot access /usr/lib/llvm-3.8/bin/lldb-3.8.0: No such file or directory

** Affects: llvm-defaults (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547344

Title:
  lldb executable not properly installed on Xenial

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1544926] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From abdha...@in.ibm.com 2016-02-19 01:15 EDT---
(In reply to comment #6)
> The error in your log is:
>
> insserv: warning: script 'S99autotest' missing LSB tags and overrides
> insserv: warning: script 'autotest' missing LSB tags and overrides
> insserv: There is a loop at service plymouth if started
> insserv: There is a loop between service plymouth and procps if started
> insserv: loop involving service procps at depth 2
> insserv: loop involving service udev at depth 1
> insserv: Starting autotest depends on plymouth and therefore on system
> facility `$all' which can not be true!
>
> This is not a bug in Ubuntu.  You have an init script on your system,
> /etc/init.d/autotest, which is not from Ubuntu and which is not an
> LSB-compliant init script.  This is not supported, and will cause insserv to
> fail to calculate boot order as shown here.

alright, Yes I had run a kernel build test case from autotest earlier
which created /etc/init.d/autotest.

kexec-tools insall worked fine, when /etc/init.d/autotest is removed.

This is not a bug

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544926

Title:
  kexec-tools : errors while installing kexec tools package

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547190] Re: LXD Power8 container hangs and slow creation

[Stéphane Graber]

Oh and for the slow creation part of this bug, I'm getting container
created within 30s on my ppc64el system when using the directory backend
which is a normal time.

When enabling btrfs (zfs should be the same), I get a container creation
time of ~1s.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547190

Title:
  LXD Power8 container hangs and slow creation

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1545255] Re: Dependency wait on lcy01-34 Missing build dependencies: liblz4-dev (>= 0.0~r126)

[dragonhahney]

sir,

i spent over $100 dollars such as i bought ubuntu usb, donations
(libreoffice) etc.. still i cannot use ubuntu and lost all the libreoffice
files?  because ms os 8.1 wipe out all files...very respectfully
submitted. edward hahn

On Wed, Feb 17, 2016 at 12:18 AM, dino99 <1545...@bugs.launchpad.net>
wrote:

> apt 1.2.3 has now landed into xenial archive
>
> ** Changed in: apt (Ubuntu)
>Status: New => Fix Released
>
> --
> You received this bug notification because you are subscribed to apt in
> Ubuntu.
> Matching subscriptions: dragonhahney
> https://bugs.launchpad.net/bugs/1545255
>
> Title:
>Dependency wait on lcy01-34  Missing build dependencies: liblz4-dev
>   (>= 0.0~r126)
>
> Status in apt package in Ubuntu:
>   Fix Released
>
> Bug description:
>   https://launchpad.net/ubuntu/+source/apt
>
>   Built of apt 1.2.3 is locked due to missing dependency:
>
>   Build status
>   [MANUALDEPWAIT] Dependency wait on lcy01-34
>
>   Missing build dependencies: liblz4-dev (>= 0.0~r126)
>   Started on 2016-02-11
>   Finished on 2016-02-11 (took 4 minutes, 1.9 seconds)
>   buildlog (11.4 KiB)
>
>   liblz4-dev  0.0~r131-1 is available into xenial archive:
>
>   lz4 (0.0~r131-1) unstable; urgency=medium
>
> * Snapshot, taken from the trunk (r131).
> * Update and enable atches/0001-Disable-valgrind.patch.
>
>-- Nobuhiro Iwamatsu   Sun, 16 Aug 2015 20:46:09
> +0900
>   ---
>   ApportVersion: 2.19.4-0ubuntu2
>   Architecture: amd64
>   CurrentDesktop: GNOME
>   DistroRelease: Ubuntu 16.04
>   NonfreeKernelModules: nvidia_uvm nvidia
>   Package: apt 1.1.10
>   PackageArchitecture: amd64
>   ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1
>   Tags:  xenial
>   Uname: Linux 4.4.0-5-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1545255/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545255

Title:
   Dependency wait on lcy01-34  Missing build dependencies: liblz4-dev
  (>= 0.0~r126)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1460242] Re: documentation: apt-keys via http allows man-in-the-middle-attacks

[Thomas Mayer]

Covered by this issue, https://wiki.ubuntuusers.de/some/program has
become available in the meantime and it's https-only which is good.

To go for

add-apt-repository ppa:

is a nice way and I'm aware of this. Nice as long as key material is
transferred in a secure manner (e.g. https-only).

But first of all this is not copy-paste-able (user has to click  "(Read
about installing)" to see the full command, and still can't copy-paste
something.

And secondly, I still see

sudo apt-key add

all over the place, often with wget via http and even with https it is
hard to verify trustworthyness unless it origins e.g. from the
maintainer's domain.

Please make the add-apt-repository ppa: syntax copy-
pasteable all over the place at least for launchpad-hosted packages.
This is much easier for average users and it's ways more realistic that
they use it and install software in a safe manner. This should at least
cover launchpad's packages.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460242

Title:
  documentation: apt-keys via http allows man-in-the-middle-attacks

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1512221] Re: MPT3SAS Driver update for next kernel release

[Chaitra P B]

Update mpt3sas inbox driver version for Ubuntu 16.04 to "12.100.00.00".

mpt3sas drivers update(to v12.100.00.00) feature list along with commit
id's on top of  inbox driver "09.102.00.00"

1.mpt3sas: A correction in unmap_resources
   commit 5f985d88bac34e7f3b4403118eab072902a0b392
 
2.mpt3sas: Added support for high port count HBA variants.
   commit 1abeff9c9ab2384a0da5019956d52944350301e6
 
3.mpt3sas: Used IEEE SGL instead of MPI SGL while framing a SMP Passthrough 
request message.
   commit 415f1c3fe636022dd2d91fc152c0665adf588e44
 
4.mpt3sas: Fix static analyzer(coverity) tool identified defects
   commit dc2ed1660060a04ae9857047ace1169bddeb2ef6

5.mpt3sas: Never block the Enclosure device
   commit b17d0b7ff0768070180e1021c0f32988445644d8 
 
6.mpt3sas: Make use of additional HighPriority credit message frames for 
sending SCSI IO's
   commit 3ffa7c60b71fcd1070a68a74c380c05c4c161710  
 
7.mpt3sas: Added smp_affinity_enable module parameter. 
   commit be65e666abdd21865b3ea2713257a66e624eeaec  
 
8.mpt3sas: Add support for configurable Chain Frame Size 
   commit 84619ca86eb0797aad61f962dafa82788861c4e0  
 
9.mpt3sas: Updated MPI Header to 2.00.42 
   commit ff711f645e0de9adec7fff52f2a5f0a1959d5be6 

10.mpt3sas: Fix for Asynchronous completion of timedout IO and task abort of 
timedout IO. 
   commit 06071c8bae271ea2f8af3951c40ffad340b2cbbd 

11.mpt3sas: Updating mpt3sas driver version to 12.100.00.00 
   commit f27b0bd7abe06288ba38125f144aa3d91fb315f4 

12.mpt3sas: Remove cpumask_clear for zalloc_cpumask_var and don't  free 
free_cpu_mask_var before reply_q
   commit 01b96358f594b38813f25d89da850e4bce337318

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512221

Title:
  MPT3SAS Driver update for next kernel release

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547073] Re: package libnss3-nssdb 2:3.21-0ubuntu0.14.04.1 failed to install/upgrade: package libnss3-nssdb is already installed and configured

[dino99]

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

** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547073

Title:
  package libnss3-nssdb 2:3.21-0ubuntu0.14.04.1 failed to
  install/upgrade: package libnss3-nssdb is already installed and
  configured

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1547336] [NEW] almost gets to third action on the list then get error also it says it needs to kick off a third party program google i assume or i dunno it has alot that never got the full last u

[ross]

Public bug reported:

suks im sick of missing somethin realy small if i had the rebooter disc
id start from scratch  i did buy it u know some ppl jus rob a guy bcuz
theives are fags

ProblemType: Bug
DistroRelease: Zorin OS 10
Package: ubuntu-release-upgrader-core 1:15.04.14.1 [origin: unknown]
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
CrashDB: ubuntu
Date: Fri Feb 19 00:00:46 2016
InstallationDate: Installed on 2015-07-31 (202 days ago)
InstallationMedia: Zorin 9 trusty - Release amd64 (20140729)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to vivid on 2016-02-19 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2016-02-18 23:54:16.010994
 Log time: 2016-02-18 23:54:49.056809
 Log time: 2016-02-18 23:55:12.133985
 Log time: 2016-02-19 00:00:51.446415
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade third-party-packages vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1547336

Title:
  almost gets to third action on the list then get error also it says it
  needs to kick off a third party program google i assume or i dunno it
  has alot that never got the full last update it

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1359224] Re: Feature request: Add support for multiple bridges

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1359224

Title:
  Feature request: Add support for multiple bridges

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1428490] Re: AppArmor vs unix socket inside LXC containers

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1428490

Title:
  AppArmor vs unix socket inside LXC containers

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1302053] Re: lxc-start with bad container name gives strange err message

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302053

Title:
  lxc-start with bad container name gives strange err message

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1340836] Re: error: error executing "lxc-start" when juju client runs inside kvm

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1340836

Title:
  error: error executing "lxc-start" when juju client runs inside kvm

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1302053] Re: lxc-start with bad container name gives strange err message

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1302053

Title:
  lxc-start with bad container name gives strange err message

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1428490] Re: AppArmor vs unix socket inside LXC containers

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1428490

Title:
  AppArmor vs unix socket inside LXC containers

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1340836] Re: error: error executing "lxc-start" when juju client runs inside kvm

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1340836

Title:
  error: error executing "lxc-start" when juju client runs inside kvm

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1359224] Re: Feature request: Add support for multiple bridges

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359224

Title:
  Feature request: Add support for multiple bridges

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1293549] Re: Filesystem mount from lxc template causes filesystem permission breakages

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1293549

Title:
  Filesystem mount from lxc template causes filesystem permission
  breakages

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1524328] Re: libpng 1.6 support

[Timo Aaltonen]

i've synced libpng1.6 yesterday, it's in universe now

** Changed in: libpng (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1524328

Title:
  libpng 1.6 support

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1441307] Re: lxc-clone makes new copies of each hardlinked file

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1441307

Title:
  lxc-clone makes new copies of each hardlinked file

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1441307] Re: lxc-clone makes new copies of each hardlinked file

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1441307

Title:
  lxc-clone makes new copies of each hardlinked file

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1436722] Re: lxc domain setup instructions are incorrect

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436722

Title:
  lxc domain setup instructions are incorrect

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1470599] Re: Stuck mountall inside container

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1470599

Title:
  Stuck mountall inside container

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470599] Re: Stuck mountall inside container

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470599

Title:
  Stuck mountall inside container

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1470599] Re: Stuck mountall inside container

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1470599

Title:
  Stuck mountall inside container

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1436722] Re: lxc domain setup instructions are incorrect

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436722

Title:
  lxc domain setup instructions are incorrect

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1519681] Re: Some media keys on keyboards do not work as expected

[Simon Fels]

It hardly depends on what the keyboard supports. Check via bluetoothctl
which profiles it supports. If its only HID then its not AVRCP but
otherwise it could and then we have to fix this differently.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519681

Title:
  Some media keys on keyboards do not work as expected

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472929] Re: undefined symbol: cgmanager_get_pid_cgroup_abs_sync

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1472929

Title:
  undefined symbol: cgmanager_get_pid_cgroup_abs_sync

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1470599] Re: Stuck mountall inside container

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470599

Title:
  Stuck mountall inside container

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472929] Re: undefined symbol: cgmanager_get_pid_cgroup_abs_sync

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1472929

Title:
  undefined symbol: cgmanager_get_pid_cgroup_abs_sync

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1302053] [NEW] lxc-start with bad container name gives strange err message

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

$  sudo lxc-start -d -n mongodb-server-1
[sudo] password for kapil: 
lxc-start: Executing '/sbin/init' with no configuration file may crash the host

how bout  just no such container exists.

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

-- 
lxc-start with bad container name gives strange err message
https://bugs.launchpad.net/bugs/1302053
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1359224] [NEW] Feature request: Add support for multiple bridges

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I want to allow multiple users to create unpriviledged containers on the
same host. And I would like each user to  be assigned a different
bridge, so that each user's containers can be restricted to a sub-net.

The `/etc/init/lxc-ent` script seems to be hard-coded for one bridge. If
it could read a list of bridge names and create them automatically, it
would be great.

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


** Tags: bridge feature lxc
-- 
Feature request: Add support for multiple bridges
https://bugs.launchpad.net/bugs/1359224
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1302053] [NEW] lxc-start with bad container name gives strange err message

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

$  sudo lxc-start -d -n mongodb-server-1
[sudo] password for kapil: 
lxc-start: Executing '/sbin/init' with no configuration file may crash the host

how bout  just no such container exists.

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

-- 
lxc-start with bad container name gives strange err message
https://bugs.launchpad.net/bugs/1302053
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1359224] [NEW] Feature request: Add support for multiple bridges

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I want to allow multiple users to create unpriviledged containers on the
same host. And I would like each user to  be assigned a different
bridge, so that each user's containers can be restricted to a sub-net.

The `/etc/init/lxc-ent` script seems to be hard-coded for one bridge. If
it could read a list of bridge names and create them automatically, it
would be great.

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


** Tags: bridge feature lxc
-- 
Feature request: Add support for multiple bridges
https://bugs.launchpad.net/bugs/1359224
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1428490] [NEW] AppArmor vs unix socket inside LXC containers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I know this seems like an odd bug, but I've spent all day chasing it
down.

I was seeing problems with LDAP lookups inside an LXC container, and
strace on getent lookups was showing that attempts to read from
/var/run/nslcd/socket were being closed as -1 (EACCESS).

That file/UNIX socket is owned by nslcd, also running inside the LXC.

Back on the host machine, setting the LXC config to set lxc.aa_profile =
unconfined (and restarting the container) then allowed that socket to
start working freely.

This seems weird, as there's all sorts of other things using UNIX
sockets inside containers that still function normally, but I thought
I'd mention it, especially in case anyone hits this issue.

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


** Tags: apparmor ldap lxc nslcd
-- 
AppArmor vs unix socket inside LXC containers
https://bugs.launchpad.net/bugs/1428490
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1486073] Re: 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1486073

Title:
  'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1063838] Re: Launcher - clicking on a Storage Device icon in the Launcher should focus then spread the Nautilus windows that are displaying the storage device's content

[Khurshid Alam]

@3v1n0

After this fix, it treats hard disk partition as a removable storage.
However If create a symlink of a folder in that partition, it focuses on
main nautilus window. Very confusing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1063838

Title:
  Launcher - clicking on a Storage Device icon in the Launcher should
  focus then spread the Nautilus windows that are displaying the storage
  device's content

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1063838/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1342960] Re: comments in common.conf must be updated

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342960

Title:
  comments in common.conf must be updated

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445539] Re: Can't create vivid lxc on trusty

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1445539

Title:
  Can't create vivid lxc on trusty

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1486073] Re: 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1486073

Title:
  'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521151] Re: init: lxc-instance main process terminated with status 255

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521151

Title:
  init: lxc-instance main process terminated with status 255

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

[RussianNeuroMancer]

~$ cat 
/etc/apparmor.d/libvirt/libvirt-aa613ca3-5fff-467e-be3b-7752dc07e856.files
# DO NOT EDIT THIS FILE DIRECTLY. IT IS MANAGED BY LIBVIRT.
  "/var/log/libvirt/**/monitoring.log" w,
  "/var/lib/libvirt/qemu/domain-monitoring/monitor.sock" rw,
  "/var/run/libvirt/**/monitoring.pid" rwk,
  "/run/libvirt/**/monitoring.pid" rwk,
  "/var/run/libvirt/**/*.tunnelmigrate.dest.monitoring" rw,
  "/run/libvirt/**/*.tunnelmigrate.dest.monitoring" rw,
  "/var/lib/libvirt/images/monitoring.img" rw,
  "/dev/net/tun" rw,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1393842

Title:
  libvirt does not grant qemu-guest-agent channel perms

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1428490] [NEW] AppArmor vs unix socket inside LXC containers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I know this seems like an odd bug, but I've spent all day chasing it
down.

I was seeing problems with LDAP lookups inside an LXC container, and
strace on getent lookups was showing that attempts to read from
/var/run/nslcd/socket were being closed as -1 (EACCESS).

That file/UNIX socket is owned by nslcd, also running inside the LXC.

Back on the host machine, setting the LXC config to set lxc.aa_profile =
unconfined (and restarting the container) then allowed that socket to
start working freely.

This seems weird, as there's all sorts of other things using UNIX
sockets inside containers that still function normally, but I thought
I'd mention it, especially in case anyone hits this issue.

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


** Tags: apparmor ldap lxc nslcd
-- 
AppArmor vs unix socket inside LXC containers
https://bugs.launchpad.net/bugs/1428490
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1342960] Re: comments in common.conf must be updated

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1342960

Title:
  comments in common.conf must be updated

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1486073] Re: 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486073

Title:
  'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1545005] Re: system settings displays 'cellular' control panel item when no modems are present

[Simon Fels]

Its a problem in ofono where still creates a modem instance (exposed as
/ril_0) without any interfaces registered when the connection to the
ril-daemon fails. IMHO ofono should not create the modem instance as
long as it can't connect to rild. We agreed on keeping ofono running
even on devices which doesn't have a modem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1545005

Title:
  system settings displays 'cellular' control panel item when no modems
  are present

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521151] Re: init: lxc-instance main process terminated with status 255

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1521151

Title:
  init: lxc-instance main process terminated with status 255

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1486073] Re: 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486073

Title:
  'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445539] Re: Can't create vivid lxc on trusty

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1445539

Title:
  Can't create vivid lxc on trusty

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1441307] [NEW] lxc-clone makes new copies of each hardlinked file

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using lxc 1.0.7 from the stable PPA on precise.

When I use lxc-clone to copy a container running MAAS, which uses
hardlinks to manage images, each hardlinked file is created as a new
file in the cloned rootfs, increasing my file system size by hundreds of
GB's.

rsync is not using -H - just rsync -a.

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


** Tags: oil
-- 
lxc-clone makes new copies of each hardlinked file
https://bugs.launchpad.net/bugs/1441307
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1436722] [NEW] lxc domain setup instructions are incorrect

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Developers are required to manually hack their configuration to enable
.lxc domain name resolution. This appears to be documented solely in
/etc/default/lxc-net. This documentation is incorrect, as it tells
developers to edit /etc/dnsmasq.conf and this file does not exist.

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

-- 
lxc domain setup instructions are incorrect
https://bugs.launchpad.net/bugs/1436722
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1441307] [NEW] lxc-clone makes new copies of each hardlinked file

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using lxc 1.0.7 from the stable PPA on precise.

When I use lxc-clone to copy a container running MAAS, which uses
hardlinks to manage images, each hardlinked file is created as a new
file in the cloned rootfs, increasing my file system size by hundreds of
GB's.

rsync is not using -H - just rsync -a.

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


** Tags: oil
-- 
lxc-clone makes new copies of each hardlinked file
https://bugs.launchpad.net/bugs/1441307
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1436722] [NEW] lxc domain setup instructions are incorrect

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Developers are required to manually hack their configuration to enable
.lxc domain name resolution. This appears to be documented solely in
/etc/default/lxc-net. This documentation is incorrect, as it tells
developers to edit /etc/dnsmasq.conf and this file does not exist.

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

-- 
lxc domain setup instructions are incorrect
https://bugs.launchpad.net/bugs/1436722
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1472929] [NEW] undefined symbol: cgmanager_get_pid_cgroup_abs_sync

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have lxc installed on 14.04 , I am getting following error while
running lxc-create command


dtripathi@dtripath-x:~$ sudo lxc-create -t default -n dtripathi-lxc01
lxc-create: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblxc.so.1: 
undefined symbol: cgmanager_get_pid_cgroup_abs_sync 
 


dtripathi@dtripathi-x:~$ ldd /usr/bin/lxc-create

linux-vdso.so.1 =>  (0x7ffd3a7e8000)
 
liblxc.so.1 => /usr/lib/x86_64-linux-gnu/liblxc.so.1 
(0x7fbc91aa)

libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbc91882000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbc914bb000)   
 
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fbc912b6000)   
 
libapparmor.so.1 => /usr/lib/x86_64-linux-gnu/libapparmor.so.1 
(0x7fbc910aa000)
  
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fbc90e86000)

libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2 
(0x7fbc90c6f000)

libcgmanager.so.0 => /lib/x86_64-linux-gnu/libcgmanager.so.0 
(0x7fbc90a55000)

libnih.so.1 => /lib/x86_64-linux-gnu/libnih.so.1 (0x7fbc9083c000)   
 
libnih-dbus.so.1 => /lib/x86_64-linux-gnu/libnih-dbus.so.1 
(0x7fbc90632000)
  
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7fbc903ed000)
  
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fbc901e9000) 
 
/lib64/ld-linux-x86-64.so.2 (0x7fbc91f2d000)
 
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fbc8ffab000) 
 
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbc8fda6000) 
 
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fbc8fb9e000) 
 
dtripathi@dtripathi-:~$ 


Please find the

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


** Tags: lxc
-- 
undefined symbol: cgmanager_get_pid_cgroup_abs_sync 
https://bugs.launchpad.net/bugs/1472929
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1472929] [NEW] undefined symbol: cgmanager_get_pid_cgroup_abs_sync

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have lxc installed on 14.04 , I am getting following error while
running lxc-create command


dtripathi@dtripath-x:~$ sudo lxc-create -t default -n dtripathi-lxc01
lxc-create: symbol lookup error: /usr/lib/x86_64-linux-gnu/liblxc.so.1: 
undefined symbol: cgmanager_get_pid_cgroup_abs_sync 
 


dtripathi@dtripathi-x:~$ ldd /usr/bin/lxc-create

linux-vdso.so.1 =>  (0x7ffd3a7e8000)
 
liblxc.so.1 => /usr/lib/x86_64-linux-gnu/liblxc.so.1 
(0x7fbc91aa)

libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fbc91882000)

libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fbc914bb000)   
 
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7fbc912b6000)   
 
libapparmor.so.1 => /usr/lib/x86_64-linux-gnu/libapparmor.so.1 
(0x7fbc910aa000)
  
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fbc90e86000)

libseccomp.so.2 => /usr/lib/x86_64-linux-gnu/libseccomp.so.2 
(0x7fbc90c6f000)

libcgmanager.so.0 => /lib/x86_64-linux-gnu/libcgmanager.so.0 
(0x7fbc90a55000)

libnih.so.1 => /lib/x86_64-linux-gnu/libnih.so.1 (0x7fbc9083c000)   
 
libnih-dbus.so.1 => /lib/x86_64-linux-gnu/libnih-dbus.so.1 
(0x7fbc90632000)
  
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7fbc903ed000)
  
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fbc901e9000) 
 
/lib64/ld-linux-x86-64.so.2 (0x7fbc91f2d000)
 
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fbc8ffab000) 
 
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fbc8fda6000) 
 
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fbc8fb9e000) 
 
dtripathi@dtripathi-:~$ 


Please find the

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


** Tags: lxc
-- 
undefined symbol: cgmanager_get_pid_cgroup_abs_sync 
https://bugs.launchpad.net/bugs/1472929
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1470599] [NEW] Stuck mountall inside container

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

trusty
lxc 1.1.2-0ubuntu3~cloud0
kernel Linux ambipom 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux


All processes running on the container:
  34700 ?Ss 0:00 [lxc monitor] /var/lib/lxc juju-machine-3-lxc-1
  34729 ?Ss 0:00  \_ /sbin/init
  34789 ?S  0:00  \_ @sbin/plymouthd --mode=boot 
--attach-to-session
  34797 ?Ss 0:00  \_ plymouth-upstart-bridge
  34803 ?S  0:00  \_ mountall --daemon
  35368 ?S  0:00  \_ upstart-socket-bridge --daemon
  36248 ?Ss 0:00  \_ dhclient -1 -v -pf /run/dhclient.eth0.pid 
-lf /var/lib/dhcp/dhclient.eth0.leases eth0

Several other containers on the same host started up just fine.


If mountall is killed and restarted from the command line with verbose and 
debug flags, this is the output:
root@juju-machine-3-lxc-1:~# mountall -v --debug
Connected to Plymouth
parse_filesystems: reading filesystems
parse_filesystems: sysfs (nodev)
parse_filesystems: rootfs (nodev)
parse_filesystems: ramfs (nodev)
parse_filesystems: bdev (nodev)
parse_filesystems: proc (nodev)
parse_filesystems: cgroup (nodev)
parse_filesystems: cpuset (nodev)
parse_filesystems: tmpfs (nodev)
parse_filesystems: devtmpfs (nodev)
parse_filesystems: debugfs (nodev)
parse_filesystems: securityfs (nodev)
parse_filesystems: sockfs (nodev)
parse_filesystems: pipefs (nodev)
parse_filesystems: anon_inodefs (nodev)
parse_filesystems: devpts (nodev)
parse_filesystems: ext3
parse_filesystems: ext2
parse_filesystems: ext4
parse_filesystems: hugetlbfs (nodev)
parse_filesystems: vfat
parse_filesystems: ecryptfs (nodev)
parse_filesystems: fuseblk
parse_filesystems: fuse (nodev)
parse_filesystems: fusectl (nodev)
parse_filesystems: pstore (nodev)
parse_filesystems: efivarfs (nodev)
parse_filesystems: mqueue (nodev)
parse_filesystems: xfs
parse_fstab: updating from /lib/init/fstab
update_mount: /: / /dev/root rootfs defaults check
update_mount: /proc: /proc none proc nodev,noexec,nosuid
update_mount: /proc/sys/fs/binfmt_misc: /proc/sys/fs/binfmt_misc none 
binfmt_misc nodev,noexec,nosuid,optional
update_mount: /sys: /sys none sysfs nodev,noexec,nosuid
update_mount: /sys/fs/cgroup: /sys/fs/cgroup none tmpfs 
optional,uid=0,gid=0,mode=0755,size=1024
update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl 
optional
update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional
update_mount: /sys/kernel/security: /sys/kernel/security none securityfs 
optional
update_mount: /sys/firmware/efi/efivars: /sys/firmware/efi/efivars none 
efivarfs optional
update_mount: /spu: /spu none spufs gid=spu,optional
update_mount: /dev: /dev none devtmpfs,tmpfs mode=0755
update_mount: /dev/pts: /dev/pts none devpts noexec,nosuid,gid=tty,mode=0620
update_mount: /tmp: /tmp none none defaults
update_mount: /run: /run none tmpfs noexec,nosuid,size=10%,mode=0755
update_mount: /run/lock: /run/lock none tmpfs nodev,noexec,nosuid,size=5242880
update_mount: /run/shm: /run/shm none tmpfs nosuid,nodev
update_mount: /run/user: /run/user none tmpfs 
nodev,noexec,nosuid,size=104857600,mode=0755
update_mount: /sys/fs/pstore: /sys/fs/pstore none pstore optional
parse_fstab: updating from /etc/fstab
update_mount: /: / LABEL=cloudimg-rootfs ext4 defaults
parse_mountinfo_file: updating mounts
update_mount: /: / /dev/disk/by-uuid/7d38a3ed-8f5b-49d4-8087-b1573a17bb98 ext4 
defaults
update_mount: /dev: /dev none tmpfs mode=0755
update_mount: /proc: /proc proc proc nodev,noexec,nosuid
update_mount: /proc/sys/net: /proc/sys/net proc proc 
rw,nosuid,nodev,noexec,relatime,rw
update_mount: /proc/sys: /proc/sys proc proc ro,nosuid,nodev,noexec,relatime,rw
update_mount: /proc/sysrq-trigger: /proc/sysrq-trigger proc proc 
ro,nosuid,nodev,noexec,relatime,rw
update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid
update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid
update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs 
rw,relatime,rw
update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs 
rw,relatime,rw
update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl 
optional
update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional
update_mount: /sys/kernel/security: /sys/kernel/security none securityfs 
optional
update_mount: /sys/fs/pstore: /sys/fs/pstore none pstore optional
update_mount: /var/log/juju: /var/log/juju 
/dev/disk/by-uuid/7d38a3ed-8f5b-49d4-8087-b1573a17bb98 ext4 
rw,relatime,rw,stripe=64,data=ordered
update_mount: /sys/fs/cgroup: /sys/fs/cgroup cgroup tmpfs 
optional,uid=0,gid=0,mode=0755,size=1024
update_mount: /sys/fs/cgroup/cgmanager: /sys/fs/cgroup/cgmanager none tmpfs 
rw,relatime,rw,size=4k,mode=755
update_mount: /dev/lxc/console: /dev/lxc/console devpts devpts 
rw,nosuid,noexec,relatime,rw,gid=5,mode=620,ptmxmode=000
update_mount: /dev/pts: /dev/pts 

[Bug 1470599] [NEW] Stuck mountall inside container

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

trusty
lxc 1.1.2-0ubuntu3~cloud0
kernel Linux ambipom 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux


All processes running on the container:
  34700 ?Ss 0:00 [lxc monitor] /var/lib/lxc juju-machine-3-lxc-1
  34729 ?Ss 0:00  \_ /sbin/init
  34789 ?S  0:00  \_ @sbin/plymouthd --mode=boot 
--attach-to-session
  34797 ?Ss 0:00  \_ plymouth-upstart-bridge
  34803 ?S  0:00  \_ mountall --daemon
  35368 ?S  0:00  \_ upstart-socket-bridge --daemon
  36248 ?Ss 0:00  \_ dhclient -1 -v -pf /run/dhclient.eth0.pid 
-lf /var/lib/dhcp/dhclient.eth0.leases eth0

Several other containers on the same host started up just fine.


If mountall is killed and restarted from the command line with verbose and 
debug flags, this is the output:
root@juju-machine-3-lxc-1:~# mountall -v --debug
Connected to Plymouth
parse_filesystems: reading filesystems
parse_filesystems: sysfs (nodev)
parse_filesystems: rootfs (nodev)
parse_filesystems: ramfs (nodev)
parse_filesystems: bdev (nodev)
parse_filesystems: proc (nodev)
parse_filesystems: cgroup (nodev)
parse_filesystems: cpuset (nodev)
parse_filesystems: tmpfs (nodev)
parse_filesystems: devtmpfs (nodev)
parse_filesystems: debugfs (nodev)
parse_filesystems: securityfs (nodev)
parse_filesystems: sockfs (nodev)
parse_filesystems: pipefs (nodev)
parse_filesystems: anon_inodefs (nodev)
parse_filesystems: devpts (nodev)
parse_filesystems: ext3
parse_filesystems: ext2
parse_filesystems: ext4
parse_filesystems: hugetlbfs (nodev)
parse_filesystems: vfat
parse_filesystems: ecryptfs (nodev)
parse_filesystems: fuseblk
parse_filesystems: fuse (nodev)
parse_filesystems: fusectl (nodev)
parse_filesystems: pstore (nodev)
parse_filesystems: efivarfs (nodev)
parse_filesystems: mqueue (nodev)
parse_filesystems: xfs
parse_fstab: updating from /lib/init/fstab
update_mount: /: / /dev/root rootfs defaults check
update_mount: /proc: /proc none proc nodev,noexec,nosuid
update_mount: /proc/sys/fs/binfmt_misc: /proc/sys/fs/binfmt_misc none 
binfmt_misc nodev,noexec,nosuid,optional
update_mount: /sys: /sys none sysfs nodev,noexec,nosuid
update_mount: /sys/fs/cgroup: /sys/fs/cgroup none tmpfs 
optional,uid=0,gid=0,mode=0755,size=1024
update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl 
optional
update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional
update_mount: /sys/kernel/security: /sys/kernel/security none securityfs 
optional
update_mount: /sys/firmware/efi/efivars: /sys/firmware/efi/efivars none 
efivarfs optional
update_mount: /spu: /spu none spufs gid=spu,optional
update_mount: /dev: /dev none devtmpfs,tmpfs mode=0755
update_mount: /dev/pts: /dev/pts none devpts noexec,nosuid,gid=tty,mode=0620
update_mount: /tmp: /tmp none none defaults
update_mount: /run: /run none tmpfs noexec,nosuid,size=10%,mode=0755
update_mount: /run/lock: /run/lock none tmpfs nodev,noexec,nosuid,size=5242880
update_mount: /run/shm: /run/shm none tmpfs nosuid,nodev
update_mount: /run/user: /run/user none tmpfs 
nodev,noexec,nosuid,size=104857600,mode=0755
update_mount: /sys/fs/pstore: /sys/fs/pstore none pstore optional
parse_fstab: updating from /etc/fstab
update_mount: /: / LABEL=cloudimg-rootfs ext4 defaults
parse_mountinfo_file: updating mounts
update_mount: /: / /dev/disk/by-uuid/7d38a3ed-8f5b-49d4-8087-b1573a17bb98 ext4 
defaults
update_mount: /dev: /dev none tmpfs mode=0755
update_mount: /proc: /proc proc proc nodev,noexec,nosuid
update_mount: /proc/sys/net: /proc/sys/net proc proc 
rw,nosuid,nodev,noexec,relatime,rw
update_mount: /proc/sys: /proc/sys proc proc ro,nosuid,nodev,noexec,relatime,rw
update_mount: /proc/sysrq-trigger: /proc/sysrq-trigger proc proc 
ro,nosuid,nodev,noexec,relatime,rw
update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid
update_mount: /sys: /sys sysfs sysfs nodev,noexec,nosuid
update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs 
rw,relatime,rw
update_mount: /sys/devices/virtual/net: /sys/devices/virtual/net sysfs sysfs 
rw,relatime,rw
update_mount: /sys/fs/fuse/connections: /sys/fs/fuse/connections none fusectl 
optional
update_mount: /sys/kernel/debug: /sys/kernel/debug none debugfs optional
update_mount: /sys/kernel/security: /sys/kernel/security none securityfs 
optional
update_mount: /sys/fs/pstore: /sys/fs/pstore none pstore optional
update_mount: /var/log/juju: /var/log/juju 
/dev/disk/by-uuid/7d38a3ed-8f5b-49d4-8087-b1573a17bb98 ext4 
rw,relatime,rw,stripe=64,data=ordered
update_mount: /sys/fs/cgroup: /sys/fs/cgroup cgroup tmpfs 
optional,uid=0,gid=0,mode=0755,size=1024
update_mount: /sys/fs/cgroup/cgmanager: /sys/fs/cgroup/cgmanager none tmpfs 
rw,relatime,rw,size=4k,mode=755
update_mount: /dev/lxc/console: /dev/lxc/console devpts devpts 
rw,nosuid,noexec,relatime,rw,gid=5,mode=620,ptmxmode=000
update_mount: /dev/pts: /dev/pts 

[Bug 1285850] Re: interuppting lxc-clone can destroy source container

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1532069] Re: Can't create a container with a loop backing store in 1.0.8

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1532069

Title:
  Can't create a container with a loop backing store in 1.0.8

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1532069] Re: Can't create a container with a loop backing store in 1.0.8

[Stéphane Graber]

** Project changed: lxc => lxc (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532069

Title:
  Can't create a container with a loop backing store in 1.0.8

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1456422] Re: limit nofile 64000 64000 or similar in an upstart job fails in a user lxc

[Stéphane Graber]

Nothing LXC can do about it. An unprivileged container cannot have any
more right than the user which spawned it. Your user cannot  open that
many files therefore root in the container can't either.

** Changed in: lxc
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456422

Title:
  limit nofile 64000 64000 or similar in an upstart job fails in a user
  lxc

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1285850] Re: interuppting lxc-clone can destroy source container

[Stéphane Graber]

** No longer affects: lxc

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1285850

Title:
  interuppting lxc-clone can destroy source container

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456422] Re: limit nofile 64000 64000 or similar in an upstart job fails in a user lxc

[Stéphane Graber]

Nothing LXC can do about it. An unprivileged container cannot have any
more right than the user which spawned it. Your user cannot  open that
many files therefore root in the container can't either.

** Changed in: lxc
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mongodb in Ubuntu.
https://bugs.launchpad.net/bugs/1456422

Title:
  limit nofile 64000 64000 or similar in an upstart job fails in a user
  lxc

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1486073] [NEW] 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When cloning an unprivileged container with the "-s -B overlayfs" flags,
then starting this container and running a command like ``apt-get
update`` in the new container, a kernel error "Failed to whiteout" is
produced.

- Kernel error: http://pastebin.com/iajXHbHZ
- Kernel version: 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
- LXC version: 1.0.7

- Commands to reproduce:

lxc-clone -s -B overlayfs base test
lxc-start -n test -d
lxc-attach -n test
apt-get update


When executing the above commands, your terminal will hang, and you won't be 
able to destroy/stop the container anymore. The kernel log then also has the 
error linked above.

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


** Tags: overlayfs
-- 
'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7
https://bugs.launchpad.net/bugs/1486073
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1486073] [NEW] 'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When cloning an unprivileged container with the "-s -B overlayfs" flags,
then starting this container and running a command like ``apt-get
update`` in the new container, a kernel error "Failed to whiteout" is
produced.

- Kernel error: http://pastebin.com/iajXHbHZ
- Kernel version: 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
- LXC version: 1.0.7

- Commands to reproduce:

lxc-clone -s -B overlayfs base test
lxc-start -n test -d
lxc-attach -n test
apt-get update


When executing the above commands, your terminal will hang, and you won't be 
able to destroy/stop the container anymore. The kernel log then also has the 
error linked above.

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


** Tags: overlayfs
-- 
'Failed to whiteout' error in 14.04 with 3.19 kernel and LXC 1.0.7
https://bugs.launchpad.net/bugs/1486073
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1445539] [NEW] Can't create vivid lxc on trusty

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I create a vivid lxc in trusty like this:

lxc-create -t ubuntu -n vivid-lxc -- -r vivid

I get this error at the end:

Hit http://archive.ubuntu.com vivid-updates/universe Translation-en 

│··
Reading package lists... Done   

│··
Reading package lists... Done   

│··
Building dependency tree... Done

│··
Package lxcguest is not available, but is referred to by another package.   

│··
This may mean that the package is missing, has been obsoleted, or   

│··
is only available from another source   

│··
E: Package 'lxcguest' has no installation candidate 

│··

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: oil
-- 
Can't create vivid lxc on trusty
https://bugs.launchpad.net/bugs/1445539
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1445539] [NEW] Can't create vivid lxc on trusty

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I create a vivid lxc in trusty like this:

lxc-create -t ubuntu -n vivid-lxc -- -r vivid

I get this error at the end:

Hit http://archive.ubuntu.com vivid-updates/universe Translation-en 

│··
Reading package lists... Done   

│··
Reading package lists... Done   

│··
Building dependency tree... Done

│··
Package lxcguest is not available, but is referred to by another package.   

│··
This may mean that the package is missing, has been obsoleted, or   

│··
is only available from another source   

│··
E: Package 'lxcguest' has no installation candidate 

│··

** Affects: lxc (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: oil
-- 
Can't create vivid lxc on trusty
https://bugs.launchpad.net/bugs/1445539
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1521151] [NEW] init: lxc-instance main process terminated with status 255

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

We have a trusty host which has 9 trusty guests running under LXC.  On
the most recent reboot, 3 of the LXC processes crashed:

[   10.912793] init: lxc-instance (nz-prod-bdbbackup-akl3) main process (3175) 
terminated with status 255
[   11.031717] init: lxc-instance (au-prod-db-akl3) main process (2974) 
terminated with status 255
[   11.079716] init: lxc-instance (au-test-backup-akl3) main process (3042) 
terminated with status 255

We were able to manually start them afterwards, but it's not clear why
they crashed on boot.

Each of those containers has identical software configurations to at
least one of the 6 containers that didn't crash on boot, so it appears
to be random.

We're running the 3.13.0-68-generic kernel and LXC 1.0.7-0ubuntu0.10.
All other packages are current.

Here is a sample config:

# Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu
# Parameters passed to the template: -r trusty --user  --auth-key 
/home//.ssh/authorized_keys
# For additional config options, please look at lxc.container.conf(5)

# Common configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf

# Container specific configuration
lxc.rootfs = /var/lib/lxc/au-test-backup-akl3/rootfs
lxc.mount = /var/lib/lxc/au-test-backup-akl3/fstab
lxc.utsname = au-test-backup-akl3
lxc.arch = amd64

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.hwaddr = 00:16:3e:9e:7c:41
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br1
lxc.network.hwaddr = 00:16:3f:18:88:d9
lxc.start.auto = 1

And fstab:

/var/backups/au-test-backup-akl3 var/backups bind defaults,bind 0 0

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

-- 
init: lxc-instance main process terminated with status 255
https://bugs.launchpad.net/bugs/1521151
You received this bug notification because you are a member of Ubuntu Server 
Team, which is subscribed to lxc in Ubuntu.

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521151] [NEW] init: lxc-instance main process terminated with status 255

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

We have a trusty host which has 9 trusty guests running under LXC.  On
the most recent reboot, 3 of the LXC processes crashed:

[   10.912793] init: lxc-instance (nz-prod-bdbbackup-akl3) main process (3175) 
terminated with status 255
[   11.031717] init: lxc-instance (au-prod-db-akl3) main process (2974) 
terminated with status 255
[   11.079716] init: lxc-instance (au-test-backup-akl3) main process (3042) 
terminated with status 255

We were able to manually start them afterwards, but it's not clear why
they crashed on boot.

Each of those containers has identical software configurations to at
least one of the 6 containers that didn't crash on boot, so it appears
to be random.

We're running the 3.13.0-68-generic kernel and LXC 1.0.7-0ubuntu0.10.
All other packages are current.

Here is a sample config:

# Template used to create this container: /usr/share/lxc/templates/lxc-ubuntu
# Parameters passed to the template: -r trusty --user  --auth-key 
/home//.ssh/authorized_keys
# For additional config options, please look at lxc.container.conf(5)

# Common configuration
lxc.include = /usr/share/lxc/config/ubuntu.common.conf

# Container specific configuration
lxc.rootfs = /var/lib/lxc/au-test-backup-akl3/rootfs
lxc.mount = /var/lib/lxc/au-test-backup-akl3/fstab
lxc.utsname = au-test-backup-akl3
lxc.arch = amd64

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.hwaddr = 00:16:3e:9e:7c:41
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br1
lxc.network.hwaddr = 00:16:3f:18:88:d9
lxc.start.auto = 1

And fstab:

/var/backups/au-test-backup-akl3 var/backups bind defaults,bind 0 0

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

-- 
init: lxc-instance main process terminated with status 255
https://bugs.launchpad.net/bugs/1521151
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs