This seems to have been solved after updating kernel and graphics
drivers to the current LTS version backports.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1319535
Title:
ing to solve this bug, I
would be willing to lend our server for some weeks.
Regards, Jens
--
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/1587142
Title:
Shutdown hangs in md
Not working export with xkbcomp $DISPLAY
** Attachment added: "output-neo2-not-working.xkb"
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+attachment/5149977/+files/output-neo2-not-working.xkb
--
You received this bug notification because you are a member of Ubuntu
Working output with xkbcomp $DISPLAY
** Attachment added: "output-neo2-working.xkb"
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/879838/+attachment/5149978/+files/output-neo2-working.xkb
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I just hit this bug too and can confirm it for 17.10 and 18.04.
However, there is an easy workaround: Make sure Neo2 is the only layout
in your XKB keymap. The easiest way would be to have just one layout.
Another solution for me is to have exactly 4 layouts and Neo2 is the
4th. Checking with
Public bug reported:
6.0-8ubuntu1_i386.deb (--unpack):
Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.26/changelog.Debian.gz«
zu überschreiben, welches verschieden von anderen Instanzen des Paketes
libperl5.26:i386 ist
Fehler traten auf beim Bearbeiten von:
I followed the steps from #27 and everything works fine now on 16.04.3
with a SuperMicro Board X11SSH-F with Intel C236 Chipsets RST and two
sata disks as Raid 1.
I can also confirm #28, the first reboot still needed a hard reset and a
rebuild of the Raid 1, but after this, every (>10) shutdown
Public bug reported:
Fehlermeldung:
dpkg: Fehler: Dateideskriptorflags für »« können nicht gelesen werden: Ungültiger Dateideskriptor
beim Installieren eines deb-Paketes mit Paket-Instalaationsprogramm
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
gdebi:
Public bug reported:
I use a USB printer Samsung ML-1640. Since the latest ubuntu upgrade the
printer does not start to print anymore when I send a print job via
libreoffice or evince. The printer queue says its processing the print
job but nothing happens. By trial and error I found that it is
I am/was also affected by this bug and can confirm that it is caused by
leftover files from a former sendmail installation.
Because of this, I'll add the sendmail package to the bug.
Reinstalling sendmail removed the bug.
Doing an apt-get purge on all sendmail-related packages also removed the
Not an issue anymore. Printing works fine now.
** Changed in: cups (Ubuntu)
Status: New = Fix Released
** Changed in: cups (Ubuntu)
Status: Fix Released = Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
Obviously lxc does NOT depend on dnsmasq-base and thus this dependency
should be lowered to optional or recommended.
Today entities using containers already have proper DNS as well as DHCP
servers and thus do not need at all another point of failure/possible
weak
Public bug reported:
Defining USE_LXC_BRIDGE and than overwriting it unconditionally in the
source /etc/default/lxc-net doesn't make sense/is confusing.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
Public bug reported:
When one creates a incorrect profile, apparmor_parser seems to leave an
artifact of the problem file in the same directory, which in turn
leads to another error, when the file gets fixed. Not sure, how appamor
stuff works, but this is simply an unacceptable behavior! It
Well, it is strange: If there is such a setting in /etc/default/lxc, one
usually assumes, that this is the master of the disaster and gets
propagated downwards, but obviously it is not ... And thus I wonder,
which files in the lxc forest need to be checked as well to avoid
further surprises ...
Probably because this piece of junk (upstart) just silently discards any
*.conf file with errors/unknown directives in it instead of
reporting/logging the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in
# https://wiki.ubuntu.com/DebuggingPrintingProblems#USB_printer
#
2.
jens@blackbox:~$ lsmod | grep usb
usblp 23075 0
usbhid 53121 0
hid 106436 4 hid_generic,usbhid,hid_logitech_dj
3.+4.
jens@blackbox:~$ tail -f /var/log/syslog
Aug
** Attachment added: error_log
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1351351/+attachment/4179330/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
** Changed in: cups (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1351351
Title:
Printer does print only after reconnect
Status in
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271452/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271455/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271454/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271456/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271459/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271458/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271457/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271460/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271463/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271464/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271465/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271466/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271467/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271468/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271471/+files/Xrandr.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271469/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271470/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271462/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271461/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271472/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xserver.errors.txt
https://bugs.launchpad.net/bugs/1391652/+attachment/4271473/+files/xserver.errors.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
@Christopher M. Penalver: This bug is still incomplete as the TO did not
respond for more that 2 months now. I can reproduce it reliably on a
Thinkpad T500 Bios 6FET93WW (3.23 ) (duplicate 1414778). What
information do you need?
--
You received this bug notification because you are a member of
)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1768): WARNING **: Failed to load user image: Failed
to open file '/home/jens/.face': Permission denied
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1768): WARNING **: Failed to load user image: Failed
to open file '/home/jens/.face': Permission denied
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting
(38 days ago)
InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
LightdmGreeterLog:
** (lightdm-gtk-greeter:1768): WARNING **: Failed to load user image: Failed
to open file '/home/jens/.face': Permission denied
g_dbus_connection_real_closed: Remote peer vanished
Public bug reported:
'pgrep upstart-udev-bridge' should definitely spit out a pid, but it
doesn't. When one uses the option -f than it actually prints the PID of
the upstart-udev-bridge process. However using -f is a bad workaround,
because than (at least wrt. the man page) the arguments and
I can confirm this bug using Thinkpad T420 with nvidia optimus enabled
and proprietary driver. Is there any update on this or any workaround?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
I've updated the BIOS.
xorg (or is it gnome-shell?) still hangs, but without any ACPI-warnings
this time.
The bios version as requested is:
A19
09/07/2012
There are still some warnings during startup:
Jan 10 22:01:33 jens-XPS-L702X kernel: [3.753967] [Firmware Bug]:
ACPI(PEGP) defines _DOD
First I want to point out that I had to reinstall my system a week ago.
While I still have trouble to print its not the same syptom it was
before. Now I am not able to print anything anymore, independent from
when I connect the printer to the computer. However, I have tried all
the modifications
Public bug reported:
Ubuntu documentation states, that changing /etc/gai.conf is the way to
be able to prefer IPv4 over IPv6.
So from the original gai.conf we removed the comment in front of the precedence
statements AND set the value for :::0:0/96 to 60.
Unfortunately this does not seem to
Actually that's not the same at all, because $cgroup != $lxc_name . Your
workaround is absolutely user UNfriendly, i.e. still hard to read and
for casual users inconvinient, because one needs supply all that many
format options ...
Anyway, I agree, that these utils should support such things out
Yepp, and that's IMHO a design flaw. E.g. if one wants to distribute the
load on iots storage, it might make sense, to distribute the zones of
several storage devices, e.g. zone1 on JBOD1, zone2 on JBOD2, etc
As said, the only thing, which lxc nees to track is a single config
directory which
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jens 2464 F pulseaudio
/dev/snd/controlC0: jens 2464 F pulseaudio
BuildID: 20150112203438
Channel: Unavailable
Date: Mon Jan 26 21:05:56 2015
EcryptfsInUse: Yes
Extensions
Public bug reported:
Right now lxc does a pretty poor job wrt. managing containers, i.e. one
needs to know, where containers have been installed to be able to
access/use/manage them (option -P dir) unless they've been installed in
the default location. Even if one knows the install path, it is
** Package changed: upstart (Ubuntu) = lxc (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/1424233
Title:
RFE lxc: lxc should do a better jon of housekeeping
Public bug reported:
Container management/monitoring is currently a pain, because procps do
not support container, i.e. there is no way to tell the tools to
filter the output wrt. a certain zone or to add a column, which shows
the zone name a process belongs to.
E.g. for what is needed:
Please read carefully! This bug is not about upstart-udev-bridge or any
other service but about PGREP . 'pgrep upstart-udev-bridge' is just an
example, which should work on any Ubuntu, i.e. to reproduce the problem!
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
1. Lock the screen
2. Try to log in and find the entire screen is white, except for the mouse
cursor
3. Pressing any keys on the keyboard does not change anything
4. Pressing any mouse button makes the login screen visible the way expected.
This happens since the upgrade to
-ckt2
Uname: Linux 3.16.0-29-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jens 2464 F pulseaudio
/dev/snd/controlC0: jens 2464 F
I'm running utopic with latest updates. Any container, which has systemd
running simply hangs, when /sbin/init gets started (no matter, whether
config has 'lxc.kmsg = 0' or not). Tried it previously with a trusty and
today with a vivid container. So wondering, whether there is a bugfix
available
It appears, that something is still broken. Because systemd doesn't
work, I installed upstart + upstart-sysv (and uninstalled systemd-
sysv), but unfortunately sssd doesn't come up (has exactly the same
config, as in other 14.10 zones, where it works as expected). And
because sssd doesn't come
Public bug reported:
On my Nexus 4 running Ubuntu Touch from channel Stable (presently
Ubuntu 14.10 r19) the welcome screen always shows No data sources
available, no matter if the option is selected or not in the settings.
Is the problem known and will it be solved soon?
** Affects:
:56, Jens Becker escibió:
Silly question: How do I install the fix? Settings says there are no
updates available!?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https
Silly question: How do I install the fix? Settings says there are no
updates available!?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to telepathy-mission-
control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1476781
Title:
I have the same issue. Not a solution, but a good work around for me was
to turn on the onscreen keyboard in the universal access settings.
This leads to a (fallback?) old school login screen which has no problem
with the finger print reader.
--
You received this bug notification because you
As dash is used to replace bash for non-interactive shells, dash should
reproduce the bash syntax of the `local` keyword as best as it can.
I agree with Dan's comment #7 "the above DASH behaviour is broken, for
all three uses "local", "export", and "readonly". BASH is correct, and
DASH should be
Today I upgraded our last utopic containers (~10) to vivid using do-
release-upgrade: Everywhere the same: after reboot systemd is the only
thing which is running in the container, but nothing else happens. It
doesn't start anything! So the only way to get the stuff fixed is to
manually attach to
Any update if this fix will go into 16.04 LTS?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1580577
Title:
python2.7 crashes with SegFault when running Zope
Status
Sorry for impatience. I just found it is already in proposed updates.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1580577
Title:
python2.7 crashes with SegFault when
Public bug reported:
When a users having tcsh as its [login] shell presses tab key
(autocompletion), tcsh coredumps immediately, always:
admin.python ~ > gdb tcsh
GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git
...
(gdb) run
Starting program: /local/home/admin/tcsh
admin.python
Public bug reported:
After a clean install of Ubuntu 16.10 it is not possible to install the
package "mythtv-frontend" because it depends on the package "transcode".
The package "transcode" is not available anymore. It seems that in 16.10
a special package for transcoding purposes in mythtv was
I am another Dell XPS 15 owner who is affected by this bug using 16.10.
Please incorporate the fix as soon as possible, as the normal end user
(e.g. my wife) is not willing to kill dnsmasq each time the notebook
wakes up from suspend.
--
You received this bug notification because you are a
The bug/subject here is, that apt-get doesn't return a proper exit code,
not, what else one could use to workaround the bug.
Saying, that update from one of all (i.e. 1+) sites is sufficient is
like going to fly with a jet, where one of two engines is already broken
before it starts. Making this
Actually this is the problem: Users think, their system is up-to-date,
but it is not for sure because a site failed to respond. Therefore only
if _all_ sites answered the request properly, apt-get should return 0.
If not, it should return a specified return code, which lets the callee
know, that
Public bug reported:
Since on common platforms ureadahead solves nothing but causes a huge
amount of garbage/totally useless error messages, which makes it really
hard to extract the important messages from e.g. journalctl output, it
should be removed from ubuntu-minimal. If there are people,
AFAICS the problem is libmount/src/context_mount.c:exec_helper() which
is uses operands in a wrong/not posixly incorrect way. See also
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
When running 'apt-get update' (e.g. on a container install post-install
script), apt-get return with exit code 0, even so it wasn't able to
"update" properly. E.g.:
+ apt-get update
Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Temporary failure resolving
Public bug reported:
"/bin/mount -t zfs -o defaults,atime,dev,exec,rw,suid,nomand,zfsutil
rpool/zones/bla /zones/bla"
fails, if env var POSIXLY_CORRECT is set, because it calls
"/sbin/mount.zfs rpool/zones/bla /zones/bla -o rw,zfsutil", which is obviously
a bug. Options should always come first
mount from util-linux 2.27.1 (libmount 2.27.0: selinux, assert, debug)
Description:Ubuntu 16.04.2 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1692109
Title:
Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not
able to update properly and thus the result of the operation is
unreliable. So its like "your connection is secured, but may be not". I
guess most people wouldn't do any financial transaction when reading
this ... ;-)
--
You
Hi,
had the same problem with a pptp vpn (don't ask why we use pptp). As
described i had to set the MTU of the physical network adapter (e.g.
eth0) to 1000 to get the VPN working without disconnectes all the time.
You can set the MTU easily via the network manager on the "ethernet"
tab, but you
properties:
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf434 irq 142"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
Confirmed, except for me it always resets to 100%. That's far too high,
I need it to be around 50% or so. Either way, the resetting is very
annoying.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
*** This bug is a duplicate of bug 1688018 ***
https://bugs.launchpad.net/bugs/1688018
@rouniy @m-witte-d
Hi,
locking down the packages resulted in breaking gdm3 in my installation of
ubuntu-gnome 16.04.4.
That's because gdm3 has a inherited dependency on libnm0 (>=
No, this is not an option. Also note, that this breaks a lot of
workflows without reason, because Ubuntu ssh client simply stops
working with a message like "~/.ssh/config line 3: Bad SSH2 cipher spec
'...'": it simply does not know such ciphers (does not ignore them). So
especially in
Public bug reported:
In bionic openssh client/server ships without blowfish-cbc, arcfour,
arcfour128, arcfour256 and cast128-cbc. Unfortunately they are required
for backward compatibility, especially for embedded devices, which do
not support other ciphers (e.g. Rittal Liquid Cooling Package for
I can confirm the workaround in #92 for my 16.04.3 LTS installation.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/120
Title:
network manager openvpn dns
I found another workaround, that works fine without changing package versions
or DNS servers.
It is tested with the issues I had with openconnect for NM.
it is "just" killing the dnsmasq instance and it gets restarted
automatically which then results in a working system again. It easy and
not
Lenovo Ideapad 2 13 (2 in 1 convertible, touchscreen)
Ubuntu 18.04 (+ 17.10, + 16.04)
even after installing 18.04 and the latest updates on Jan 2nd 2018 the
following feature persists:
a few times a week the cursor goes nuts - it looks like it's jumping to the
lower left corner (gnome
Public bug reported:
After upgrading to Ubuntu 18.10 I can't run eagle:
./eagle: symbol lookup error: /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0:
undefined symbol: xcb_dri3_get_supported_modifiers
https://www.autodesk.com/products/eagle/free-download
libglx-mesa0:
Installed:
I also ran into the problem but solved it by downgrading systemd:
> apt install systemd=229-4ubuntu4 libsystemd0=229-4ubuntu4
> apt-mark hold systemd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
# apt install lxc-templates
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
busybox-static cloud-image-utils debootstrap dirmngr distro-info genisoimage
gnupg gnupg-l10n
I think the original report was against the UOA implementation which
does no longer exist anyway
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-control-center-
signon in Ubuntu.
https://bugs.launchpad.net/bugs/1080591
Public bug reported:
> + do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
Get:2 Upgrade tool [1,263 kB]
Fetched 1,264 kB in 0s (0 B/s)
It has to answer unicast M-SEARCH. That's in the UPnP spec and
validation test suite.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp in Ubuntu.
https://bugs.launchpad.net/bugs/1799977
Title:
[MIR] gssdp
Status in
Łukasz Zemczak, yes, upgraded a machine from bionic to focal - same
problem. However, the patch looks not optimal but sufficient.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
If one creates e.g. /etc/systemd/network.cu and /etc/systemd/network.fc
and symlinks /etc/systemd/network to one of them, network setup will
fail on reboot, because /usr/share/initramfs-tools/hooks/udev does a
very poor job: it simply checks for a directory instead of the
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
If one sets in /etc/default/grub (as e.g. desired by facebook oomd):
GRUB_CMDLINE_LINUX="systemd.unified_cgroup_hierarchy=1 swapaccount=1 ..."
lxc is not able to start any
Public bug reported:
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename: focal
lxc-stop -r -n $zone
Stops the container, but does not reboot it anymore, as in bionic.
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
--
You
Hmmm, that's an old one. IIRC the real root cause was, that some files
possibly included via /usr/share/lxc/config/ubuntu.common.conf still
used lxc.cgroup.devices.* instead of lxc.cgroup2.devices.* (the machine
was upgraded from bionic to focal).
--
You received this bug notification because
Public bug reported:
If one starts dhcrelay with explicitly specifying the interfaces to
listen,it silently ignores these options and still listens on all
interfaces. This is neither what the man page says (it says, only if no
interface is given, it listen on all interfaces), nor what is needed.
1 - 100 of 125 matches
Mail list logo
