Vagrant does not work: Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-libsodium.gemspec]: stack level too deep

Bug #1804626 reported by Ville Ranki
46
This bug affects 11 people
Affects Status Importance Assigned to Milestone
vagrant (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Steps to reproduce:

1. apt install vagrant (on 18.04 lts)
2. vagrant box list

Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl-libsodium.gemspec]: stack level too deep

vagrant up also causes the same error and nothing happens.

Looks like the ubuntu package is broken according to is discussion on the issue on github: https://github.com/hashicorp/vagrant/issues/9788

This is a showstopper bug as it completely prevents the use of vagrant.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vagrant 2.0.2+dfsg-2ubuntu8
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 22 11:38:01 2018
InstallationDate: Installed on 2018-05-02 (204 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: vagrant
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ville Ranki (ville-ranki) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in vagrant (Ubuntu):
status: New → Confirmed
Revision history for this message
Marat BN (maratbn) wrote :

Hmmm, this happened to me after I tried to manually install Vagrant from source on an Ubuntu 18.04 system, and then tried to go back to the official Ubuntu Vagrant.

So I ran the following command to determine if I had any extra manually-installed Ruby gems on my system that were not compatible with the default Ubuntu Vagrant installation:

comm -23 <(find / -xdev -type f|sort) <(sort /var/lib/dpkg/info/*.list) | grep Ruby | sort

Discovered that I had a whole bunch of extra Ruby gems under '/var/lib/gems/2.5.0/' that weren't owned by any package. Moved the whole directory out from under '/var/lib/gems/', and then was able to run 'vagrant' without any errors.

Revision history for this message
Marat BN (maratbn) wrote :

Oh, sorry, meant the command to be:

comm -23 <(find / -xdev -type f|sort) <(sort /var/lib/dpkg/info/*.list) | grep gem | sort

grep gem not 'Ruby'

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.