Bug 608386

Summary: clock-applet depends on wrong libedataserver
Product: [Fedora] Fedora Reporter: Dave Botsch <botsch>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: lucilanga, mbarnes, mclasen, mcrha, pmrpla, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 17:55:08 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:
Attachments:
Description Flags
output from yum update evolution none

Description Dave Botsch 2010-06-27 06:22:49 UTC 
Description of problem:

In FC13, 64-bit, the clock-applet will not start. Evidently, the clock-applet wants an older version of libedataserver than what comes w. FC13.


Version-Release number of selected component (if applicable):
gnome-panel-2.30.0-1.fc13.x86_64



How reproducible:
100% of the time

Steps to Reproduce:
1. Install FC13 64-bit
2. Try to start the clock-applet
  
Actual results:

You can only get the actual error message from the commandline:

$ /usr/libexec/clock-applet 
/usr/libexec/clock-applet: error while loading shared libraries: libedataserver-1.2.so.11: cannot open shared object file: No such file or directory


Expected results:

Clock applet starts

Additional info:

$ locate libedataserver-1.2.so
/usr/lib/libedataserver-1.2.so.13
/usr/lib/libedataserver-1.2.so.13.0.1
/usr/lib64/libedataserver-1.2.so
/usr/lib64/libedataserver-1.2.so.13
/usr/lib64/libedataserver-1.2.so.13.0.1

$ rpm -q evolution-data-server
evolution-data-server-2.30.2-2.fc13.x86_64
evolution-data-server-2.30.2-2.fc13.i686
Comment 1 Jim Haynes 2010-06-28 16:39:23 UTC 
Created attachment 427456 [details]
output from yum update evolution
Comment 2 Matthias Clasen 2010-06-28 17:43:45 UTC 
This is a problem with a bad evolution update that should have not gone out.
Comment 3 Milan Crha 2010-06-28 17:55:08 UTC 

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