When I run bundle exec rspec spec/ I get the following messages in the console:
Could not open library 'libgtkmm-2.4': libgtkmm-2.4: cannot open shared object file: No such file or directory.
Could not open library 'libgtkmm-2.4.so': libgtkmm-2.4.so: cannot open shared object file: No such file or directory.
Could not open library 'libgtkmm-2.4.so.1': libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory.
Could not open library 'libgtkmm-3.0': libgtkmm-3.0: cannot open shared object file: No such file or directory.
Could not open library 'libgtkmm-3.0.so': libgtkmm-3.0.so: cannot open shared object file: No such file or directory.
Could not open library 'libgtkmm-3.0.so.1': libgtkmm-3.0.so.1: cannot open shared object file: No such file or directory
But, all of the tests pass and my app works just fine. Can anyone fill me in on what may have happened? Should I just scrap this box and clone my repo into a fresh one? I'm using Ruby 2.0.0p247 and Rails 4.0.2 in a Nitrous.io box. Thanks.
Even though unrelated (thank google for finding this), I have been trying to install Nitrogen for Ubuntu today. I get the same error. Seems like a specific GTK library has gone missing recently from either your system or your distro's repository (if you're even using Linux).
If you're using a Linux system, install the libgtkmm packages and if you're lucky enough, your missing library will be in one of those.
Use in Ubuntu this to install all of them:
sudo apt-get install libgtkmm*
Hope this helps.
Related
I would like to create a macOS app using py2app. My application (testapp) has a few dependencies
(paramiko,scp,PyYAML,PyQt5). To do so:
I installed python3 using brew (located in /usr/local/Cellar).
I installed the aforementioned dependencies in this python
I ran python3 setup.py py2app --packages paramiko,yaml,scp
Everything runs apparently fine. I have a testapp.app directory created in dist. However, when I run the python located in the bundle (./dist/testapp.app/Contents/MacOS/python) I run into troubles. Indeed, I can import the aforementioned external packages but when I inspect their path, the result gives me the local installation and not the one of the bundle.
For instance paramiko.__path__ gives me: /usr/local/Cellar/python3/3.6.3/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/paramiko
Looking deeper into the bundle, I could not find the file site-packages.zip which should be created by py2app.
As such my bundle is absolutely not self consistent and can not be distributed on other machines. Would you have any idea about what is wrong with my setup ?
EDIT: I forgot to mention that I started to inspect the embedded python because running the embedded app failed.
After last attacks, I upgraded MODX to 2.6.5 version. And now there is a problem with uploading files via Modx File Manager. There are no errors during uploading. Message in File Manager after all is "File successfully uploaded" but file isn't uploaded.
In logs there are several errors but nothing about file transfer. A lot of error in /core/xpdo/xpdo.class.php:
Could not load class: fastFieldParser from fastfieldparser.
Problem getting service parser, instance of class fastFieldParser, from path /core/components/fastfield/model/fastfield/
Where can i find solution if there are no errors about file transfer problem?
I'd recommend re-running the upgrade. I've found that Susan's install script works very well for quick reinstallations. If that doesn't work I'd recommend reviewing the server's PHP logs to see if there's anything useful in there.
Install script: MODX Install Script
I need to install ruby 2.0.0-p645 and I use rbenv. I tried downloading it by running
rbenv install 2.0.0-p645
But the internet in my college keeps dropping every few minutes, so the transfer was always closing with some 11MB remaining.
To counter that, I saw the url from where rbenv was downloading, and used wget to download the source file that rbenv was downloading. (using wget -c for resuming every time the connection closed).
Now I have the file, is there a way to install that ruby version now?
The file's link on cloudfront that I have on my machine.
Yes. Put the downloaded file into ~/.rbenv/cache. You might need to create the directory first. Then run your rbenv install command again. Here is the link to the documentation for this: https://github.com/rbenv/ruby-build#package-download-caching
To summarize, for future reference:
Download the file using wget
Create a cache folder in ~/.rbenv/ if it doesn't exist already.
Rename the downloaded file to ruby-x.y.z-pabc.tar.gz. Extract it and move it to ~/.rbenv/cache/
Run rbenv install x.y.z-pabc
For me, the following steps work.
1 Download the file using `wget/curl or any other way`
2. Create a `cache` folder in `~/.rbenv/` if it doesn't exist already.
3. Move the downloaded file to `~/.rbenv/cache/`
4. Run `rbenv install x.y.z` (ex. rbenv install 2.7.1`)
The difference from the above answer was,
- do not need to change file name
- do not need to extract
- if file rename to something random (ex. x.y.z-pabc) it show ruby-build: definition not found: x.y.z-pabc
Hope this can help someone.
I'm currently evaluating RubyMine 7.0.4 on Mac OS X 10.8.5, and I'm trying to get my Ruby on Rails project up and running in the editor but after I try to bundle, I get "Error Copying Gems". Locally I use rbenv but this project uses Vagrant with Ruby 2.1.
I've gone into RubyMine Preferences -> Languages and Frameworks -> Ruby SDK and Gems and set up a "Remote Interpreter" which looks like it is correctly pulling in my Vagrant / SSH information.
After I click OK, it looks like it correctly pulls down the gems, and copies them to the vendor/bundle folder, but then the IDE pops up an error message saying :
"Error Copying Gems - Unknown message with code 'Could not determine the type of file sftp://127.0.0.0.1:2222/......'"
or sometimes I'll get a more detailed error:
"Error Copying Gems - Could not copy sftp://127.0.0.1:2222/usr/bin/sudoedit to file://Users/my.username/Library/Caches/RubyMine70/ruby_stubs/....."
It feels like it is trying to copy them to a local cache folder on my Mac but failing for some reason.
I was facing a similar albeit different problem, maybe you are making the same mistake:
When setting up RubyMine to work with Vagrant, I am assuming you are adding a remote interpreter using the Vagrant dialogue. There it asks you to input the path to ruby executible. This is misleading, what you need is the path to where the gems are installed.
I'm also assuming you using RVM on your VM, as you indicate that you are not using rbenv on your VM.
I solved this by following the symlink steps found http://randycoulman.com/blog/2013/11/05/rubymine-and-vagrant/
Basically, RubyMine isn't trying to save things on your host machine. Its trying to save things to that particular path on your guest OS. I worked around this issue by creating the /Users/user_name/... directory on my guest OS, and then symlinking the directory that has the projects to /vagrant (Again, on the guest OS)
error while loading shared libraries: libopencv_core.so.3.0: cannot open shared object file: No such file or directory.
I am using eclipse c/c++ ide on ubuntu 14.04. Tried everything which I got from google
You are trying to run in Eclipse so the solution provided (The export part) in openCV program compile error "libopencv_core.so.2.4: cannot open shared object file: No such file or directory" in ubuntu 12.04 May not work.
I suppose you have installed open cv following the instructions provided in open cv documentation. If so, you can get rid of this problem by adding the following environment variables to the eclipse runtime.
Name - LD_LIBRARY_PATH
Value - $LD_LIBRARY_PATH:/usr/local/lib
Steps
Click on Run As -> Run Configurations
On the window on the right hand side you see the Environment tab.
Here click on New, you'll see a New Environment Variable pop up.
Here, for Name enter LD_LIBRARY_PATH, for Value enter $LD_LIBRARY_PATH:/usr/local/lib. click ok and Apply
Now run again, you shouldn't see the issue.
I had the same problem too. Upgrading to the latest Eclipse version solved it.