[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] The library containing the configuration wizard
From:       Klaus Brause <thorsten () billib ! de>
Date:       2006-11-12 14:44:46
Message-ID: 4557335E.2090601 () billib ! de
[Download RAW message or body]

Jason 'vanRijn' Kasper schrieb:
> On Saturday 11 November 2006 17:19, Klaus Brause wrote:
>   
>> Ciao all,
>>
>> I am (like many others these days, it seems) trying to sync my treo 650
>> to the Edgy Eft-box on my desktop.
>>
>> After compiling the svn-sources (Thanks again, Adriaan, seems I was
>> slightly too drunk to tell "libcal..." from "libkcal..." this night) and
>> starting kpilot, I chose to use the wizard to configure kpilot. The
>> anwer was something like "The library containing the configuration
>> wizard for KPilot could not be started..." , well, in german. With the
>> other opporutnity the dialogue-box just stayed clear. No activity
>> whatsoever.
>>
>>  All I could find with google was codeyard.net-sourcecode, which does
>> not really help me. Hope this is a well known thread and I am geting on
>> your nerves, but a brief look in the archives showed nothing similar.
>>     
>
> Hi Klaus!
>
> Oooh, I just saw this myself recently.  Oh--I think it was because I was 
> trying to launch kpilotDaemon or kpilot from KDE's "run" dialog.  The 
> problem, I think, is that there's something broken with how KDE launches 
> programs that are not installed in the same KDEDIR as the base KDE 
> installation.  For instance, I run FC6 nowadays on my powerbook, and all of 
> KDE (including KDEPIM) is installed via RPM in /usr.  However, I build kpilot 
> from codeyard's svn repository and install it into $HOME/local/kde3.  If I 
> start kpilotDaemon from KDE's run command dialog, and then kpilotDaemon tries 
> to launch the configurator, I get the same error you did, I believe.  If, 
> however, I start kpilotDaemon from a konsole window after having properly set 
> KDEDIR, LD_LIBRARY_PATH, etc., then I do not.
>
> So, long answer short: try launching kpilotDaemon and kpilot ONLY from a 
> konsole window where you've previously properly set up KDEDIR, 
> LD_LIBRARY_PATH, etc.
>
> HTH!  =:)
>
>   
Thanks a lot Jason,

I did actually try to start from the console, but did not set any 
variables or paths. Oh, if you could see me blushing...
After several years of scraping by on linux iI should have been thinking 
of that. Will try to figure out how, thanks again,

Thorsten

P.S.: This is a bit off-topic, but let me say my name is Thorsten. Klaus 
Brause is actually just some german tomfool-name, which I use because it 
seems so strange to me that the installing-routines of all the operating 
systems insist on knowing your real name. An ironic attempt to seem 
brighter than the machine...
_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users
[prev in list] [next in list] [prev in thread] [next in thread]