Incompatible library version of fontconfig

Hello,
Just in case there's a quick fix... I'm getting this message on my mac which was running this application (called "root") without problems until about 2 weeks ago. I guess some software update must have overwritten the right version of fontconfig. Maybe someone has advice?
Cheers,
Ricardo
$ root
dyld: Library not loaded: /usr/X11/lib/libfontconfig.1.dylib
Referenced from: /usr/X11/lib/libXft.2.dylib
Reason: Incompatible library version: libXft.2.dylib requires version 5.0.0 or later, but libfontconfig.1.dylib provides version 3.0.0
Trace/BPT trap

This is the root homepage:
http://root.cern.ch/
And yes, it's also the name of the admin account. I just posted to the unix forum, thanks for the tip.

Similar Messages

Bridge will not open after upgrading Reason: Incompatible library version OSX 10.6.8

I decided I would upgrade Bridge CC today, and it turns out that was a very bad idea. I have a ton of work and Bridge will not open. I can't revert back to the older bridge CC.
PLEASE HELP!!!
Reason: Incompatible library version: dvanet requires version 7.0.0 or later, but libcurl.4.dylib provides version 6.0.0

I decided I would upgrade Bridge CC today, and it turns out that was a very bad idea. I have a ton of work and Bridge will not open. I can't revert back to the older bridge CC.
PLEASE HELP!!!
Reason: Incompatible library version: dvanet requires version 7.0.0 or later, but libcurl.4.dylib provides version 6.0.0

Dashcode quits at the startup, Incompatible library version

Hi all, I'm on Snow Leopard (10.6.8) and I have a problem with Dashcode.
It quits at the startup because:
Dyld Error Message: Library not loaded: /usr/lib/libcurl.4.dylib
Referenced from: /Applications/Utilities/Dashcode.app/Contents/MacOS/../Frameworks/CYKit.
Reason: Incompatible library version: CYKit requires version 7.0.0 or later, but libcurl.4.dylib provides version 6.0.0
How do I do?
Is it possible to update this Library?
Sorry if the question is dummy, I'm totally newbie...
thank you in advance for your help

Hi! no one can give me some help? please...

