Ouch - If you wanted to get clever, you could add your own puppet package
provider that extends the default gem one to use that altered path - it's
probably not as hard as it sounds.
On Thu, Jun 21, 2018 at 3:10 AM Philip Davies <1777...@bugs.launchpad.net>
wrote:
> Hey Nick,
>
> Ah ok, so thats
Hi Philip,
The workaround comes in two parts:
First you rollback to ruby2.0 2.0.0.484-1ubuntu2 and install psych
2.0.17 - this will require build-essential libffi-dev and ruby2.0-dev
(as per dockerfile). At this point you can reinstall the security fix
The second part, which is awful, is you h
Here's a version of andy edwards' Dockerfile which applies my
workaround:
---
FROM ubuntu:trusty
ENV DEBIAN_FRONTEND noninteractive
RUN apt-get update && apt-get -y install ruby2.0=2.0.0.484-1ubuntu2
libruby2.0=2.0.0.484-1ubuntu2 libffi-dev ruby2.0-dev build-essential
RUN ruby2.0 -S gem install
I have a workaround - I downgraded to the previous version:
apt-get install ruby2.0=2.0.0.484-1ubuntu2 libruby2.0=2.0.0.484-1ubuntu2
ruby2.0 -S gem install psych --version 2.0.17
apt-get install ruby2.0
ruby2.0 -S gem -r yaml -r rubygems/safe_yaml install $whatever
--
You received this bug notif
I meant to say I temporarily rolled back, installed psych, then upgraded
back to the secure version again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777174
Title:
2.0.0.484-1ubuntu2.10 triggers
If it's of use to anyone else, I had a broken build due to bundler
choking on this error - I edited my /usr/local/bin/bundle and added:
--- bundle 2018-06-20 16:07:50.742507869 +1200
+++ /usr/local/bin/bundle 2018-06-20 16:05:45.021007716 +1200
@@ -7,6 +7,8 @@
#
require 'rubygems'
Also affected - gem2.0 is totally stuffed with this. It seems like if
your system didn't already have a recent version of psych installed
before the upgrade (maybe) then you can't use it...
I tried using the safe_yaml that seems to be bundled with ruby (or
perhaps it was pre-installed?), but tha
Just a note that the https://launchpadlibrarian.net/190142754/dpkg-
sig_0.13.1+nmu1.diff patch fixed the issue for me - I am also using fpm
to build packages and was hoping to use dpkg-sig.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
A solution that worked for me was to use Win32 Disk Imager to write the
ISO to the USB flash drive. Ubuntu installed with no problems.
When I opened the ISO image in 7-zip, or mounted it using Daemon Tools
and viewed the contents in Windows Explorer, both showed the files in
/pool/main/l/linux wit
I'm not sure anymore that monitors.xml has anything to do with it. Can
anyone out there give me some tips for debugging this further?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011086
Title:
X
I can reproduce the bug by rebooting and then plugging in a second
monitor. I can workaround the bug by removing the .config/monitors.xml
before my X session starts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
So, I renamed .config/monitors.xml and this has sort of fixed it. I'll
attach my old monitors.xml in case that helps anyone.
** Attachment added: "monitors file from $HOME/.config/monitors.xml"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+attachment/3183069/+files/monitors.xml
** Attachment added: "strace from xorg while hogging the cpu"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+attachment/3183015/+files/strace.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "xorg.log showing backtraces"
https://bugs.launchpad.net/bugs/1011086/+attachment/3183004/+files/Xorg-crash-on-external-monitor.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
I've just upgraded to 12.04 from 11.10, and now when I connect my
external monitor, either before or after login, my X session freezes up.
It also seems to stop -- from letting me switch to a
console.
I've attached an Xorg.log that shows me booting up with both monitors
attac
I've just done a dist-upgrade, and the bug hasn't happened since.
--
Window switcher (alt-tab) causes freeze
https://bugs.launchpad.net/bugs/428527
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
Also, top shows compiz using ~100% of the cpu.
--
Window switcher (alt-tab) causes freeze
https://bugs.launchpad.net/bugs/428527
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
ht
Public bug reported:
After installing Karmic alpha 5 (fresh install, not an upgrade), hitting
alt-tab caused X to freeze up. Screen looks fine (no artifacts) but the
mouse stops responding. I'm able to recover by switching to a virtual
terminal and then restarting gdm. This is on an Dell Inspir
I am also experiencing this problem on Hardy. I removed all sound juicer
related settings from ~/.config and ~/.gconf, then created a new custom
profile called "test". It could not be selected from the drop-down menu,
even after closing and re-opening Sound Juicer.
Not sure if it makes a differenc
I can confirm this using Gutsy Tribe 5 and an Nvidia GeForce FX 5600XT.
When ticking the box to enable NVIDIA Accelerated graphics driver I
received the message "The software source for the package nvidia-glx is
not enabled". Looking at Software Sources, I saw that all repositories
was ticked. I un
Just wanted to say I am also occasionally experiencing this problem.
Unfortunately, I cannot reproduce it on a whim at the moment, but I will
post again if and when I can.
--
pages show as loaded but no content is displayed
https://bugs.launchpad.net/bugs/86477
You received this bug notification
21 matches
Mail list logo
