[Bug 1847275] Re: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability
Ran into the same problem. The service never recovers after this error, because the package is not shipped with a systemd unit, but with an old /etc/init.d/stunnel4 script. I ended up uninstalling the Ubuntu version, compling 5.60 (latest at the time) from source and then running it with a makeshift systemd service (available at https://gist.github.com/Jalle19/60532513bbcec2fa630a9d8b576d91e3). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847275 Title: stunnel4: "INTERNAL ERROR: Bad magic at ssl.c, line 117" - DoS vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stunnel4/+bug/1847275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561370] Re: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency)
I can confirm that priv's workaround from post #17 works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/561370 Title: gnome-terminal transparency no longer works reliably (usually opaque, but sometimes shows transparency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/561370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813132] Re: Please backport fix for bug that causes VLC to crash while hovering over certain menus
For me this happens without hovering over any menu, it's enough to start VLC from the command line with "vlc" for it to crash in libmicrodns. Please, backport a working version to Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813132 Title: Please backport fix for bug that causes VLC to crash while hovering over certain menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmicrodns/+bug/1813132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840909] Re: ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 Nitro instances from stopping normally
I ended up uninstalling the package since we don't use hibernation, but I trust the fix works since it's pretty clear what's going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840909 Title: ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 Nitro instances from stopping normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1840909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840909] [NEW] ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 instances from stopping normally
Public bug reported: Recently I've noticed a bunch of related issues with our AWS EC2 instances: * stopping takes forever * terminating takes forever (probably because it tries to stop first) * lots of dangling nodes in our Consul cluster Today I decided to debug what was going on. At first I thought it was something that we do to our AMIs that was the issue, but after starting a vanilla Ubuntu 18.04 official AMI (0cdab515472ca0bac to be exact) I could replicate the issue. What happens is that you get "systemd-logind[816]: Power key pressed" in the journal when you issue a Stop action against your EC2 instance. However, after that nothing happens, until 300 seconds have passed and AWS terminates your instance instead. This means nothing exits cleanly, which explains why Consul nodes are left dangling. At first I thought it was a bug in systemd-logind, until I found /usr/lib/systemd/logind.conf.d/ec2-hibinit-agent-ignore-powerkey.conf, containing: [Login] HandlePowerKey=ignore Removing this file or uncommenting the last line fixes the problem. So in effect this package completely prevents the normal shutdown mechanism from working correctly. I'm currently working on a workaround for this for our AMI building process but an official fix would be nice. Just remove the file, it doesn't even come from upstream, but since it has been in this repository since version 1.0.0 I can't find anything in the git history regarding *why* it was added. ** Affects: ec2-hibinit-agent (Ubuntu) Importance: Undecided Status: Confirmed ** Bug watch added: github.com/aws/ec2-hibernate-linux-agent/issues #10 https://github.com/aws/ec2-hibernate-linux-agent/issues/10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840909 Title: ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 instances from stopping normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1840909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1840909] Re: ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 instances from stopping normally
I spun up some of our older AMIs (built a few months ago) and this package is not installed on them. Either this package should not be included by default (IMO a sane decision since I assume the majority of people don't hibernate their EC2 instances) or the HandlePowerKey override should be removed. Based on https://github.com/aws/ec2-hibernate-linux-agent/issues/10, what actually happens when you hibernate an instance on AWS is "Suspend key pressed", so I don't know why you're messing with the power button in the first place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1840909 Title: ec2-hibinit-agent-ignore-powerkey.conf prevents EC2 instances from stopping normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1840909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733557] Re: Login screen showing Authentication Failure Switch to greeter...
I also started experiencing this issue some time ago. My dad was visiting and used the guest session and after that it started happening, although I'm not 100% sure if it was incidental or not. Rebooting helps for some time, but after a day or two the issue is back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failure Switch to greeter... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
Enable proposed updates from the "Software updater" application, install whatever updates you get, then disable proposed updates again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
FWIW the Xenial kernel from -proposed seems to work just fine too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
Just installed the kernel from proposed, if I don't report back that means it works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1680904] Re: zesty unable to handle kernel NULL pointer dereference
Can someone comment here once a fix for the HWE kernel in Ubuntu 16.04 is available? I'm currently using one of the custom builds from earlier in this thread but I haven't yet been able to confirm whether it fixes the issue or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1680904 Title: zesty unable to handle kernel NULL pointer dereference To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1680904/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373598] Re: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com
This used to happen only on the Vagrant boxes we build but now I've seen it in production as well. It's always the same: W: Failed to fetch http://fi.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://fi.archive.ubuntu.com/ubuntu/dists/trusty-updates/universe/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://fi.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/binary-i386/Packages Hash Sum mismatch W: Failed to fetch http://fi.archive.ubuntu.com/ubuntu/dists/trusty-updates/universe/binary-i386/Packages Hash Sum mismatch Is there anything that can be done to prevent this except changing mirrors completely? Why is it always (and only) affecting trusty- updates? This is getting absolutely ridiculous and makes Ubuntu unusable for servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450066] Re: IPv6 hop limit set to 0
Since upstream has provided a fix for this issue, can someone please update the network-manager package so we don't have to jump through hoops to get IPv6 working? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450066 Title: IPv6 hop limit set to 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1450066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659422] Re: Boot failure after upgrading kernel to 2.6.32-25-generic
I can confirm that this happens with kernel 2.6.32-27-generic-pae on a VMware ESX 4.1 (build 320092). udevadm segfaults right after the kernel has finished loading, and it inevitable leads to failure to mount the root filesystem. Eagerly waiting for a fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659422 Title: Boot failure after upgrading kernel to 2.6.32-25-generic -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 659422] Re: Boot failure after upgrading kernel to 2.6.32-25-generic
Forgot to say that both kernels -27 and -26 work just fine on ESX 4.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/659422 Title: Boot failure after upgrading kernel to 2.6.32-25-generic -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 516909] Re: entire desktop environment locks up in 9.10, i3-530 proc, built-in graphics
I can confirm this bug. The same things happened today on a brand new computer with an ASUS P7H55-M PRO motherboard fitted with an Intel i3-530 CPU, both in the Live CD environment and after a successful installation (had to use the alternate installer). After a bit of googling I found an acceptable workaround though. By chaning the last line in /etc/xdg/compiz/compiz-manager to COMPIZ_NAME=metacity (effectively turning desktop effects off) everything seems to work just fine. I can't tell for sure if this workaround will work in the long run as I just installed the system but it's been working flawlessly for about an hour now compared to the 5-10 seconds it did before. Could someone enlighten me/us as to whether this is a bug in the driver, in Compiz or in the kernel? For the record I'm running a stock Karmic kernel (2.6.31-19-generic). -- entire desktop environment locks up in 9.10, i3-530 proc, built-in graphics https://bugs.launchpad.net/bugs/516909 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 54024] Re: WIN key SUPER_L should be mapped to Applications menu
Currently I have it set up so that when I press the Super key, all windows are minimized. This is ONLY because it is not possible to create a keyboard shortcut like Super+D (which would be the Windows equivalent to minimizing all windows and focusing on the desktop). Thus, I think this is just a wishlist item and not a real papercut bug. What I, and probably many others too, would like is the ability to create keyboard shortcuts that use the Super key as a combo key (like Super+D to minimize all windows, Super+L to lock the screen etc.). Why couldn't we just make all the standard Windows shortcuts the same on Ubuntu? I don't know about you guys, but after using Windows for many many years you grow used to hitting Windows+D to minimize your open windows, and when that same command doesn't work in Ubuntu, you get frustrated. On top of that, the fact that you CANNOT mimic the same behaviour is even more frustrating. [/rant] -- WIN key SUPER_L should be mapped to Applications menu https://bugs.launchpad.net/bugs/54024 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
