[Bug 1379779] Re: neutron-openvswitch-agent fails to apply iptables rules - Set IPv4cf55331e-3b18-488d-8 doesn't exist.
** Branch linked: lp:ubuntu/utopic-proposed/neutron -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1379779 Title: neutron-openvswitch-agent fails to apply iptables rules - Set IPv4cf55331e-3b18-488d-8 doesn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1379779/+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 1379779] Re: neutron-openvswitch-agent fails to apply iptables rules - Set IPv4cf55331e-3b18-488d-8 doesn't exist.
This bug was fixed in the package neutron - 1:2014.2~rc2-0ubuntu1 --- neutron (1:2014.2~rc2-0ubuntu1) utopic; urgency=medium * New upstream release candidate: - d/p/*: Refresh. * Fixup optimized iptables management by l2 daemons (LP: #1379779): - d/neutron-common.install: Install ipset-firewall.filters to support use of ipset to optimize firewall rulebase management. - d/control: Add ipset to Depends of neutron-common. * d/watch: Only match versions starting with digits. -- James Page james.p...@ubuntu.com Fri, 10 Oct 2014 15:13:44 +0100 ** Changed in: neutron (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to neutron in Ubuntu. https://bugs.launchpad.net/bugs/1379779 Title: neutron-openvswitch-agent fails to apply iptables rules - Set IPv4cf55331e-3b18-488d-8 doesn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1379779/+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 1380036] [NEW] kubuntu plasma next ( 14.10) - kf5 apps use gtk2 theme
Public bug reported: I am using the kubuntu next repository on kubuntu 14.10 - with the latest release of plasma 5.1. I have a bizarre issue that the kf5 applications like system-settings seem to be using the gtk2 theme set using the kde-gtk-config tool. Kde4 applications and qt4 applications correctly use the application style set. E,g, i set application style to breeze, gtk2 theme to qtcurve and gtk3 to adwaita - and i can see that systemsettings5 is using qtcurve. while konversation (kde 4) and cadence (qt4) is using breeze (qt4config shows that theme is set to desktop default). When i change the gtk2 theme to say oxygen-gtk and restart system- settings it changes themes. Changing the theme in kde application style doesn't have any effect on system settings - also i that kde 4 applications don't change themes on the fly - they need to be restarted which is different behaviour to what i had seen in the early betas of plasma next Please let me know how i can debug this issue further? Output of lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 output of apt-cache policy plasma-workspace plasma-workspace: Installed: 4:5.1.0-0ubuntu1~ubuntu14.10~ppa4 Candidate: 4:5.1.0-0ubuntu1~ubuntu14.10~ppa4 Version table: *** 4:5.1.0-0ubuntu1~ubuntu14.10~ppa4 0 500 http://ppa.launchpad.net/kubuntu-ppa/next/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: bug-theme.png https://bugs.launchpad.net/bugs/1380036/+attachment/4231366/+files/bug-theme.png ** Package changed: open-vm-tools (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to open-vm-tools in Ubuntu. https://bugs.launchpad.net/bugs/1380036 Title: kubuntu plasma next ( 14.10) - kf5 apps use gtk2 theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1380036/+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 1380038] [NEW] SSL problems: doesn't check certificate chain and hostname when ssl connecting
*** This bug is a security vulnerability *** Public security bug reported: Recently, we are trying to find SSL security problems by static analysis. For example, as we all know, Hostname verification is an important step when verifying X509 certificates, however, people tend to miss the step or to misunderstand the APIs when using SSL/TLS, which might cause severe man in the middle attack and break the entire TLS mechanism. And static analysis is a way of finding whether the APIs are called correctly. Now, we find some SSL problems in pacemaker, the following is details: 1. file : /pacemaker-1.1.6/lib/common/remote.c problem : Certificate chain verification is missing 2. file : /pacemaker-1.1.6/lib/common/remote.c problem : Hostname verification is missing More specifically , we can take hostname check for example, the function verify_certificate() can only guarantee the validity of the certificate but cannot guarantee that the host you are trying to connect is the one you intend to visit, which may lead to man-in-the-middle attack or other security issues. And other APIs have similar problems. PS: for more information, you can see the paper: http://people.stfx.ca/x2011/x2011ucj/SSL/p38-georgiev.pdf and more details you can contact with us, my email : rainkin1...@gmail.com Thanks. ** Affects: pacemaker (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1380038 Title: SSL problems: doesn't check certificate chain and hostname when ssl connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1380038/+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 1380080] [NEW] Cannot make directory '/var/run/screen': Permission denied (convert init to upstart)
Public bug reported: Same problem as bug #574773 but happening on Ubuntu 14.04 Trusty Tahr. It looks like the upstart script was removed and there is an /etc/init.d script that just doesn't work properly. It can be fixed by copying the upstart script from 12.04. ** Affects: screen (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1380080 Title: Cannot make directory '/var/run/screen': Permission denied (convert init to upstart) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380080/+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 1380084] [NEW] SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Public bug reported: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1380099] Re: smbd crashed with SIGABRT in dump_core()
*** This bug is a duplicate of bug 1295518 *** https://bugs.launchpad.net/bugs/1295518 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1295518, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1380099/+attachment/4231618/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1380099/+attachment/4231620/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1380099/+attachment/4231621/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1380099/+attachment/4231622/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1380099/+attachment/4231623/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1380099/+attachment/4231626/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1380099/+attachment/4231627/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1295518 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1380099 Title: smbd crashed with SIGABRT in dump_core() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1380099/+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 1379761] Re: Asset compression does not happen unless debug mode is enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: horizon (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1379761 Title: Asset compression does not happen unless debug mode is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1379761/+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 1380150] [NEW] novaclient: security groups, should fail when creating security groups with duplicate name
Public bug reported: When creating a security group using the novaclient.security_groups create API, there is not check which avoids creating security group if one already exist. This later on poses a problem when trying to delete, find the security group, which results in a NoUniqueMatch exception as below. It would be better if the API returned an error when creating a security group with the same name. == ERROR: test_network_scenarios (__main__.NetworkScenarioTest) -- Traceback (most recent call last): File /home/xyz/code/install_oct10/pns/vmtp.py, line 359, in tearDown self.comp.security_group_delete() File /home/xyz/code/install_oct10/pns/compute.py, line 183, in security_group_delete group = self.novaclient.security_groups.find(name=self.config.security_group_name) File /home/xyz/env/env1/lib/python2.7/site-packages/novaclient/base.py, line 140, in find raise exceptions.NoUniqueMatch NoUniqueMatch ** Affects: python-novaclient (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-novaclient in Ubuntu. https://bugs.launchpad.net/bugs/1380150 Title: novaclient: security groups, should fail when creating security groups with duplicate name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-novaclient/+bug/1380150/+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 1380164] Re: screen crashed when trying to split via terminal control sequence
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1380164 Title: screen crashed when trying to split via terminal control sequence To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380164/+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 1380164] Re: screen crashed when trying to split via terminal control sequence
This is likely fixed in 4.2.1-2 in Utopic. At least I can't reproduce it anymore on Debian Testing with 4.2.1-2. It's likely that this had been fixed upstream with either 4.2.0 or 4.2.1. ** Changed in: screen (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to screen in Ubuntu. https://bugs.launchpad.net/bugs/1380164 Title: screen crashed when trying to split via terminal control sequence To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1380164/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
** Attachment added: ssh_config.local https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+attachment/4231875/+files/ssh_config.local -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
** Attachment added: sshd_config.remote https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+attachment/4231905/+files/sshd_config.remote -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
Happens with all SSH commands such as scp and sftp. This also means that I can't use the file explorer called files to connect to remote file systems. sftp will not work in the files browser because there is no way to tell files to use SSH_AUTH_SOCK=0 So I can not browse remote files in the file explorer as if they were local. I'm talking about the GUI file explorer. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1336555] Re: ovs-vswitchd segfault every 2 days
After updating kernel in ubuntu 14.04 I found this again. But this time with kernel panic. ct 12 00:56:30 red-compute kernel: [ 2139.850867] ovs-vswitchd[19280]: segfault at 0 ip 00459340 sp 7fff2d88c3e8 error 4 in ovs-vswitchd[40+133000] Oct 12 00:56:31 red-compute ovs-vswitchd: ovs|00010|daemon(monitor)|ERR|7 crashes: pid 19280 died, killed (Segmentation fault), core dumped, restarting Oct 12 00:57:01 red-compute CRON[19736]: (root) CMD (if [ -x /usr/share/mdadm/checkarray ] [ $(date +%d) -le 7 ]; then /usr/share/mdadm/checkarray --cron --all --idle --quiet; fi) Oct 12 00:58:28 red-compute ovsdb-client: ovs|1|fatal_signal|WARN|terminating with signal 15 (Terminated) Oct 12 00:58:34 red-compute kernel: [ 2264.419340] init: neutron-plugin-openvswitch-agent main process (14411) killed by KILL signal Oct 12 00:58:56 red-compute kernel: [ 2286.159789] INFO: task jbd2/rbd1-8:10184 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.159802] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.159807] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.159812] jbd2/rbd1-8 D 88032fc54480 0 10184 2 0x Oct 12 00:58:56 red-compute kernel: [ 2286.159822] 88029baadbc8 0046 8802d1ac8000 88029baadfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.159832] 00014480 00014480 8802d1ac8000 88032fc54d18 Oct 12 00:58:56 red-compute kernel: [ 2286.159840] 88032ffb1020 0002 811ee820 88029baadc40 Oct 12 00:58:56 red-compute kernel: [ 2286.159847] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.159864] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159875] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.159884] [811ee82e] sleep_on_buffer+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.159892] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159899] [811ee820] ? generic_block_bmap+0x50/0x50 Oct 12 00:58:56 red-compute kernel: [ 2286.159907] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.159916] [810ab010] ? autoremove_wake_function+0x40/0x40 Oct 12 00:58:56 red-compute kernel: [ 2286.159924] [811efb5a] __wait_on_buffer+0x2a/0x30 Oct 12 00:58:56 red-compute kernel: [ 2286.159933] [812888f0] jbd2_journal_commit_transaction+0xee0/0x1a70 Oct 12 00:58:56 red-compute kernel: [ 2286.159943] [810754ff] ? try_to_del_timer_sync+0x4f/0x70 Oct 12 00:58:56 red-compute kernel: [ 2286.159951] [8128d4ad] kjournald2+0xbd/0x250 Oct 12 00:58:56 red-compute kernel: [ 2286.159959] [810aafd0] ? prepare_to_wait_event+0x100/0x100 Oct 12 00:58:56 red-compute kernel: [ 2286.159967] [8128d3f0] ? commit_timeout+0x10/0x10 Oct 12 00:58:56 red-compute kernel: [ 2286.159974] [8108b492] kthread+0xd2/0xf0 Oct 12 00:58:56 red-compute kernel: [ 2286.159981] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.159988] [8172f77c] ret_from_fork+0x7c/0xb0 Oct 12 00:58:56 red-compute kernel: [ 2286.159995] [8108b3c0] ? kthread_create_on_node+0x1c0/0x1c0 Oct 12 00:58:56 red-compute kernel: [ 2286.160016] INFO: task init:10493 blocked for more than 120 seconds. Oct 12 00:58:56 red-compute kernel: [ 2286.160022] Tainted: PW OX 3.13.0-37-generic #64-Ubuntu Oct 12 00:58:56 red-compute kernel: [ 2286.160025] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Oct 12 00:58:56 red-compute kernel: [ 2286.160028] initD 88032fc94480 0 10493 10443 0x Oct 12 00:58:56 red-compute kernel: [ 2286.160036] 8802eae2da28 0082 8802b37a3000 8802eae2dfd8 Oct 12 00:58:56 red-compute kernel: [ 2286.160043] 00014480 00014480 8802b37a3000 88032fc94d18 Oct 12 00:58:56 red-compute kernel: [ 2286.160050] 88032ffb7908 0002 812851c0 8802eae2daa0 Oct 12 00:58:56 red-compute kernel: [ 2286.160057] Call Trace: Oct 12 00:58:56 red-compute kernel: [ 2286.160066] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160074] [8172344d] io_schedule+0x9d/0x140 Oct 12 00:58:56 red-compute kernel: [ 2286.160081] [812851ce] sleep_on_shadow_bh+0xe/0x20 Oct 12 00:58:56 red-compute kernel: [ 2286.160088] [817238d2] __wait_on_bit+0x62/0x90 Oct 12 00:58:56 red-compute kernel: [ 2286.160095] [812851c0] ? start_this_handle+0x590/0x590 Oct 12 00:58:56 red-compute kernel: [ 2286.160103] [81723977] out_of_line_wait_on_bit+0x77/0x90 Oct 12 00:58:56 red-compute kernel: [
[Bug 1336555] Re: ovs-vswitchd segfault every 2 days
ovs-vsctl (Open vSwitch) 2.0.2 Compiled Aug 15 2014 14:31:02 I did: apport-collect 1336555 Package openvswitch not installed and no hook available, ignoring But no luck. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1336555 Title: ovs-vswitchd segfault every 2 days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1336555/+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 1320074] Re: maas-import-pxe fails to catch comms errors when downloading UEFI shim and TBs instead
giving me a syntax error near unexpected token '('
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1320074
Title:
maas-import-pxe fails to catch comms errors when downloading UEFI shim
and TBs instead
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1320074/+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] Re: php5-fpm logrotate errors after package switched to upstart
Having this issue here too. So, been reading through your comments but what now? Will a bugfix come out soon? If not, what's the recommended, temporary, workaround?? -- 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
