![]() Registered Member ![]()
|
So incase you haven't figured out from reading any of my other posts, I am quite new to KDE and pretty new to linux in general... but that being said, I seem to have a problem which is stumping the bajesus out of me, and carrying an equal weight in annoyance.
I recently installed gcaldaemon in order to sync multiple calendars from the same google account with korganizer. This ended up working quite well, so I decided I would also try to use the ldap server feature in order to sync my google contacts with Ekiga. This did not work as well, and i got output telling me it failed to connect to the google server. In my quest to get it to work, I inserted a different gcal-daemon.jar from this thread, whichfixed the failure to connect and started the ldap server, but then gave me a warning telling me I had an incompatible gmail configuration and it couldn't retrieve my contacts list. After that, I decided to give compiling the .deb package from here a try, thinking i might have gone wrong in my manual installation of the gcaldaemon. Unable to find the .jar to replace after the deb installation, I instead went back to the manual package, but installed it instead in the folder originally indicated in the instructions (/usr/share/sbin - i had originally installed it in my home folder). When this didn't fix the problem, I resigned myself to the fact that the feature is just broken, and simply went back to using the deb install (because of it's slightly improved accessibility). That was mostly just a walkthrough of what I did... now for the actual problem. Somewhere throughout this process (i think during the course of my first installation of gcaldaemon, because i didn't think i'd try reinstalling it) I apparently set the shell script standalone-start.sh to autostart with login, because now whenever I log in, my default notepad program starts and attempts to load ~/Documents/standalone-start.sh. This document does not exist, as I deleted the installation it originated from (and furthermore, the installation was not installed to that folder). I have checked my autostart options, and it is not listed as a script which attempts to autostart. I checked my .kde/autostart folder and it's not there. Does anyone know of a way (maybe through the CLI?) that I can get a deeper look and what my system is trying to autostart? Or know of any other way to help with this issue? As I was writing this, I went back and found that an autostart script DID actually exist in my .kde/autostart folder. Don't know why it didn't show up before, but oh well... If anyone has any insight to the ldap issue with gcaldaemon though, that would be much appreciated (or knows of a solution to sync/import my contacts from google with/to Ekiga). ![]() |
Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]