Bug 668309

Summary: How I fixed the anjuta 1:2.32.1.1-1.fc14 I received today
Product: [Fedora] Fedora Reporter: rmknox <knox>
Component: anjutaAssignee: Debarshi Ray <debarshir>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: debarshir, jhs, rpandit
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-16 21:03:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description rmknox 2011-01-10 00:28:22 UTC
Description of problem: dies when i start it


Version-Release number of selected component (if applicable):
anjuta.i686                      1:2.32.1.1-1.fc14                      @updates

How reproducible:
100%


Steps to Reproduce:
1.start it
2.
3.
  
Actual results:
dies complains about libsqlite.so

Expected results:


Additional info:
I am running under
kernel.i686  2.6.35.10-74.fc14   @anaconda-InstallationRepo-201010211814.i386 

today when I ran yum update it delivered
anjuta.i686                      1:2.32.1.1-1.fc14                      @updates

which died when I tried to start it, complaining about libsqlite.so

I tried to file the automatic problem report, but the system rejected it telling me that the problem is fixed.

I then ran yum install libsqlite*

It installed 

libsqlite3x.i686                        20071018-9.fc14                  @fedora

libsqlite3x-devel.i686                  20071018-9.fc14                  @fedora


plus something else – and anjuta now works.

This is described in more detail in the report that i tried to file automatically - maybe it is in your system?

Comment 1 Johannes Schmid 2011-02-16 21:03:21 UTC

*** This bug has been marked as a duplicate of bug 657368 ***