Fedora 20 K3B broken

[Stephen Morris]

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 at 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 at paul Desktop]$ whereis libproj.so.0
>>>>> libproj.so: /usr/lib/libproj.so.0
>>>>> [paul at 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 at 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 at 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


-------------- next part --------------
A non-text attachment was scrubbed...
Name: samorris.vcf
Type: text/x-vcard
Size: 130 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20140626/4e978379/attachment.vcf>