[Bug 2063898] [NEW] broken doc symlinks after t64 transition in noble
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 copyright -> ../libssl3/copyright libssl3 doenst exist anymore, it is now libssl3t64 $ apt-cache policy openssl libssl3t64 openssl: Installed: 3.0.13-0ubuntu3 Candidate: 3.0.13-0ubuntu3 Version table: *** 3.0.13-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status libssl3t64: Installed: 3.0.13-0ubuntu3 Candidate: 3.0.13-0ubuntu3 Version table: *** 3.0.13-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063898 Title: broken doc symlinks after t64 transition in noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2063898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059874] Re: on upgrade sshd-socket-generator conversion does not respect administrator intent
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 (per VRF instances or something), having the main service and socket units disabled, but I doubt that happens that much in practice. For me the biggest problem was the socket unit beeing re-enabled when I had it disabled it but still running sshd.service (ie without socket activation) - now you're unexpectidly switched back to using socket activation - something I explicitly opted out of. I could also see this causing problems if you have the socket unit masked (dont see why you would want that however) but the the service is enabled, now you are without sshd. Actually I think the postinst would also fail in that case, as systemctl enable fails enabling masked units. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059874] [NEW] on upgrade sshd-socket-generator conversion does not respect administrator intent
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 disabled. systemctl unmask ssh.service systemctl disable --now ssh.service > /dev/null 2>&1 # sshd-socket-generator is invoked on daemon-reload. systemctl daemon-reload systemctl enable ssh.socket fi fi fi This does not respect existing service and socket unit configuration, it effectively re-enables a disabled ssh.service (and even a masked one), and a manually disabled socket unit. I strongly suspect it does not respect systemd presets either. This is unexpected behaviour. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059874 Title: on upgrade sshd-socket-generator conversion does not respect administrator intent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059872] [NEW] Unable to listen on port 22 if multiple Port= present in sshd configuration
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 it. To show it clearly, here is an example: Port 22 Port 1024 It generates: ListenStream= ListenStream=1024 Now nothing is listening to port 22, hence breaking existing configurations. This was tested on 1:9.6p1-3ubuntu11. The intention seems to be to not generate the drop-in if only port 22 is in use, but it does not account for the case of multiple Port or ListenAddress where one of them is for port 22. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059872 Title: Unable to listen on port 22 if multiple Port= present in sshd configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959475] Re: "machinectl shell" connections immediately terminated
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959475] Re: "machinectl shell" connections immediately terminated
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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created
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: /tmp/systemd-private-%b-* [/usr/lib/tmpfiles.d/tmp.conf:16] Failed to replace specifiers: /tmp/systemd-private-%b-*/tmp [/usr/lib/tmpfiles.d/tmp.conf:17] Failed to replace specifiers: /var/tmp/systemd-private-%b-* [/usr/lib/tmpfiles.d/tmp.conf:18] Failed to replace specifiers: /var/tmp/systemd-private-%b-*/tmp ACL operation on "/var/log/journal" failed: No such file or directory ACL operation on "/var/log/journal" failed: No such file or directory chmod() of /var/log/journal via /proc/self/fd/3 failed: No such file or directory dpkg: error processing package systemd (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits
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.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717714] [NEW] @{pid} variable broken on systems with pid_max more than 6 digits
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:
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
It only covers up to 6 digits.
This Ubuntu 17.04 system has:
kernel.pid_max = 4194303
And is showing
type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open"
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3"
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86"
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
Which should be matched by
@{PROC}/sys/vm/overcommit_memory r,
in /etc/apparmor.d/abstractions/libvirt-qemu
I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
(2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
I am aware this is a non-default configuration, but I think this should
work.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717714
Title:
@{pid} variable broken on systems with pid_max more than 6 digits
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578022] Re: dmidecode fails to output smibios 3.0 info
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: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578022] Re: dmidecode fails to output smibios 3.0 info
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 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=364055211b1956539c6a6268e111e244e1292c8c There's also a couple other SMBIOS 3.0 related fixes that is listed as recomended for 3.0 on http://dmidecode.nongnu.org/ Fix 'No SMBIOS nor DMI entry point found' on SMBIOS3 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=bf7bad24ce141dab5b5acc3ffb98ce5fe4a8e0f9 Use DWORD for Structure table maximum size in SMBIOS3 http://git.savannah.gnu.org/cgit/dmidecode.git/commit/?id=ab02b117511230e46bbef7febbd854b9c832c13c -- 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: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578022] Re: dmidecode fails to output smibios 3.0 info
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 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: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1474080] [NEW] KVM, virtio_rng, rngd starts before /dev/hwrng is up, promptly crashes
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 similar configuration) modular virtio_rng - same as in ubuntu kernel SSD backed which may make this problem more likely to show up (timing wise) Loading virtio_rng from initramfs seems to load it early enough to workaround the problem. root@infra1:~# systemctl status rng-tools ● rng-tools.service - (null) Loaded: loaded (/etc/init.d/rng-tools) Active: failed (Result: exit-code) since ma. 2015-07-13 19:40:31 CEST; 1min 33s ago Docs: man:systemd-sysv-generator(8) Process: 255 ExecStart=/etc/init.d/rng-tools start (code=exited, status=1/FAILURE) juli 13 19:40:31 infra1 systemd[1]: Starting (null)... juli 13 19:40:31 infra1 rng-tools[255]: Starting Hardware RNG entropy gatherer daemon: (Ha...nd) juli 13 19:40:31 infra1 rng-tools[255]: /etc/init.d/rng-tools: Cannot find a hardware RNG ...se. juli 13 19:40:31 infra1 systemd[1]: rng-tools.service: control process exited, code=exited...s=1 juli 13 19:40:31 infra1 systemd[1]: Failed to start (null). juli 13 19:40:31 infra1 systemd[1]: Unit rng-tools.service entered failed state. juli 13 19:40:31 infra1 systemd[1]: rng-tools.service failed. Hint: Some lines were ellipsized, use -l to show in full. ** Affects: rng-tools (Ubuntu) Importance: Undecided Status: New ** Tags: systemd-boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1474080 Title: KVM, virtio_rng, rngd starts before /dev/hwrng is up, promptly crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rng-tools/+bug/1474080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357424] Re: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
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 merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357424] Re: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main)
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 Title: Please merge amavisd-new_2.9.0-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1357424/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1271591] Re: upstart job race prevents gnome-keyring from being ssh agent
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 all work like they should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271591 Title: upstart job race prevents gnome-keyring from being ssh agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 793450] Re: Calendar doesn't show today's date until opened a second time today
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/793450 Title: Calendar doesn't show today's date until opened a second time today To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/793450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242376] Re: reload php5-fpm crashes
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 php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1242376] [NEW] reload php5-fpm crashes
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 telling upstart to instead use SIGUSR2 on reload*, things work as expected. * reload signal SIGUSR2 in upstart php5-fpm.conf Signals handled by php5-fpm seems to be: * SIGINT, SIGTERM: immediate termination * SIGQUIT: graceful stop * SIGUSR1: re-open log file * SIGUSR2: graceful reload of all workers + reload of fpm conf/binary Ubuntu 13.10, amd64 ii php5-fpm 5.5.3+dfsg-1ubuntu2 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- 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 php5-fpm crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1242376] Re: reload php5-fpm crashes
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242376] [NEW] reload php5-fpm crashes
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 telling upstart to instead use SIGUSR2 on reload*, things work as expected. * reload signal SIGUSR2 in upstart php5-fpm.conf Signals handled by php5-fpm seems to be: * SIGINT, SIGTERM: immediate termination * SIGQUIT: graceful stop * SIGUSR1: re-open log file * SIGUSR2: graceful reload of all workers + reload of fpm conf/binary Ubuntu 13.10, amd64 ii php5-fpm 5.5.3+dfsg-1ubuntu2 amd64 server-side, HTML-embedded scripting language (FPM-CGI binary) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1242376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1230917] [NEW] php5-fpm logrotate errors after package switched to upstart
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:
Installed: 5.5.3+dfsg-1ubuntu1
Candidate: 5.5.3+dfsg-1ubuntu1
Version table:
*** 5.5.3+dfsg-1ubuntu1 0
500 http://uk.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
100 /var/lib/dpkg/status
root@ops:~# cat /etc/logrotate.d/php5-fpm
/var/log/php5-fpm.log {
rotate 12
weekly
missingok
notifempty
compress
delaycompress
postrotate
invoke-rc.d php5-fpm reopen-logs /dev/null
endscript
}
root@ops:~# dpkg -S /etc/logrotate.d/php5-fpm
php5-fpm: /etc/logrotate.d/php5-fpm
root@ops:~# invoke-rc.d php5-fpm reopen-logs
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action reopen-logs failed.
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
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/1230917
Title:
php5-fpm logrotate errors after package switched to upstart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1230917] [NEW] php5-fpm logrotate errors after package switched to upstart
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:
Installed: 5.5.3+dfsg-1ubuntu1
Candidate: 5.5.3+dfsg-1ubuntu1
Version table:
*** 5.5.3+dfsg-1ubuntu1 0
500 http://uk.archive.ubuntu.com/ubuntu/ saucy/universe amd64 Packages
100 /var/lib/dpkg/status
root@ops:~# cat /etc/logrotate.d/php5-fpm
/var/log/php5-fpm.log {
rotate 12
weekly
missingok
notifempty
compress
delaycompress
postrotate
invoke-rc.d php5-fpm reopen-logs /dev/null
endscript
}
root@ops:~# dpkg -S /etc/logrotate.d/php5-fpm
php5-fpm: /etc/logrotate.d/php5-fpm
root@ops:~# invoke-rc.d php5-fpm reopen-logs
initctl: invalid command: reopen-logs
Try `initctl --help' for more information.
invoke-rc.d: initscript php5-fpm, action reopen-logs failed.
** Affects: php5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1230917
Title:
php5-fpm logrotate errors after package switched to upstart
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152135] Re: dia-gnome crashed with SIGSEGV in g_main_dispatch()
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 g_main_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/1152135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 241305] Re: security.ubuntu.com not accessible in IPv6 (AAAA record missing in the DNS)
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 operate. Postponing it much longer is not beeing a good netizen, yo ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/241305 Title: security.ubuntu.com not accessible in IPv6 ( record missing in the DNS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/241305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061304] Re: Configured ethernet MTU not set with IPv4 disabled
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 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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1061304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061304] Re: Configured ethernet MTU not set with IPv4 disabled
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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1061304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061304] [NEW] Configured ethernet MTU not set with IPv4 disabled
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 address makes configured MTU work. Tested on Quantal, network manager 0.9.6.0-0ubuntu7 Status in Precise is unknown but its likely a problem there too. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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 disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1061304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 964710] Re: indicator-sound-service spontaniously crashed with SIGABRT in g_assertion_message()
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/964710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931717] Re: locale-gen does not work in LXC container
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 container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/931717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945725] Re: icedtea-7-plugins makes browsers cry when running BankID applet
** 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. https://bugs.launchpad.net/bugs/945725 Title: icedtea-7-plugin makes browsers cry when running BankID applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/945725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 931717] Re: locale-gen does not work in LXC container
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 denied_mask=w fsuid=0 ouid=0 Reading the strace, it does try to fchmod a fd for a file it has unlinked. I wonder how that is supposed to work.. Bug in libc-bin? -- 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 container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/931717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
