Re: [Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 install
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 a bit painful as means till this is fix we'll need to go
> through our puppet code and re-write a whole heap to run ruby2.0 -r
> yaml -r rubygems/safe_yaml -S gem instead of the puppet way :(
>
> Thanks
>
> Phil
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1777174
>
> Title:
> 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on
> calling gem2.0 install
>
> Status in ruby2.0 package in Ubuntu:
> Confirmed
>
> Bug description:
> # Summary
> Our Docker builds have just started failing as soon as
> 2.0.0.484-1ubuntu2.10 was released. Whenever we call "gem2.0 install {some
> package}", we get an error saying "uninitialized constant Gem::SafeYAML"
>
> # Required Info
>
> 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
> -> About Ubuntu
> Description: Ubuntu 14.04.3 LTS
> Release: 14.04
>
> 2) The version of the package you are using, via 'apt-cache policy
> pkgname' or by checking in Software Center
> ruby2.0:
> Installed: 2.0.0.484-1ubuntu2.10
> Candidate: 2.0.0.484-1ubuntu2.10
> Version table:
>*** 2.0.0.484-1ubuntu2.10 0
> 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64
> Packages
> 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
>2.0.0.484-1ubuntu2 0
> 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
>
> 3) What you expected to happen
> "gem install rubygems-update" to work
>
> 4) What happened instead
> We see the error below
> ERROR: While executing gem ... (NameError)
> uninitialized constant Gem::SafeYAML
>
> # Recreate:
> To recreate, take the following Dockerfile and try to build the image:
>
> ---
> FROM ubuntu:trusty
> ENV DEBIAN_FRONTEND noninteractive
> RUN apt-get update && apt-get -y install ruby2.0 ruby2.0-dev
> RUN gem2.0 install rubygems-update
> ---
>
> This produces the following output:
>
> ---
> Sending build context to Docker daemon 2.048kB
> Step 1/4 : FROM ubuntu:trusty
>---> 38c759202e30
> Step 2/4 : ENV DEBIAN_FRONTEND noninteractive
>---> Running in fb4736ccbcfe
> Removing intermediate container fb4736ccbcfe
>---> 8d3ab112c945
> Step 3/4 : RUN apt-get update && apt-get -y install ruby2.0 ruby2.0-dev
>---> Running in 17e525082f30
> Ign http://archive.ubuntu.com trusty InRelease
> Get:1 http://archive.ubuntu.com trusty-updates InRelease [65.9 kB]
> Get:2 http://archive.ubuntu.com trusty-security InRelease [65.9 kB]
> Get:3 http://archive.ubuntu.com trusty Release.gpg [933 B]
> Get:4 http://archive.ubuntu.com trusty Release [58.5 kB]
> Get:5 http://archive.ubuntu.com trusty-updates/main Sources [514 kB]
> Get:6 http://archive.ubuntu.com trusty-updates/restricted Sources [6449
> B]
> Get:7 http://archive.ubuntu.com trusty-updates/universe Sources [253 kB]
> Get:8 http://archive.ubuntu.com trusty-updates/main amd64 Packages
> [1348 kB]
> Get:9 http://archive.ubuntu.com trusty-updates/restricted amd64
> Packages [21.4 kB]
> Get:10 http://archive.ubuntu.com trusty-updates/universe amd64 Packages
> [587 kB]
> Get:11 http://archive.ubuntu.com trusty-security/main Sources [199 kB]
> Get:12 http://archive.ubuntu.com trusty-security/restricted Sources
> [5050 B]
> Get:13 http://archive.ubuntu.com trusty-security/universe Sources [88.9
> kB]
> Get:14 http://archive.ubuntu.com trusty-security/main amd64 Packages
> [924 kB]
> Get:15 http://archive.ubuntu.com trusty-security/restricted amd64
> Packages [18.1 kB]
> Get:16 http://archive.ubuntu.com trusty-security/universe amd64
> Packages [292 kB]
> Get:17 http://archive.ubuntu.com trusty/main Sources [1335 kB]
> Get:18 http://archive.ubuntu.com trusty/restricted Sources [5335 B]
> Get:19 http://archive.ubuntu.com trusty/universe Sources [7926 kB]
> Get:20 http://archive.ubuntu.com trusty/main amd64 Packages [1743 kB]
> Get:21 http://archive.ubuntu.com trusty/restricted amd64 Packages [16.0
> kB]
> Get:22 http://archive.ubuntu.com trusty/universe amd64 Packages [7589
> kB]
> Fetched 23.1 MB in 6s ( kB/s)
> Reading package lists...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> The following extra packages will be installed:
> ca-certificates libjs-jquery libruby1.9.1 libruby2.0 libyaml-0-2
> openssl
> ruby ruby1.9.1 rubygems-integration
> Suggested packages:
> javascript-common ri ruby-dev ruby1.9.1-examples ri1.9.1 graphviz
> ruby1.9.1-dev ruby-swit
[Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 install
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 have to make sure any gem commands are run with: ruby2.0 -r yaml -r rubygems/safe_yaml -S gem I've just rechecked building that dockerfile from scratch and it all looks good my end, so maybe go over it a bit more carefully and see if you've missed something from the steps. -- 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 uninitialized constant Gem::SafeYAML on calling gem2.0 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.0/+bug/1777174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 install
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 psych --version 2.0.17 RUN apt-get -y install ruby2.0 libruby2.0 RUN ruby2.0 -r yaml -r rubygems/safe_yaml -S gem2.0 install rubygems-update --- -- 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 uninitialized constant Gem::SafeYAML on calling gem2.0 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.0/+bug/1777174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 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 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 uninitialized constant Gem::SafeYAML on calling gem2.0 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.0/+bug/1777174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 install
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 uninitialized constant Gem::SafeYAML on calling gem2.0 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.0/+bug/1777174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 install
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' +require 'yaml' +require 'rubygems/safe_yaml' version = ">= 0" -- 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 uninitialized constant Gem::SafeYAML on calling gem2.0 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.0/+bug/1777174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777174] Re: 2.0.0.484-1ubuntu2.10 triggers uninitialized constant Gem::SafeYAML on calling gem2.0 install
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 that fails to... ruby2.0 -r safe_yaml -r rubygems/safe_yaml -S gem install psych --version 2.0.17 --backtrace ERROR: While executing gem ... (ArgumentError) wrong number of arguments (4 for 1..3) /usr/lib/ruby/vendor_ruby/safe_yaml/load.rb:136:in `load' /usr/lib/ruby/vendor_ruby/safe_yaml.rb:29:in `safe_load' /usr/lib/ruby/2.0.0/rubygems/safe_yaml.rb:31:in `safe_load' /usr/lib/ruby/2.0.0/rubygems/package.rb:445:in `block (2 levels) in read_checksums' /usr/lib/ruby/2.0.0/rubygems/package.rb:444:in `wrap' /usr/lib/ruby/2.0.0/rubygems/package.rb:444:in `block in read_checksums' -- 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 uninitialized constant Gem::SafeYAML on calling gem2.0 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby2.0/+bug/1777174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1156988] Re: Fails to verify GPG signature of a package
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 Ubuntu. https://bugs.launchpad.net/bugs/1156988 Title: Fails to verify GPG signature of a package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg-sig/+bug/1156988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161771] Re: Corrupted filenames in ISO Ubuntu 12.04.2 Server amd64
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 with truncated names. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161771 Title: Corrupted filenames in ISO Ubuntu 12.04.2 Server amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1161771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011086] Re: X freezes after connecting external monitor
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 freezes after connecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1011086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011086] Re: X freezes after connecting external monitor
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.launchpad.net/bugs/1011086 Title: X freezes after connecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011086] Re: X freezes after connecting external monitor
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.old -- 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 freezes after connecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011086] Re: X freezes after connecting external monitor
** 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.net/bugs/1011086 Title: X freezes after connecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011086] Re: X freezes after connecting external monitor
** 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/bugs/1011086 Title: X freezes after connecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011086] [NEW] X freezes after connecting external monitor
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 attached, and then later me logging in, after which it happens. I observed the default wallpaper being stretched across both monitors, then everthing freezes up. The OS seems to stop responding to all keypresses but I can still log in via SSH. When I log in via SSH, X is running at 100%. I did an strace on the running X process, but it doesn't look very useful. lsb_release -rd output: Description:Ubuntu 12.04 LTS Release:12.04 uname -a Linux tehlappy 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux ** Affects: xorg (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/1011086 Title: X freezes after connecting external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1011086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 428527] Re: Window switcher (alt-tab) causes freeze
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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 428527] Re: Window switcher (alt-tab) causes freeze
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 428527] [NEW] Window switcher (alt-tab) causes freeze
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 Inspiron 1525. I'm guessing this is a compiz-related problem, because turning off visual effects stops the bug. I'll attach an xserver log for your pleasure. Let me know what else you need, I'd love to help. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: 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 Inspiron 1525. + I'm guessing this is a compiz-related problem, because turning off + visual effects stops the bug. + I'll attach an xserver log for your pleasure. Let me know what else you need, I'd love to help. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 178652] Re: No access to non-default sound format profiles
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 difference, but the Gstreamer Pipeline entry for "test" was copied and pasted from a known working profile. I have provided the URL of the upstream bug report. ** Bug watch added: GNOME Bug Tracker #469334 http://bugzilla.gnome.org/show_bug.cgi?id=469334 ** Also affects: sound-juicer via http://bugzilla.gnome.org/show_bug.cgi?id=469334 Importance: Unknown Status: Unknown -- No access to non-default sound format profiles https://bugs.launchpad.net/bugs/178652 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 134918] Re: Misleading error message - cannot install 3d drivers
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 unticked and ticked them all and closed the window, which then reloaded the package lists and allowed me to install nvidia-glx. -- Misleading error message - cannot install 3d drivers https://bugs.launchpad.net/bugs/134918 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86477] Re: pages show as loaded but no content is displayed
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 because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
