+1
For the record, Snap being forced upon users for critical packages is
the primary reason why I recently dropped Ubuntu and stopped
recommending the distro to others, after using it for over 15 years.
Container-based packaging has its place. Snap has some interesting
features compared to FlatPa
Still broken in disco.
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to initialize ecryptfs keys
Status
The systemd patch I posted earlier no longer works in disco, and the
workarounds posted here only partially fix the problem and only for a
subset of use cases. Looks like we're back to needing a proper fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Public bug reported:
Adding lxc.cgroup.devices.allow directives to an unprivileged container
config prevent the container from starting. These lxc-start errors look
relevant:
lxc-start testbox 20190910192712.171 WARN cgfsng -
cgroups/cgfsng.c:get_hierarchy:204 - There is no useable devices
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails to
*** This bug is a duplicate of bug 1718658 ***
https://bugs.launchpad.net/bugs/1718658
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1718658
ecryptfs-mount-private fails to initialize ecryptfs keys
--
You rece
The ecryptfs-manager workaround helps the mount to succeed, but (at
least in my case) the system refuses to unmount it afterward. This is a
problem for those of us who open our ecryptfs volumes only for as long
as they're needed.
--
You received this bug notification because you are a member of U
This is a systemd bug, created by this commit:
https://github.com/systemd/systemd/commit/74dd6b5
It looks like poettering has attempted to address it in more recent
versions of systemd (though that doesn't help us in ubuntu 17.10):
https://github.com/systemd/systemd/pull/6832
--
You received t
Here's a simple patch to disable the broken systemd feature, and restore
ecryptfs functionality.
** Patch added: "disable_system_service_session_keyrings.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718658/+attachment/5038578/+files/disable_system_service_session_keyrings.pat
A systemd build with my patch applied is available here:
https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Here's a first attempt:
https://github.com/lxc/lxc-pkg-ubuntu/pull/2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to d
Public bug reported:
PackageKit-based tools, such as pkcon and pk-update-icon, do not respect
Ubuntu phased updates. As far as I can tell, they do not provide a way
to access or react to the Phased-Update-Percentage field in an apt
package index at all.
The result is that utilities based on Packa
** Bug watch added: freedesktop.org Bugzilla #91887
https://bugs.freedesktop.org/show_bug.cgi?id=91887
** Also affects: tango-icon-theme via
https://bugs.freedesktop.org/show_bug.cgi?id=91887
Importance: Unknown
Status: Unknown
--
You received this bug notification because you ar
** Changed in: network-manager-applet (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-icon-theme in
Ubuntu.
https://bugs.launchpad.net/bugs/772709
Title:
Network Manager Ic
Removing nm-applet-use-indicator.patch (and refreshing the patches that
depend on it) fixes this in Xubuntu. In other words, that patch causes
the regression.
I'm removing the invalid status on network-manager-applet (Ubuntu), in
hopes of getting someone to reevaluate this. If Ubuntu maintainers a
I also created an upstream bug report against the Tango icon theme,
mainly to get more eyes on the problem. Honestly, though, I don't expect
every icon theme developer will want to to modify their software in
order to compensate for something that was broken by an Ubuntu-specific
patch.
--
You re
Also, this is a security problem. It robs the user of the ability to
easily see that the VPN is (still) connected. If the VPN goes down, and
the user doesn't happen to see the momentary pop-up message (or if that
message has been accidentally or deliberately suppressed), the user will
think his com
Chris, I have no way to test this, because I no longer have a filesystem
with multiply-claimed blocks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1321418
Title:
fsck
Public bug reported:
After upgrading to Ubuntu 17.04 (zesty), resolution of my local
network's host names is completely broken. Apparently the upgrade
replaced my existing resolver with systemd-resolve, which deliberately
refuses to pass "single-label" domain names to my domain name server.
That
According to the systemd documentation, UseDomains only affects systems
that get their network setup from DHCP, which is not the case at my
site. Furthermore, it is documented as a way to add a DNS search
domain, which would not help resolve hosts that have no domains.
So far, the only way I have
No, that won't help either.
You don't seem to understand: Adding a domain search list will not help
because the local machines do not have domains. They only have names,
like "host1" or "beetle", even on the network's DNS servers.
Since systemd's resolver refuses to consult the name servers for n
Problem still exists in Ubuntu 16.10.
** Summary changed:
- starting any container with umask 007 breaks lxc-stop and prevents host
system shutdown
+ starting any container with umask 007 breaks host system shutdown. lxc-stop
just hangs.
--
You received this bug notification because you are a
I hate to say this, folks, but ecryptfs looks like a dead end for us.
It's no longer supported by Ubuntu (the package has been moved to the
Universe repo). Also, the problem at hand is caused by systemd, which is
run by a man famous for releasing poorly-vetted, system-breaking
software, and then re
** Bug watch added: github.com/heftig/rtkit/issues #22
https://github.com/heftig/rtkit/issues/22
** Also affects: rtkit via
https://github.com/heftig/rtkit/issues/22
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
My /tmp folder has dozens of empty folders with names like grilo-plugin-
cache-ABCDEF. I don't know anything about grilo-plugins, but surely they
can do their job without leaving endless garbage directories behind when
they're done?
$ lsb_release -a
No LSB modules are availab
** Bug watch added: gitlab.gnome.org/GNOME/grilo-plugins/-/issues #70
https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70
** Also affects: grilo-plugins via
https://gitlab.gnome.org/GNOME/grilo-plugins/-/issues/70
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
When I use the ps command's "lxc" format specifier, for example:
ps -eo pid,lxc,command
The second output column is supposed to show "the name of the lxc
container within which a task is running. If a process is not running
inside a container, a dash ('-') will be shown." [
The top command's LXC column (not shown by default, but can be enabled
through the 'f' menu) also shows a - for all processes, including those
that belong to containers.
My containers are unprivileged, in case that matters.
--
You received this bug notification because you are a member of Ubuntu
Sure. Is this the right place?
https://github.com/lxc/lxc-pkg-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to d
Public bug reported:
Gstreamer 0.10 stops processing certain flac files before their end is
reached. When it happens, no error condition is reported. It fails
silently, as if the file was truncated.
This affects all applications that use gstreamer0.10-plugins-good,
including clementine, exaile, s
** Patch added: "0010-flacparse-avoid-indefinite-search-for-frame-end.patch"
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+attachment/4366258/+files/0010-flacparse-avoid-indefinite-search-for-frame-end.patch
--
You received this bug notification because you are
** Patch added: "0011-flacparse-additional-frame-crc-check.patch"
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+attachment/4366259/+files/0011-flacparse-additional-frame-crc-check.patch
--
You received this bug notification because you are a member of Ubuntu
Tou
I have attached 3 upstream patches to fix the premature eos on some flac
files:
0010-flacparse-avoid-indefinite-search-for-frame-end.patch
0011-flacparse-additional-frame-crc-check.patch
0012-flacparse-additional-header-sanity-check.patch
These are suitable for adding to the debian/patches direct
** Patch added: "0012-flacparse-additional-header-sanity-check.patch"
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1440440/+attachment/4366260/+files/0012-flacparse-additional-header-sanity-check.patch
--
You received this bug notification because you are a member of Ub
All I have is a couple of files that trigger the bug. Unfortunately, I
don't have the rights to post them publicly, and I haven't found a way
to extract a useful segment from them without remuxing (and hiding the
problem).
--
You received this bug notification because you are a member of Ubuntu
T
I discovered the problem with Exaile, Totem, and Sound Converter. I
verified it and narrowed it down with gst-launch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-good0.10 in
Ubuntu.
https://bugs.launchpad.net/b
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1390792
Title:
Synapti
Which branch?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1389954
Title:
Make .lxc domain name resolution easier to discover and enable
Status in lxc package in Ubuntu:
Okay, I've written up a short README.Debian describing the necessary
changes to /etc/default/lxc-net and the dnsmasq config file. I don't
remember what steps are necessary to make the domain names accessible,
though, and I'd like to include those steps in the readme.
Do I have to restart the lxc-n
Thanks for taking an interest in the issue.
Since I filed this specifically against lxc in Ubuntu, wouldn't it make
sense to start by documenting the necessary config changes (including
NetworkManager's dnsmasq config, since it is part of Ubuntu by default)
in /usr/share/doc/lxc/README?
--
You r
On Mon, 13 Apr 2015 13:32:15 -, Robie Basak wrote:
>A release
>upgrade should not cause biosdevname to get installed. So can you (or
>someone) please confirm that this is definitely the behaviour in some
>case,
It has now been most of a year since I filed the bug report, so as you might
imagi
Public bug reported:
If I run lxc-start with umask 007 (or any other value that masks the
world-execute bit), my host system enters a state with the following
problems:
* lxc-stop hangs forever instead of stopping any container, even one that
wasn't started with umask 007.
* lxc-stop --kill --no
Possibly related: when the problem is triggered, I notice that my guest
instances start with no /etc/resolv.conf and no inet address.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bu
** Description changed:
If I run lxc-start with umask 007 (or any other value that masks the
world-execute bit), my host system enters a state with the following
problems:
* lxc-stop hangs forever instead of stopping any container, even one that
wasn't started with umask 007.
* lxc-s
** Description changed:
If I run lxc-start with umask 007 (or any other value that masks the
world-execute bit), my host system enters a state with the following
problems:
* lxc-stop hangs forever instead of stopping any container, even one that
wasn't started with umask 007.
* lxc-s
** Description changed:
- If I run lxc-start with umask 007 (or any other value that masks the
- world-execute bit), my host system enters a state with the following
- problems:
+ If I have umask 007 (or any other value that masks the world-execute
+ bit) when I run lxc-start for the first time af
Linux xenialbox 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1642767
Title:
start
I reproduced it with the latest mainline kernel as well:
Linux xenialbox 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20
22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Here's the slightly different syslog output:
Nov 22 14:36:55 xenialbox kernel: [ 484.506570] INFO: task systemd:3086
bl
Public bug reported:
Both of these scripts do the same thing, and both are installed by
x11-common:
/etc/X11/Xsession.d/35x11-common_xhost-local
/etc/X11/Xsession.d/60x11-common_localhost
35x11-common_xhost-local is present in debian, while
60x11-common_localhost is not. I suspect the latter sho
Public bug reported:
The lxc package installs dnsmasq configuration as
/etc/dnsmasq.d-available/lxc, and a symlink to it is created at
/etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
instance on systems running NetworkManager, because NetworkManager
starts a dnsmasq instance tha
** Description changed:
The lxc package installs dnsmasq configuration as
/etc/dnsmasq.d-available/lxc, and a symlink to it is created at
/etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
instance on systems running NetworkManager, because NetworkManager
starts a dnsmasq
Public bug reported:
The lxc package on ubuntu does almost nothing to help a user enable DNS
resolution for containers via dnsmaq, let alone discover that it is
possible. How about enabling it by default? I think all it would take is
adding server=/lxc/10.0.3.1 to a file in /etc/NetworkManager/dns
For the record:
This happened to me during a distribution upgrade from 13.10 (saucy) to 14.04
(trusty). When it happened, the release upgrade tool interrupted itself with a
dialog box containing this alarming and not very helpful message:
Could not install the upgrades
The upgrade has aborted. Y
Here's a cleaner variation of the workaround:
sudo dpkg --purge --force-depends libpostproc52
sudo apt-get install libpostproc52
sudo apt-mark auto libpostproc52
The first line purges the package without removing any of the packages
that depend on it. (This is fine, since we're going to reinstall
Public bug reported:
Relatively recent linux distribution upgrades have been causing
computers' ethernet devices to be unexpectedly renamed. While I
understand that consistent device naming solves problems on some systems
(mostly multi-NIC servers and a few specialty embedded devices),
unilaterall
** Description changed:
Relatively recent linux distribution upgrades have been causing
computers' ethernet devices to be unexpectedly renamed. While I
understand that consistent device naming solves problems on some systems
(mostly multi-NIC servers and a few specialty embedded devices),
** Tags added: regression-release saucy
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1247719
Title:
crackling, popping, clicking in playback t
This bug completely breaks WiFi support on my system using ConnMan. Took
a bit to hunt down and I also wrote my own patch before finding this bug
report. Can we please get this fix pushed out?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I'm actually a bit confused -- the bug status is "fix released" but it
is not at all clear to me in what Ubuntu release this fix has been
applied. Can someone clarify this for me?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Question: Why are --force-yes and --assume-yes not honored as they are
when checking authenticity of binaries?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1329274
Title:
ap
Or at least just --force-yes. --assume-yes is not sufficient to bypass
the authenticity check without a prompt. I gather there is a desire to
avoid prompting.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
htt
61 matches
Mail list logo
