I've had success working around this in Xenial by creating the following
file:
/etc/apt/preferences.d/avoid-broken-uwsgi
```
# 2.0.12-5-ubuntu3.1 is broken for almost all the uwsgi packages,
# until this bug gets fixed:
# https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1717378
Package: uwsgi
Confirmed on 16.04 LTS with:
Linux: 4.4.0-47-generic
Qt: 5.5.1
KDE Frameworks: 5.18.0
Konsole: 15.12.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574535
Title:
Konsole doesn't honour "Initial d
That sounds reasonable from my end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1319595
Title:
upstart script ignores some php-fpm.conf parameters, cannot be
bypassed in preference of SystemV in
Public bug reported:
Trusty 14.04 LTS x86_64 Server
The upstart script invokes php5-fpm with --nodaemonize.
This causes several options from the config file to be ignored,
including log file locations, pid file, and others. It also means that
logging is done to /var/log/upstart/ and is no longe
+1. In a very related vein, the init script exits with status 4 when it
tries to start an already-running haproxy. Both the stop and start
behaviors are non-standard LSB: http://linux-
ha.org/wiki/LSB_Resource_Agents
--
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
In recent versions of MySQL server, including the version currently
packaged in 12.04, using 'type=EngineType' in a table definition is no
longer valid.
'Type' should be replaced with 'Engine' going forward.
The db-config install script packaged with pdns-backend-mysql (by
d
Public bug reported:
Binary package hint: bash
I would simply like to suggest a much larger history length by default.
500 commands is quite small and I know of no technical reason a much
larger number would be unreasonable.
I like to use 1 myself. It can be VERY useful to recover a
complic
I have learned that while this can be fixed using the above patch
(actually, I had to increase my timeout to over nine minutes!) - the
true cause of the issue is a bug in kvm-84.
kvm-85 will start even large VMs very quickly, obviating the need to
increase the startup timeout in the first place.
Also experiencing this. 0.6.1-0ubuntu5
Was fine until writing +200GB to the qcow image, now cannot start the
machine after destroying it.
--
libvirtError: internal error unable to start guest
https://bugs.launchpad.net/bugs/344400
You received this bug notification because you are a member of U
