Public bug reported:
$ pwd
/usr/share/doc/openssl
$ ls -l
total 52
lrwxrwxrwx 1 root root30 mars 31 08:42 changelog.Debian.gz ->
../libssl3/changelog.Debian.gz
lrwxrwxrwx 1 root root23 mars 31 08:42 changelog.gz ->
../libssl3/changelog.gz
lrwxrwxrwx 1 root root20 mars 31 08:42
I'm not that invested in the having openssh-server installed but not
running use-case, but in general people do not like their local
configuration beeing overridden on package upgrades in this manner.
I could image people having it installed for the man-pages, or maybe
using other units for it
Public bug reported:
the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code
snippet:
if [ "$action" == configure ]; then
..snip..
if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then
..snip..
if [ -d /run/systemd/system ]; then
# Make sure ssh.service is
Public bug reported:
Recently introduced sshd-socket-generator for socket activation in
openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or
ListenAddress entries in the sshd configuration.
If you have multiple Port or ListenAddress and one of them is for port
22, it just skips
Please consider backporting for Focal (20.04) at least. The backport is
trivial and applies cleanly as-is except for patch offsets.
Might be wise to test some other combinations though. For example hosts
without this commit, running nspawn containers with it.
--
You received this bug
Just tested, and can confirm backporting
e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 to focal's systemd fixes the
segfaults when using machinectl shell on a Jammy host trying to start a
shell in a Focal nspawn container.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
systemd upgrades are now failing in my build chroots, and I suspect it
is related to this change.
Setting up systemd (234-2ubuntu12.3) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
[/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace specifiers:
Sorry, a correction (copy paste error):
Which should be matched by
owner @{PROC}/@{pid}/task/[0-9]*/comm rw,
in /etc/apparmor.d/abstractions/libvirt-qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
If your kernel.pid_max sysctl is set higher than the default, say at 7
digits, the @{pid} variable no longer matches all pids, causing some
breakage in any profile using it.
@{pid} is defined in /etc/apparmor.d/tunables:
Yup, this package fixes it on my systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1578022
Title:
dmidecode fails to output smibios 3.0 info
To manage notifications about this bug go to:
The following two upstream patches is needed to fix this (on my system):
Let read_file return the actual data size
http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=de9a74e1c60210bee229fcf55b1678a99d1b44dd
dmidecode: Use read_file() to read the DMI table from sysfs
Recent BIOS upgrades from Asrock Rack is also hitting this, for example
v2.10 for the dual socket Xeon EP2C612D16-2L2T board.
For Asrock at least SMBIOS 3.0 seems to have arrived with Broadwell-EP
CPU support (Xeon E5 v4).
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
On my KVM guests, rngd starts before the virtio /dev/hwrng device is
ready, and promptly crashes.
I dont have any bug reporting tools on this system, but there should be
enough information.
Ubuntu Core 15.04 x64, dpkg edition
systemd boot
kernel 4.1.2 (not ubuntu, but very
On some systems, watchdog not starting at boot can lead to infinite
system reset loops.
Better behaved hardware watchdogs starts the counter on first open/write
to /dev/watchdog and thus not starting on boot is not fatal, but will
cause system lockups to go undetected.
--
You received this bug
Debian 8.0 is now released with amavisd-new 2.10.1
Ubuntu 15.04 still ships 2.7.1, same as debian oldstable
What is happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357424
Title:
Please
Debian 8.0 is now released with amavisd-new 2.10.1
Ubuntu 15.04 still ships 2.7.1, same as debian oldstable
What is happening.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1357424
I see what I think is this bug on 3 different computers running 13.10, 2
installed with 13.10, 1 upgraded from 12.10.
Often what ssh agent is tried depends on how I start the terminal - the
agent environment is set differently if started from the dash, launcher
or alt-ctrl-t. And sometimes they
I dont like doing me too's, but I do see it as well across all of my
computers after I upgraded to 13.10.
While not really important in itself it is one of those things that just
gets to you and makes things feel very unfinished.
--
You received this bug notification because you are a member of
Note that the move to upstart for php5-fpm happened with Ubuntu 13.10
Its not relevant for older releases.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload
Public bug reported:
reload php5-fpm with upstart does not work.
php5-fpm will crash and leave non-working child processes hanging around
that will block any recovery until they are killed off manually.
This is because php5-fpm does not handle SIGHUP. It results in an
uncontrolled exit. After
Note that the move to upstart for php5-fpm happened with Ubuntu 13.10
Its not relevant for older releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242376
Title:
reload php5-fpm crashes
To
Public bug reported:
reload php5-fpm with upstart does not work.
php5-fpm will crash and leave non-working child processes hanging around
that will block any recovery until they are killed off manually.
This is because php5-fpm does not handle SIGHUP. It results in an
uncontrolled exit. After
Public bug reported:
Getting weekly cron warning emails during logrotation after php5-fpm
package switched to upstart in Saucy.
root@ops:~# lsb_release -rd
Description:Ubuntu Saucy Salamander (development branch)
Release:13.10
root@ops:~# apt-cache policy php5-fpm
php5-fpm:
Public bug reported:
Getting weekly cron warning emails during logrotation after php5-fpm
package switched to upstart in Saucy.
root@ops:~# lsb_release -rd
Description:Ubuntu Saucy Salamander (development branch)
Release:13.10
root@ops:~# apt-cache policy php5-fpm
php5-fpm:
Dia does not even start with a blank sheet anymore - this bug renders
the package completely unusable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1152135
Title:
dia-gnome crashed with SIGSEGV in
While IPv6 only networks are quite uncommon still (though they do
exist), not having services on IPv6 has implications for ISP networks
going forward. As major ISP's are deploying Carrier Grade NAT, every
IPv4 only service makes their CGN and/or NAT64 boxes ever bigger and
more expensive to
Setting it manually works fine, and I see 9k frames on the wire for IPv6.
Its a I350-T2 Intel server NIC, fairly modern.
Currently I've added a /etc/network/if-up.d/ script to set it every time
the interface comes up (legacy protocols in my networks? never!)
--
You received this bug
Oh, and for completeness;
root@slurv:~# ip link set dev eth2 mtu 9000
root@slurv:~# echo $?
0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1061304
Title:
Configured ethernet MTU not set with IPv4
Public bug reported:
Setting MTU in the Wired tab of the network manager UI does nothing if IPv4
is set to disabled, eg in IPv6-only environments.
Setting it to 9000 and bringing the interface up its still stuck at 1500, both
global MTU and protocol specific MTU.
Enabling IPv4 with any bogus
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/964710
Title:
indicator-sound-service spontaniously crashed with SIGABRT in
g_assertion_message()
To manage
Note that unloading the apparmor profiles (as a temporary measure of
course) workarounds this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931717
Title:
locale-gen does not work in LXC
** Summary changed:
- icedtea-7-plugins makes browsers cry when running BankID applet
+ icedtea-7-plugin makes browsers cry when running BankID applet
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparmor reports this:
[235069.803869] type=1400 audit(1329758407.826:37): apparmor=DENIED
operation=chmod info=Failed name lookup - deleted entry error=-2
parent=26483 profile=/usr/bin/lxc-start//lxc_container
name=/usr/lib/locale/locale-archive.cYcWvi pid=26503 comm=localedef
requested_mask=w
33 matches
Mail list logo