HT1229 My iPhoto Library (version 8.1.2) is 280GB (greater than 50% of my 500GB total storage memory on my iMac. It was too large for me to drag it to a new hard drive so the Apple geniuses did it for me. However they did not delete the Library from my

My iPhoto Library (version 8.1.2) is 280GB (greater than 50% of my 500GB total storage memory on my iMac. It was too large for me to drag it to a new hard drive so the Apple geniuses did it for me. However they did not delete the Library from my iMac (that's my responsibility). I dragged it to Trash and when it started to move I clicked over to the new hard drive to confirm it had indeed been copied. I became nervous when I didn't see among the few files on this otherwise empty new hard drive anything that resembled a 280GB Library so I cancelled the migration to trash.
How can I be sure that my iphoto has been copied and that all my "metadata" survived in tact?

the new backup drive
I thought the new drive would be your data drive to host the iPhoto library. Do you also use it for TimeMachine backups?
I am unable to search either in email as well as Finder. I AM able to search within iPhoto though, thankfully
Spotlight may still be busy rebuildig its index.
You could try to rebuild the Spotlight Index, if you do see no progress:
Spotlight: How to re-index folders or volumes
I hope, other frequent posters will drop in. I have not used iPhoto 8.x in long time.

How to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

how to hide the file name (the bizarre number assigned by the camera) when exporting an image version in aperture from an album. Pl understand I want to keep the file name in the project library version.

Within Aperture you have Images, which are constructed on-the-fly from two files (the Master and the Version). You get an image-format file _only_ when you export an Image. You select the file name (usually a scheme) when you create an image-format file (that is, when you export). Look under "Aperture→Presets→File Naming" for built-in Presets. You can, of course, create your own or customize any provided.
The Preset is applied to only the file newly created by your "export" command. It is not applied to the Image in Aperture (unless you rename your Versions or your Masters).

Can IPhoto Library Version 9.2.3 work on snow leopard

Can Iphoto Library Version 9.2.3 work on snow leopard?

iPhoto 9.2.3 works on 10.6.8
That's what I hane on my SL machine.

Dispatcher not starting up ::Shared library version mismatch

Hi,
System is SAP ECC 6.0, AIX and Oracle 10g.
We upgraded the Kernel Level from 201 to Level 221.
<hostname>/root$ su - <sid>adm
[YOU HAVE NEW MAIL]
.profile[30]: 1: not found.
<hostname>:sidadm> disp+work
disp+work information
kernel release                700
kernel make variant           700_REL
compiled on                   AIX 2 5 005DD9CD4C00
compiled for                  64 BIT
compilation mode              UNICODE
compile time                  Aug 23 2009 20:51:38
update level                  0
patch number                  221
source id                     0.221
supported environment
database (SAP, table SVERS)   700
operating system
AIX 1 5
AIX 2 5
AIX 3 5
After upgrading the kernel dispatcher is not starting. Kindly find the below error:
sysno      10
sid        SID
systemid   324 (IBM RS/6000 with AIX)
relno      7000
patchlevel 0
patchno    221
intno      20050900
make:      single threaded, Unicode, 64 bit, optimized
pid        778402
Wed Nov 25 12:20:08 2009
kernel runs with dp version 243000(ext=110000) (@(#) DPLIB-INT-VERSION-243000-UC)
length of sys_adm_ext is 576 bytes
SWITCH TRC-HIDE on ***
***LOG Q00=> DpSapEnvInit, DPStart (10 778402) [dpxxdisp.c   1287]
DwSLCheckVersion: shared library version mismatch:
        shared lib "dw_xml.so" version 201 <-> kernel version 221
        shared lib "dw_xtc.so" version 201 <-> kernel version 221
        shared lib "dw_stl.so" version 201 <-> kernel version 221
        shared lib "dw_gui.so" version 201 <-> kernel version 221
        shared lib "dw_mdm.so" version 201 <-> kernel version 221
DP_FATAL_ERROR => Version mismatch of dw shared libraries detected. See dev_disp trace for details.
Set environment variable SAP_NO_SLIB_CHECK=1 to disable version checking.
DISPATCHER EMERGENCY SHUTDOWN ***
NiWait: sleep (5000ms) ...
NiISelect: timeout 5000ms
NiISelect: maximum fd=1
NiISelect: read-mask is NULL
NiISelect: write-mask is NULL
Wed Nov 25 12:20:13 2009
NiISelect: TIMEOUT occured (5000ms)
ERROR => DpHalt: my PID is not the dispatcher's (778402/0) [dpxxdisp.c   10510]
Kindly look into the issue. Looking forward for your reply.
Thanks,
Soumya

Soumya Saha wrote:
ERROR => DpHalt: my PID is not the dispatcher's (778402/0) http://dpxxdisp.c 10510
The system appears to think that the dispatcher process may already be running. Stop all the SAP processes and run cleanipc to clear out the shared memory. I've seen this on AIX before where the shared memory will prevent SAP from starting back up and clearing these resolved the issue.
Hope that is helpful.
J. Haynes

Incompatible class versions :linkage error- JAVADOM

HI,
We have done Mapping using java DOm,created ZIp file & successfully imported in IR.
My NWDS is using java 1.4.2_15
we are using PI70/Sp09/Java Version 1.5.0_14
During Execution in IE we are getting this error.
error -
<SAP:Code area="MAPPING">LINKAGE_ERROR</SAP:Code>
<SAP:Stack>Incompatible class versions (linkage error)</SAP:Stack>
<Trace level="1" type="T">Interface Mapping http://XI/Mapping/JavaDom/DOMMapping4 IM_ORDER1_ORDER</Trace>
<Trace level="1" type="T">LinkageError at JavaMapping.load(): Could not load class: CSJAVA/com/yash/xi/DOMMapping4</Trace>
<Trace level="1" type="T">java.lang.NoClassDefFoundError: JAVA/com/xi/DOMMapping4 (wrong name: com//xi/DOMMapping4) at java.lang.ClassLoader.defineClass0
Regards
shekar chandra

Hi,
Check the links they may help u out.
Event or DOM parsing?
http://discuss.joelonsoftware.com/default.asp?design.4.156750.12
XML Parsers: DOM and SAX Put to the Test
http://www.devx.com/xml/Article/16922/1954?pf=true
Regards,
Phani

Unable to load Adobe InDesign CC 2014 Type Library (Version 1.0)

Good evening,
I've just upgraded ID from CC to CC 2014 and now a script that had always run without issue now won't work. I get an error saying 'Unable to load Adobe InDesign CC 2014 Type Library (Version 1.0)'
The bit of code I was running was executing a little VB script copying files:
        var vbScript = 'Set fs = CreateObject("Scripting.FileSystemObject")\r';
        vbScript += 'fs.CopyFile "' + f.fsName.replace("\\", "\\\\") + '", "' + destinationFolder.fsName.replace("\\", "\\\\") + "\\" + f.name + '"';
        app.doScript(vbScript, ScriptLanguage.visualBasic);
From trawling the net I can see stuff about the 'Resources for Visual Basic.tlb' file. I can see this in the C:\ProgramData\Adobe\InDesign\Version 10.0\en_GB\Scripting Support\10.1 folder but clearly it isn't registered or something similar.
Can anyone help me get past this problem?
Thanks for any help.

Thanks for your prompt reply.
Do you mean copy the 'Resources for Visual Basic.tlb' into the Version 9 folder?
If so I already have the file in there: "C:\ProgramData\Adobe\InDesign\Version 9.0\en_US\Scripting Support\9.0\Resources for Visual Basic.tlb" as well as the file in this location: "C:\ProgramData\Adobe\InDesign\Version 10.0\en_US\Scripting Support\10.1\Resources for Visual Basic.tlb"
The only difference between the 2 installs that I can see is that v10 also has a locale for en_GB.

Error starting Software Update Manager (SUM) Can't retrieve C library version

Hi,
I am trying to update my SAP Solution Manager 7.1 SP04 to SP11 on a Debain squeeze. I did create a stack.xml and downloaded SUM SP10 (SUM10SP10_4-20006543.SAR)
unpacked location is /usr/sap/S01/SUM
I tried to run ./STARTUP with user s01adm but I got the following error:








May 6, 2014 3:23:52 PM [Info]: *************************************************
May 6, 2014 3:23:52 PM [Info]: Starting SL Controller listening on port 4241 ...
May 6, 2014 3:23:52 PM [Info]: Starting StorageService ...
May 6, 2014 3:23:52 PM [Info]: Initializing SecurityManager ...
May 6, 2014 3:23:54 PM [Info]: Server certificate fingerprint is 3E 76 23 18 C1 74 AC B9 5D E4 CC 88 BF FE 3A 08
May 6, 2014 3:23:54 PM [Info]: Configuring HTTPManager ...
May 6, 2014 3:23:54 PM [Info]: Starting WebstartService ...
May 6, 2014 3:23:54 PM [Info]: Starting RoleService ...
May 6, 2014 3:23:54 PM [Info]: Starting AlertService ...
May 6, 2014 3:23:54 PM [Info]: Starting NotesService ...
May 6, 2014 3:23:54 PM [Info]: Starting ProcessService ...
May 6, 2014 3:23:54 PM [Info]: Starting MIDService ...
May 6, 2014 3:23:54 PM [Info]: Starting FileService ...
May 6, 2014 3:23:54 PM [Info]: LogService switched off.
May 6, 2014 3:23:54 PM [Info]: Starting MailService ...
May 6, 2014 3:23:54 PM [Info]: Starting services ...
May 6, 2014 3:23:54 PM [Info]: Starting service "UseCaseService" ...
May 6, 2014 3:23:55 PM [Info]: Starting MIDService ...
May 6, 2014 3:23:59 PM [Error]: Can't retrieve C library version.
May 6, 2014 3:23:59 PM [Error]: Error while initializing service context.
May 6, 2014 3:23:59 PM [Error]: Can't initilize sdt service provider
May 6, 2014 3:23:59 PM [Error]: Creation of use case executor failed.
May 6, 2014 3:23:59 PM [Fatal]: Error during controller startup.
May 6, 2014 3:23:59 PM [Fatal]: SL Controller exiting.
This is what /usr/sap/S01/SUM/sdt/trc/DETECT.TRC reports:








May 6, 2014 3:23:56 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path
May 6, 2014 3:23:57 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path
May 6, 2014 3:23:57 PM [Error]:                                                                    com.sap.sdt.dmt.DMTFactoryManager [Thread[main,5,main]]: Property file dmt.properties not found in class path
May 6, 2014 3:23:58 PM [Error]:                                                                  com.sap.sdt.jspm.JspmFactoryManager [Thread[main,5,main]]: Property file jspm.properties not found in class path
May 6, 2014 3:23:59 PM [Error]:            com.sap.sdt.tools.sysinfo.unx.UnixDetermineOSInfo.setupUNIX(UnixDetermineOSInfo.java:131) [Thread[main,5,main]]: Can't retrieve C library version.
May 6, 2014 3:23:59 PM [Error]:                                                         com.sap.sdt.server.core.admin.SDTServerAdmin [Thread[main,5,main]]: com.sap.sdt.tools.sysinfo.DetermineOSException: Can't retrieve C library version.
at com.sap.sdt.tools.sysinfo.unx.UnixDetermineOSInfo.setupUNIX(UnixDetermineOSInfo.java:131)
at com.sap.sdt.tools.sysinfo.unx.UnixDetermineOSInfo.<init>(UnixDetermineOSInfo.java:64)
at com.sap.sdt.tools.sysinfo.unx.UnixOSInfoFactory.getOSInfo(UnixOSInfoFactory.java:29)
at com.sap.sdt.j2ee.services.OSInfoServiceRetriever.retrieveOSInfo(OSInfoServiceRetriever.java:47)
at com.sap.sdt.j2ee.services.SDTServiceProvider.detectOSInformation(SDTServiceProvider.java:587)
at com.sap.sdt.j2ee.services.SDTServiceProvider.initServiceContext(SDTServiceProvider.java:414)
at com.sap.sdt.j2ee.services.SDTServiceProvider.initialize(SDTServiceProvider.java:180)
at com.sap.sdt.executor.service.ServiceAndBeanProviderFactory.getServiceAndBeanProvider(ServiceAndBeanProviderFactory.java:120)
at com.sap.sdt.executor.usecase.UseCaseExecutionInitializer.getServiceBeanProviderWrapper(UseCaseExecutionInitializer.java:268)
at com.sap.sdt.executor.usecase.UseCaseExecutionInitializer.initialize(UseCaseExecutionInitializer.java:155)
at com.sap.sdt.executor.factory.UseCaseExecutorFactory.createUseCaseExecutor(UseCaseExecutorFactory.java:56)
at com.sap.sdt.dsu.service.UseCaseService.createUseCaseExecutor(UseCaseService.java:1014)
at com.sap.sdt.dsu.service.UseCaseService.initDetectUseCaseExecutor(UseCaseService.java:1027)
at com.sap.sdt.dsu.service.UseCaseService.init(UseCaseService.java:166)
at com.sap.sdt.server.core.services.Service.start(Service.java:94)
at com.sap.sdt.server.core.admin.SDTServerAdmin.startServices(SDTServerAdmin.java:1155)
at com.sap.sdt.server.core.admin.SDTServerAdmin.start(SDTServerAdmin.java:367)
at com.sap.sdt.server.core.admin.SDTServerAdmin.runServer(SDTServerAdmin.java:847)
at com.sap.sdt.server.core.admin.SDTServerAdmin.start(SDTServerAdmin.java:217)
at com.sap.sdt.server.core.admin.SDTServerAdmin.main(SDTServerAdmin.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.sdt.bootstrap.BootStrap.start(BootStrap.java:169)
at com.sap.sdt.bootstrap.Startup.start(Startup.java:140)
at com.sap.sdt.bootstrap.Startup.main(Startup.java:356)
May 6, 2014 3:23:59 PM [Error]:                 com.sap.sdt.j2ee.services.SDTServiceProvider.initialize(SDTServiceProvider.java:184) [Thread[main,5,main]]: Error while initializing service context.
May 6, 2014 3:23:59 PM [Error]: com.sap.sdt.executor.service.ServiceAndBeanProviderFactory.getServiceAndBeanProvider(ServiceAndBeanProviderFactory.java:125) [Thread[main,5,main]]: Can't initilize sdt service provider
May 6, 2014 3:23:59 PM [Error]:           com.sap.sdt.dsu.service.UseCaseService.initDetectUseCaseExecutor(UseCaseService.java:1031) [Thread[main,5,main]]: Creation of use case executor failed.
May 6, 2014 3:23:59 PM [Fatal]:                 com.sap.sdt.server.core.admin.SDTServerAdmin.startServices(SDTServerAdmin.java:1165) [Thread[main,5,main]]: Error during controller startup.
May 6, 2014 3:23:59 PM [Fatal]:                 com.sap.sdt.server.core.admin.SDTServerAdmin.startServices(SDTServerAdmin.java:1166) [Thread[main,5,main]]: SL Controller exiting.
Any idea what could be wrong?
Thanks,
Sven

SUM checks the libc version by parsing the output of 'ldd --version'.
The java code looks like this:
String[] parsedOutput = getCommandOutput("ldd", new ValueIF[] { new StringValue("--version") }).split("libc\\) ");
   if (parsedOutput.length > 1) {
   this.cLibraryVersion = parsedOutput[1];
} else {
   throw new DetermineOSException("msg.tools.sysInfo.0078");
With newer releases of libc, the output of ldd --version no longer contains a string matching the pattern "libc\\) ", so this fails.
A rather quick-and-dirty workaround:
- rename the ldd executable to ldd.exe
- create the following shell script named ldd in /usr/bin:
#!/bin/sh
if [ $1 == "--version" ] ; then
echo "libc) 2.17"
else
/usr/bin/ldd.exe $@
fi
As SUM ignores the PATH variable it is not possible to place the modified ldd into some other directory.
br,
Sebastian

Incompatible Xalan version in IDE class path? (Max OS X Leopard)

Hi all,
I have been using NetBeans 6.1 for a while and all was well. I then installed a few plug-ins (including iReport, which I believe may be the problem). When I start the IDE I get the error "Incompatible Xalan version found in IDE class phat" and gives some link that didn't help. I have uninstalled NetBeans and reinstalled, which obviously didn't fix the problem. If anybody can help me at all, I would appreciate it very much. I really need this to run, I would hate to completely reinstall the OS to get it back going. Thanks in advance for any support.
Edited by: JavaChip on Jul 7, 2008 4:32 PM

Hi,
I encountered this problem today and I'm also using Netbeans 6.1 on Mac OS X (10.5.4). It was definitely the iReports plugin. I found a solution here:
[http://blogs.sun.com/geertjan/entry/analyzing_the_jasperreports_visual_designer]
However, I only had to remove the file xalan.jar (and keep xalan-2.7.0.jar) from the ~/.netbeans/6.1/modules/ext directory. No changes to the config were required and the iReport plugin worked.
Edited by: d_herb on Aug 5, 2008 7:45 AM

An incompatible xalan version has been detected on the ide's classpath OSX

Hi all,
I have tried to install netbeans/java tools bundle on my mac, keep getting the same error.
an incompatible xalan version has been detected on the ide's classpath. The IDE cannot start. pLease see http://wiki.java.net/bin/view/Netbeans/FaqXalanOnCP for more info.
I have had a look at this website, it says to Due to a bug in Xalan, project metadata may get corrupted when a Xalan is on the IDE classpath. For this reason, the IDE refuses to start when the broken Xalan is detected on the classpath. Please remove the Xalan under jre/lib/**.
This is quite difficult as it does not tell me the path where this file exists.
Can anyone please help me out??

That "someone" is each individual Firefox user who encounters problems like this. Mozilla stopped doing its' "web evangelism" program to help and advise websites about fixing their websites. I suppose 7 years was long enough to try fixing the web, and their time was better spent concentrating on improving Firefox.
My advice is to install an older version of Firefox Portable to use at that web site, and to continue using your current version of Firefox elsewhere. <br />
http://portableapps.com/apps/internet/firefox_portable/localization#legacy36

FXComps Library (version: 1.0.0) is released (BSD license)

FXComps Library (version: 1.0.0) is released (BSD license).
http://www.fxcomps.com/downloads.html
FXComps Library contains the following former FXComps libraries (as well as new components and classes):
- FXComps Core
- FXComps Money & Decimal
- FXComps VAComboBox
- FXComps Collator
New classes & components:
- Table component for reporting purposes
- Enhanced versions of several controls
- ResourceUpdater
- Printing & print preview
- etc.
For more information, follow this link:
http://www.fxcomps.com
Regards,
Laszlo Sas

The "Significant Changes since Beta" section is not present in the in released documentation (...\jwsdp-1.1\jaxb-1.0\docs\ReleaseNotes.html)
... [flame, flame, rant, rant, ...] ... which cost me a LOT of time

GPIB-USB-B VISA I/O Library version

I need a GPIB interface that VISA I/O Library version 1.1 compliant to connect to an Agilet 8722ES network analyzer. Is the GPIB-USB-B VISA I/O Library version 1.1 compliant?
Thanks,
Brian Keats

Hi Brian,
The GPIB-USB-B device is simply a hardware device that responds to the driver you have installed for the device. The NI-488.2 drivers which control the device have complete NI-VISA functionality, and there is even an instrument driver on our website available for this device which uses GPIB and VISA. You can click here to go to the download page. The GPIB-USB-B should work great for this application.
John M
Applications Engineer

The API Library version must match the MDM Server version

hi friends,
The API Library version must match the MDM Server version
is it compulsory.
if so please let me know the compatible matching versions between them....

Hi Ram,
Yes the JAR file Version should be compatible with the version of MDM Server.
Supposedly you have MDM Version of SP05 the Jar files should also be of SP05 version , if you use JAR files of older version it wouldnt contain new classes and methods of the newer APIs and would also contain some old classes which arent present in latest version.
Thanks
Namrata

Incompatible library version of fontconfig

Similar Messages

Maybe you are looking for