I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
On 06/25/14 10:35, Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
First of all, libproj.so.0 is provided by proj not k3b. You may both the 64 and 32 bit versions installed on your system. I would check that you have it/them installed and that the symbolic link to libproj.so.0.7.0 exits.
On 24/06/14 07:43 PM, Ed Greshko wrote:
On 06/25/14 10:35, Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
First of all, libproj.so.0 is provided by proj not k3b. You may both the 64 and 32 bit versions installed on your system. I would check that you have it/them installed and that the symbolic link to libproj.so.0.7.0 exits.
Ed,
Thanks for the reply. If I am reading this correctly:
[paul@paul Desktop]$ ls -al /usr/lib/libproj* lrwxrwxrwx 1 root root 16 Jun 24 20:20 /usr/lib/libproj.so.0 -> libproj.so.0.7.0 -rwxr-xr-x 1 root root 305696 Aug 4 2013 /usr/lib/libproj.so.0.7.0
Then it looks like libproj.so.0 is installed and the symbolic link to libproj.so.0.7.0 exists
From this:
[paul@paul Desktop]$ sudo yum list | grep libproj libprojectM.x86_64 2.0.1-20.fc20 @fedora libprojectM-devel.x86_64 2.0.1-20.fc20 @fedora libprojectM-qt.x86_64 2.0.1-8.fc20 @fedora libprojectM-qt-devel.x86_64 2.0.1-8.fc20 @fedora libprojectM.i686 2.0.1-20.fc20 fedora libprojectM-devel.i686 2.0.1-20.fc20 fedora libprojectM-qt.i686 2.0.1-8.fc20 fedora libprojectM-qt-devel.i686 2.0.1-8.fc20 fedora
It looks like both 64 and 32 bit versions are installed.
I am afraid I don't know how to remove the 32 bit version. All my attempts to use yum remove or yum erase have been unsuccessful. Any assistance you could provide would be appreciated.
On 06/25/14 12:07, Paul Erickson wrote:
On 24/06/14 07:43 PM, Ed Greshko wrote:
On 06/25/14 10:35, Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
First of all, libproj.so.0 is provided by proj not k3b. You may both the 64 and 32 bit versions installed on your system. I would check that you have it/them installed and that the symbolic link to libproj.so.0.7.0 exits.
Ed,
Thanks for the reply. If I am reading this correctly:
[paul@paul Desktop]$ ls -al /usr/lib/libproj* lrwxrwxrwx 1 root root 16 Jun 24 20:20 /usr/lib/libproj.so.0 -> libproj.so.0.7.0 -rwxr-xr-x 1 root root 305696 Aug 4 2013 /usr/lib/libproj.so.0.7.0
Then it looks like libproj.so.0 is installed and the symbolic link to libproj.so.0.7.0 exists
From this:
[paul@paul Desktop]$ sudo yum list | grep libproj libprojectM.x86_64 2.0.1-20.fc20 @fedora libprojectM-devel.x86_64 2.0.1-20.fc20 @fedora libprojectM-qt.x86_64 2.0.1-8.fc20 @fedora libprojectM-qt-devel.x86_64 2.0.1-8.fc20 @fedora libprojectM.i686 2.0.1-20.fc20 fedora libprojectM-devel.i686 2.0.1-20.fc20 fedora libprojectM-qt.i686 2.0.1-8.fc20 fedora libprojectM-qt-devel.i686 2.0.1-8.fc20 fedora
It looks like both 64 and 32 bit versions are installed.
I am afraid I don't know how to remove the 32 bit version. All my attempts to use yum remove or yum erase have been unsuccessful. Any assistance you could provide would be appreciated.
First of all, it isn't the libprojectM packages that supply libproj.so.0.
Use "yum whatprovides /usr/lib/libproj.so.0" or "yum whatprovides /usr/lib64/libproj.so.0" and you will get...
proj-4.8.0-5.fc20.x86_64 and proj-4.8.0-5.fc20.i686
Having both of these installed on your system if you have 32 bit apps and 64 bit apps that need the library. If you are running 64 bit k3b make sure you have the 64 bit version of proj installed and that /usr/lib64/libproj.so.0 exists as well as the symbolic link.
On 06/25/14 12:07, Paul Erickson wrote:
I am afraid I don't know how to remove the 32 bit version. All my attempts to use yum remove or yum erase have been unsuccessful. Any assistance you could provide would be appreciated.
Also, what do you get when you enter....
ldd -v /usr/bin/k3b | grep libproj
On 24/06/14 09:17 PM, Ed Greshko wrote:
On 06/25/14 12:07, Paul Erickson wrote:
On 24/06/14 07:43 PM, Ed Greshko wrote:
On 06/25/14 10:35, Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
First of all, libproj.so.0 is provided by proj not k3b. You may both the 64 and 32 bit versions installed on your system. I would check that you have it/them installed and that the symbolic link to libproj.so.0.7.0 exits.
Ed,
Thanks for the reply. If I am reading this correctly:
[paul@paul Desktop]$ ls -al /usr/lib/libproj* lrwxrwxrwx 1 root root 16 Jun 24 20:20 /usr/lib/libproj.so.0 -> libproj.so.0.7.0 -rwxr-xr-x 1 root root 305696 Aug 4 2013 /usr/lib/libproj.so.0.7.0
Then it looks like libproj.so.0 is installed and the symbolic link to libproj.so.0.7.0 exists
From this:
[paul@paul Desktop]$ sudo yum list | grep libproj libprojectM.x86_64 2.0.1-20.fc20 @fedora libprojectM-devel.x86_64 2.0.1-20.fc20 @fedora libprojectM-qt.x86_64 2.0.1-8.fc20 @fedora libprojectM-qt-devel.x86_64 2.0.1-8.fc20 @fedora libprojectM.i686 2.0.1-20.fc20 fedora libprojectM-devel.i686 2.0.1-20.fc20 fedora libprojectM-qt.i686 2.0.1-8.fc20 fedora libprojectM-qt-devel.i686 2.0.1-8.fc20 fedora
It looks like both 64 and 32 bit versions are installed.
I am afraid I don't know how to remove the 32 bit version. All my attempts to use yum remove or yum erase have been unsuccessful. Any assistance you could provide would be appreciated.
First of all, it isn't the libprojectM packages that supply libproj.so.0.
Use "yum whatprovides /usr/lib/libproj.so.0" or "yum whatprovides /usr/lib64/libproj.so.0" and you will get...
proj-4.8.0-5.fc20.x86_64 and proj-4.8.0-5.fc20.i686
Having both of these installed on your system if you have 32 bit apps and 64 bit apps that need the library. If you are running 64 bit k3b make sure you have the 64 bit version of proj installed and that /usr/lib64/libproj.so.0 exists as well as the symbolic link.
Thanks for this. The "yum whatprovides /usr/Lib64/libproj.so.0 revealed that somehow the 64 bit version of proj had not been installed. With it now installed K3B is back functioning properly. I don't know what caused the change, but am glad to have the functionality back.
Thanks for all the help.
On Wed, 25 Jun 2014 12:21:57 +0800, Ed Greshko wrote:
On 06/25/14 12:07, Paul Erickson wrote:
I am afraid I don't know how to remove the 32 bit version. All my attempts to use yum remove or yum erase have been unsuccessful. Any assistance you could provide would be appreciated.
Also, what do you get when you enter....
ldd -v /usr/bin/k3b | grep libproj
It's an indirect dependency only:
# repoquery --whatrequires proj|grep k3b #
# repoquery --whatrequires 'libproj.so.0()(64bit)'|grep k3b #
# rpm -q --whatrequires 'libproj.so.0()(64bit)' proj-4.8.0-5.fc20.x86_64 qt-mobility-location-1.2.2-0.12.20140317git169da60c.fc20.x86_64
# rpm --test -e qt-mobility-location qtwebkit error: Failed dependencies: qt-mobility-location(x86-64) = 1.2.2-0.12.20140317git169da60c.fc20 is needed by (installed) qt-mobility-1.2.2-0.12.20140317git169da60c.fc20.x86_64 libQtWebKit.so.4()(64bit) is needed by (installed) k3b-1:2.0.2-20.20130927git.fc20.x86_64 libQtWebKit.so.4()(64bit) is needed by (installed) kde-runtime-libs-4.12.5-1.fc20.x86_64 libQtWebKit.so.4()(64bit) is needed by (installed) kde-runtime-drkonqi-4.12.5-1.fc20.x86_64 libQtWebKit.so.4()(64bit) is needed by (installed) kdelibs-6:4.12.5-4.fc20.x86_64
Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
yum install proj
(something on your system is claiming to provide libproj.so, but actually doesn't, like the real 'proj' package does)
rpm -q --whatprovides 'libproj.so.0'
will give a clue.
-- Rex
On 25/06/14 06:00 AM, Rex Dieter wrote:
Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
yum install proj
(something on your system is claiming to provide libproj.so, but actually doesn't, like the real 'proj' package does)
rpm -q --whatprovides 'libproj.so.0'
will give a clue.
-- Rex
Thanks Rex,
That took care of it. Thanks for the time and attention.
On 06/25/2014 03:52 PM, Paul Erickson wrote:
On 24/06/14 09:17 PM, Ed Greshko wrote:
On 06/25/14 12:07, Paul Erickson wrote:
On 24/06/14 07:43 PM, Ed Greshko wrote:
On 06/25/14 10:35, Paul Erickson wrote:
I don't know exactly when this happened, but today when I tried to use K3B, I get the following error:
[paul@paul Desktop]$ k3b k3b: error while loading shared libraries: libproj.so.0: cannot open shared object file: No such file or directory
A search for libproj.so.0: reveals that it is on the system.
[paul@paul Desktop]$ whereis libproj.so.0 libproj.so: /usr/lib/libproj.so.0 [paul@paul Desktop]$
Any ideas how I can fix this? I have tried reinstalling K3B and the problem persists.
Thanks in advance.
First of all, libproj.so.0 is provided by proj not k3b. You may both the 64 and 32 bit versions installed on your system. I would check that you have it/them installed and that the symbolic link to libproj.so.0.7.0 exits.
Ed,
Thanks for the reply. If I am reading this correctly:
[paul@paul Desktop]$ ls -al /usr/lib/libproj* lrwxrwxrwx 1 root root 16 Jun 24 20:20 /usr/lib/libproj.so.0 -> libproj.so.0.7.0 -rwxr-xr-x 1 root root 305696 Aug 4 2013 /usr/lib/libproj.so.0.7.0
Then it looks like libproj.so.0 is installed and the symbolic link to libproj.so.0.7.0 exists
From this:
[paul@paul Desktop]$ sudo yum list | grep libproj libprojectM.x86_64 2.0.1-20.fc20 @fedora libprojectM-devel.x86_64 2.0.1-20.fc20 @fedora libprojectM-qt.x86_64 2.0.1-8.fc20 @fedora libprojectM-qt-devel.x86_64 2.0.1-8.fc20 @fedora libprojectM.i686 2.0.1-20.fc20 fedora libprojectM-devel.i686 2.0.1-20.fc20 fedora libprojectM-qt.i686 2.0.1-8.fc20 fedora libprojectM-qt-devel.i686 2.0.1-8.fc20 fedora
It looks like both 64 and 32 bit versions are installed.
I am afraid I don't know how to remove the 32 bit version. All my attempts to use yum remove or yum erase have been unsuccessful. Any assistance you could provide would be appreciated.
First of all, it isn't the libprojectM packages that supply libproj.so.0.
Use "yum whatprovides /usr/lib/libproj.so.0" or "yum whatprovides /usr/lib64/libproj.so.0" and you will get...
proj-4.8.0-5.fc20.x86_64 and proj-4.8.0-5.fc20.i686
Having both of these installed on your system if you have 32 bit apps and 64 bit apps that need the library. If you are running 64 bit k3b make sure you have the 64 bit version of proj installed and that /usr/lib64/libproj.so.0 exists as well as the symbolic link.
Thanks for this. The "yum whatprovides /usr/Lib64/libproj.so.0 revealed that somehow the 64 bit version of proj had not been installed. With it now installed K3B is back functioning properly. I don't know what caused the change, but am glad to have the functionality back.
Thanks for all the help.
Hi Paul, Just my 2 cents worth. As a rule of thumb in Fedora, if a library is installed into /usr/lib then it is a 32 bit application, 64 bit libraries are installed into /usr/lib64, so if you are using the 64 bit version of K3B and libproj.so.0 is in /usr/lib then that is a dead give away that the wrong version of the package is installed. This is also assuming you are using the Fedora version of K3B, all bets are off if you are using upstream applications, the obvious example of this is Firefox.
regards, Steve
-
Ed Greshko -
Michael Schwendt -
Paul Erickson -
Rex Dieter -
Stephen Morris