[Bug 1717378] Re: uwsgi-plugin-php depends on an unreleased version of libphp-embed
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-* Pin: version 2.0.12-5ubuntu3.1 Pin-Priority: -999 ``` Then apt update and you can install the previous working version as normal. Note: If this bug is not fixed in the next release, this workaround will break until THAT version is also pinned out. I'm assuming it will be fixed before then here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717378 Title: uwsgi-plugin-php depends on an unreleased version of libphp-embed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uwsgi/+bug/1717378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574535] Re: Konsole doesn't honour "Initial directory" setting
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 directory" setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/1574535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319595] Re: upstart script ignores some php-fpm.conf parameters, cannot be bypassed in preference of SystemV init script.
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 init script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1319595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1319595] [NEW] upstart script ignores some php-fpm.conf parameters, cannot be bypassed in preference of SystemV init script.
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 longer configurable. Despite the advantages Upstart brings, these problems may cause some (like me) to choose to abandon Upstart for this particular package. Unfortunately, deleting the Upstart script does not have the intended effect of falling back to the /etc/init.d version by the same name. Due to the following snippet from /etc/init.d/php5-fpm, # Don't run if we are running upstart if init_is_upstart; then exit 1 fi it is impossible to successfully run the init script. The init script is permanently and fundamentally DISABLED by this snippet. A notice or warning output would be more appropriate; or perhaps some additional value set from /etc/default/php5-fpm that would override this behavior. As things stand, I cannot use the init script without making an incompatible edit, which I would then have to fight to maintain against updates for the next few years. Backwards-compatibility, please. This is the server version, after all! ** Affects: php5 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: server trusty -- 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 init script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1319595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1038139] Re: Missing running check on init script
+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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1038139 Title: Missing running check on init script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1038139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1121299] [NEW] pdns-backend-mysql db-config script incompatible with contemporary mysql-server version
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 default, located here: /usr/share/dbconfig-common/data/pdns-backend- mysql/install/mysql) uses the old syntax, and thus the package cannot be installed successfully. Package version: pdns-backend-mysql: Installed: 3.0-1.1ubuntu1 Candidate: 3.0-1.1ubuntu1 Version table: *** 3.0-1.1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: pdns (Ubuntu) Importance: Undecided Status: New ** Tags: db-config pdns powerdns -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1121299 Title: pdns-backend-mysql db-config script incompatible with contemporary mysql-server version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pdns/+bug/1121299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544542] [NEW] Bash $HISTFILESIZE seems far too small by default.
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 complicated command from months in the past. Thanks. ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: wishlist -- Bash $HISTFILESIZE seems far too small by default. https://bugs.launchpad.net/bugs/544542 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 344400] Re: libvirtError: internal error unable to start guest
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. -- libvirtError: internal error unable to start guest https://bugs.launchpad.net/bugs/344400 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 344400] Re: libvirtError: internal error unable to start guest
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
