Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep
I'm sorry. It seems I did have additional gems installed. After removing all gems, and `ruby*` apt packages (and reinstalling vagrant), vagrant works again! When I then did `sudo gem install overcommit` which installed childprocess-0.9.0 as a dependency, vagrant broke again. Feel free to close this issue. Sorry to have bothered you, Nicholas P.S. It seems to be an interaction either with having multiple version of childprocess or maybe just childprocess > 0.5.9. On Wed, Apr 4, 2018 at 2:23 PM Antonio Terceiro <terce...@debian.org> wrote: > Control: tag -1 + moreinfo unreproducible > > On Tue, Apr 03, 2018 at 04:17:51PM -0500, Nicholas Capo wrote: > > Package: vagrant > > Version: 2.0.2+dfsg-3 > > Severity: normal > > > > Dear Maintainer, > > > > When running any `vagrant` command the following is error appears and the > > command seems to never complete. > > > > ``` > > $ vagrant status > > Invalid gemspec in > [/usr/share/rubygems-integration/all/specifications/rbnacl- > > libsodium.gemspec]: stack level too deep > > ``` > > > > At one point I typed Ctrl+C quickly and got this (possibly related) stack > > trace: > > > > ``` > > $ vagrant status > > Invalid gemspec in > [/usr/share/rubygems-integration/all/specifications/rbnacl- > > libsodium.gemspec]: stack level too deep > > [...] > > ``` > > I can't reproduce this on my system, nor in a clean system with only > vagrant installed. > > > I have tried removing `ruby-rbnacl` (which removes `vagrant`) and > reinstalling, > > but the issue persists. > > ``` > > $ sudo apt autoremove --purge ruby-rbnacl > [...] > > $ sudo apt install vagrant > > $ vagrant status > > Invalid gemspec in > [/usr/share/rubygems-integration/all/specifications/rbnacl- > > libsodium.gemspec]: stack level too deep > > ^C > > ``` > > > > I do not beleive I have any gems installed (other than what comes from > apt), > > but here is the list just in case: > > > > ``` > > sudo gem list > [...] > > ``` > > I need more than that. please share the output of: > > find /var/lib/gems > gem list rbnacl-libsodium > ruby -e 'gem "rbnacl-libsodium"' > > also, do you have vagrant plugins installed from outside of Debian? >
Bug#894754: vagrant: Invalid gemspec in rbnacl-libsodium stack level too deep
Package: vagrant Version: 2.0.2+dfsg-3 Severity: normal Dear Maintainer, When running any `vagrant` command the following is error appears and the command seems to never complete. ``` $ vagrant status Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl- libsodium.gemspec]: stack level too deep ``` At one point I typed Ctrl+C quickly and got this (possibly related) stack trace: ``` $ vagrant status Invalid gemspec in [/usr/share/rubygems-integration/all/specifications/rbnacl- libsodium.gemspec]: stack level too deep ^CTraceback (most recent call last): 998: from /usr/bin/vagrant:23:in `' 997: from /usr/lib/ruby/2.5.0/rubygems.rb:309:in `activate_bin_path' 996: from /usr/lib/ruby/2.5.0/rubygems.rb:309:in `synchronize' 995: from /usr/lib/ruby/2.5.0/rubygems.rb:311:in `block in activate_bin_path' 994: from /usr/lib/ruby/2.5.0/rubygems.rb:239:in `finish_resolve' 993: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:68:in `require' 992: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1084:in `find_active_stub_by_path' 991: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:850:in `stubs' 990: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:782:in `installed_stubs' 989: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `map_stubs' 988: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `flat_map' 987: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `each' 986: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:793:in `block in map_stubs' 985: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `gemspec_stubs_in' 984: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `select' 983: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:208:in `valid?' 982: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:139:in `data' 981: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:197:in `to_spec' 980: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `load' 979: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `eval' [ elided many copies of the same stack] 34: from /usr/share/rubygems-integration/all/specifications/rbnacl- libsodium.gemspec:2:in `load' 33: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:68:in `require' 32: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1084:in `find_active_stub_by_path' 31: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:850:in `stubs' 30: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:782:in `installed_stubs' 29: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `map_stubs' 28: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `flat_map' 27: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `each' 26: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:793:in `block in map_stubs' 25: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `gemspec_stubs_in' 24: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `select' 23: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:208:in `valid?' 22: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:139:in `data' 21: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:197:in `to_spec' 20: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `load' 19: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1194:in `eval' 18: from /usr/share/rubygems-integration/all/specifications/rbnacl- libsodium.gemspec:2:in `load' 17: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:68:in `require' 16: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1084:in `find_active_stub_by_path' 15: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:850:in `stubs' 14: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:782:in `installed_stubs' 13: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `map_stubs' 12: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `flat_map' 11: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:790:in `each' 10: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:793:in `block in map_stubs' 9: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `gemspec_stubs_in' 8: from /usr/lib/ruby/2.5.0/rubygems/specification.rb:768:in `select' 7: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:208:in `valid?' 6: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:118:in `data' 5: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:118:in `open' 4: from /usr/lib/ruby/2.5.0/rubygems/stub_specification.rb:129:in `block in data' 3: from
Bug#833719: Workaround
I was also able to fix this issue by upgrading libnss3: Package: firefox (amd64) Version: 48.0-2 $ sudo apt install libnss3=2:3.26-1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libnss3-1d The following packages will be upgraded: libnss3 1 upgraded, 0 newly installed, 1 to remove and 1 not upgraded. Need to get 1,158 kB of archives. After this operation, 46.1 kB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://ftp.us.debian.org/debian unstable/main amd64 libnss3 amd64 2:3.26-1 [1,158 kB] Fetched 1,158 kB in 0s (2,444 kB/s) Retrieving bug reports... Done Parsing Found/Fixed information... Done Reading changelogs... Done (Reading database ... 292437 files and directories currently installed.) Removing libnss3-1d:amd64 (2:3.25-1) ... (Reading database ... 292430 files and directories currently installed.) Preparing to unpack .../libnss3_2%3a3.26-1_amd64.deb ... Unpacking libnss3:amd64 (2:3.26-1) over (2:3.25-1) ... Setting up libnss3:amd64 (2:3.26-1) ... Processing triggers for libc-bin (2.23-5) ...
Bug#680462: liferea: clobbers feedlist.opml instead of following symbolic link
Package: liferea Version: 1.8.6-1 Severity: normal I am keeping my config files under version control, and (for various unrelated reasons) elected to move the feedlist for liferea and then create a symlink to its new location. Upon running liferea the symlinks for feedlist.opml and feedlist.opml.backup have been removed and replaced with a file containing the data at the linked location. *** Steps to reproduce: ### # clean up rm -rf ~/.liferea_1.8/ rm -rf ~/.liferea_moved # create default config liferea # move the config files ls -l ./.liferea_1.8/ mv ~/.liferea_1.8/ ~/.liferea_moved mkdir ~/.liferea_1.8 # link to the config files in the new location cd ~/.liferea_moved/ for file in *; do ln -s ~/.liferea_moved/$file ~/.liferea_1.8/$file done # test ls -l ~/.liferea_1.8/ liferea ls -l ~/.liferea_1.8/ ### *** Output of last three commands ### ls -l /home/lifereatest/.liferea_1.8/ total 0 lrwxrwxrwx 1 lifereatest lifereatest 39 Jul 5 20:22 accels - /home/lifereatest/.liferea_moved/accels lrwxrwxrwx 1 lifereatest lifereatest 38 Jul 5 20:22 cache - /home/lifereatest/.liferea_moved/cache lrwxrwxrwx 1 lifereatest lifereatest 44 Jul 5 20:22 cookies.txt - /home/lifereatest/.liferea_moved/cookies.txt lrwxrwxrwx 1 lifereatest lifereatest 46 Jul 5 20:22 feedlist.opml - /home/lifereatest/.liferea_moved/feedlist.opml lrwxrwxrwx 1 lifereatest lifereatest 53 Jul 5 20:22 feedlist.opml.backup - /home/lifereatest/.liferea_moved/feedlist.opml.backup lrwxrwxrwx 1 lifereatest lifereatest 43 Jul 5 20:22 liferea.db - /home/lifereatest/.liferea_moved/liferea.db liferea (liferea:5187): libnotify-WARNING **: Failed to connect to proxy ls -l /home/lifereatest/.liferea_1.8/ total 16 lrwxrwxrwx 1 lifereatest lifereatest 39 Jul 5 20:22 accels - /home/lifereatest/.liferea_moved/accels lrwxrwxrwx 1 lifereatest lifereatest 38 Jul 5 20:22 cache - /home/lifereatest/.liferea_moved/cache lrwxrwxrwx 1 lifereatest lifereatest 44 Jul 5 20:22 cookies.txt - /home/lifereatest/.liferea_moved/cookies.txt -rw--- 1 lifereatest lifereatest 4854 Jul 5 20:22 feedlist.opml -rw--- 1 lifereatest lifereatest 4852 Jul 5 20:22 feedlist.opml.backup lrwxrwxrwx 1 lifereatest lifereatest 43 Jul 5 20:22 liferea.db - /home/lifereatest/.liferea_moved/liferea.db As you can see the links (for feedlist.opml and feedlist.opml.backup) have been removed and replaced with normal files. This does not allow me to manage my config files as I would like. As far as I am concerned symlinks should be transparent to liferea. Thanks. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liferea depends on: ii gconf-service 3.2.5-1 ii gconf2 3.2.5-1 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-33 ii libcairo2 1.12.2-1 ii libgconf-2-43.2.5-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libice6 2:1.0.8-2 ii libjson-glib-1.0-0 0.14.2-1 ii libnotify4 0.7.5-1 ii libpango1.0-0 1.30.0-1 ii libsm6 2:1.2.1-2 ii libsoup2.4-12.38.1-2 ii libsqlite3-03.7.13-1 ii libunique-1.0-0 1.1.6-4 ii libwebkitgtk-1.0-0 1.8.1-2 ii libxml2 2.8.0+dfsg1-4 ii libxslt1.1 1.1.26-12+rebuild1 ii liferea-data1.8.6-1 Versions of packages liferea recommends: ii curl 7.26.0-1 ii dbus 1.6.0-1 ii dbus-x11 1.6.0-1 ii wget 1.13.4-3 Versions of packages liferea suggests: ii network-manager 0.9.4.0-5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675763: gnome-settings-daemon: gnome-setting-daemon segfaults in libmouse.so
I made further tests on my EeePC 1000HE, and finally I can say that the problem is in the disable touchpad while typing option. If enabled, gnome crashes, otherwise everything is working fine! I can confirm that selecting disable touchpad while typing results in a g-s-d segfault. Without it g-s-d works as normal. This is in fully updated Testing. gnome-settings-daemon 3.4.2-3 gnome-control-center 1:3.4.2-2 Nicholas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
