Version: (using KDE 4.2.4) OS: Linux Installed from: Ubuntu Packages I am getting a HotSync error. This is the first attempt to use kpilot to sync my Handspring Visor. I checked all of the connection information on both the kpilot and the Visor. The output from kpilot is as follows: Application: KPilot (kpilot), signal SIGSEGV 0x00007f00395aa8f5 in waitpid () from /lib/libc.so.6 Thread 1 (Thread 0x7f003d2cc750 (LWP 4479)): [KCrash Handler] #4 0x00007f003bc17764 in KPageWidgetItem::setName () from /usr/lib/libkdeui.so.5 #5 0x000000000041a403 in _start () I don't know what to do next. Please help!
Hi Earl, I've tried to reproduce your error without much success. I have kubuntu and a Handspring Visor also. I don't know if I can help you, but here are a few questions that might help track this down: 1) I notice you are using KDE 4.2.4. Is this from Karmic? I have Jaunty and 4.2.2. kde-nightly gives me 4.3.something... 2) Do you have akonadi installed and the server running? Are the conduits enabled and pointing to the right "resources"? 3) it seems like "kpilot" itself is failing, which is interesting - I believe it's kpilotDaemon that does all the work. Normally we can get a debug log by doing running the two manually like this: killall kpilot kpilotDaemon kpilotDaemon --debug=9 > ~/kpilotDaemon.debug 2>&1 kpilot If you're able to run that way could you post the resulting debug log?
Here are some errors I got when I opened KPilot Main Configuration. I tried to enable "Contacts" conduit and got this message/report. I get the same result when I try to enable the "Contacts", "To-do" and "Calendar" conduits I also got an errorl when I selected "OK" which stated "The Configuration file for KPilot is out-of-date. Please run KPilot to update it. Since that is exactly what I did when I got the error pop-up window, how do I actually "update" the configuration file? Thanks, and here is the report. Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration. The following drivers are installed: QMYSQL3, QMYSQL. Make sure the required driver is installed. File '/home/skeet/.config/akonadi/akonadiserverrc' could not be opened Test 2: ERROR -------- MySQL server not found. Details: You currently have configured Akonadi to use the MySQL server ''. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld', its locations varies depending on the distribution. Test 3: ERROR -------- Executing the MySQL server failed. Details: Executing the MySQL server '' failed with the following error message: '' Test 4: SUCCESS -------- No current MySQL error log found. Details: The MySQL server did not report any errors during this startup into '/home/skeet/.local/share/akonadi/db_data/mysql.err'. Test 5: ERROR -------- MySQL server default configuration not found. Details: The default configuration for the MySQL server was not found or was not readable. Check your Akonadi installation is complete and you have all required access rights. Test 6: SKIP -------- MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 7: ERROR -------- MySQL server configuration not found or not readable. Details: The MySQL server configuration was not found or is not readable. Test 8: ERROR -------- akonadictl not found Details: The program 'akonadictl' needs to be accessible in $PATH. Make sure you have the Akonadi server installed. Test 9: ERROR -------- Akonadi control process not registered at D-Bus. Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 10: ERROR -------- Akonadi server process not registered at D-Bus. Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 11: SKIP -------- Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 12: ERROR -------- No resource agents found. Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: ''. The XDG_DATA_DIRS environment variable is set to '/usr/local/share/:/usr/share/:/usr/share/gdm/', make sure this includes all paths where Akonadi agents are installed to. Directory list is empty. Environment variable XDG_DATA_DIRS is set to '/usr/local/share/:/usr/share/:/usr/share/gdm/' Test 13: SUCCESS -------- No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 14: SUCCESS -------- No previous Akonadi server error log found. Details: The Akonadi server did not report any errors during its previous startup. Test 15: SUCCESS -------- No current Akonadi control error log found. Details: The Akonadi control process did not report any errors during its current startup. Test 16: SUCCESS -------- No previous Akonadi control error log found. Details: The Akonadi control process did not report any errors during its previous startup. On Sun, Aug 9, 2009 at 8:03 PM, Jeff Trull <jetrull@sbcglobal.net> wrote: > https://bugs.kde.org/show_bug.cgi?id=199624 > > > Jeff Trull <jetrull@sbcglobal.net> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |jetrull@sbcglobal.net > > > > > --- Comment #1 from Jeff Trull <jetrull sbcglobal net> 2009-08-10 03:03:49 > --- > Hi Earl, > > I've tried to reproduce your error without much success. I have kubuntu > and a > Handspring Visor also. I don't know if I can help you, but here are a few > questions that might help track this down: > > 1) I notice you are using KDE 4.2.4. Is this from Karmic? I have Jaunty > and > 4.2.2. kde-nightly gives me 4.3.something... > 2) Do you have akonadi installed and the server running? Are the conduits > enabled and pointing to the right "resources"? > 3) it seems like "kpilot" itself is failing, which is interesting - I > believe > it's kpilotDaemon that does all the work. Normally we can get a debug log > by > doing running the two manually like this: > > killall kpilot kpilotDaemon > kpilotDaemon --debug=9 > ~/kpilotDaemon.debug 2>&1 > kpilot > > If you're able to run that way could you post the resulting debug log? > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. >
Here is the output from the commands you asked me to run from the terminal window. root@Dumbo:/home/skeet# killall kpilot kpilotDaemon kpilot: no process killed kpilotDaemon: no process killed root@Dumbo:/home/skeet# kpilotDaemon --debug=9 > kpilotDaemon.debug 2>&1 root@Dumbo:/home/skeet# kpilot <unknown program name>(7921)/: KUniqueApplication: Cannot find the D-Bus session server <unknown program name>(7920)/: KUniqueApplication: Pipe closed unexpectedly. On Tue, Aug 11, 2009 at 11:58 AM, Earl <biyouboogie@gmail.com> wrote: > Here are some errors I got when I opened KPilot Main Configuration. I > tried to enable "Contacts" conduit and got this message/report. I get the > same result when I try to enable the "Contacts", "To-do" and "Calendar" > conduits > > I also got an errorl when I selected "OK" which stated "The Configuration > file for KPilot is out-of-date. Please run KPilot to update it. Since > that is exactly what I did when I got the error pop-up window, how do I > actually "update" the configuration file? > > Thanks, and here is the report. > > > > Akonadi Server Self-Test Report > =============================== > > Test 1: SUCCESS > -------- > > Database driver found. > Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi > server configuration. > The following drivers are installed: QMYSQL3, QMYSQL. > Make sure the required driver is installed. > > File '/home/skeet/.config/akonadi/akonadiserverrc' could not be opened > > Test 2: ERROR > -------- > > MySQL server not found. > Details: You currently have configured Akonadi to use the MySQL server ''. > Make sure you have the MySQL server installed, set the correct path and > ensure you have the necessary read and execution rights on the server > executable. The server executable is typically called 'mysqld', its > locations varies depending on the distribution. > > Test 3: ERROR > -------- > > Executing the MySQL server failed. > Details: Executing the MySQL server '' failed with the following error > message: '' > > Test 4: SUCCESS > -------- > > No current MySQL error log found. > Details: The MySQL server did not report any errors during this startup > into '/home/skeet/.local/share/akonadi/db_data/mysql.err'. > > Test 5: ERROR > -------- > > MySQL server default configuration not found. > Details: The default configuration for the MySQL server was not found or > was not readable. Check your Akonadi installation is complete and you have > all required access rights. > > Test 6: SKIP > -------- > > MySQL server custom configuration not available. > Details: The custom configuration for the MySQL server was not found but is > optional. > > Test 7: ERROR > -------- > > MySQL server configuration not found or not readable. > Details: The MySQL server configuration was not found or is not readable. > > Test 8: ERROR > -------- > > akonadictl not found > Details: The program 'akonadictl' needs to be accessible in $PATH. Make > sure you have the Akonadi server installed. > > Test 9: ERROR > -------- > > Akonadi control process not registered at D-Bus. > Details: The Akonadi control process is not registered at D-Bus which > typically means it was not started or encountered a fatal error during > startup. > > Test 10: ERROR > -------- > > Akonadi server process not registered at D-Bus. > Details: The Akonadi server process is not registered at D-Bus which > typically means it was not started or encountered a fatal error during > startup. > > Test 11: SKIP > -------- > > Protocol version check not possible. > Details: Without a connection to the server it is not possible to check if > the protocol version meets the requirements. > > Test 12: ERROR > -------- > > No resource agents found. > Details: No resource agents have been found, Akonadi is not usable without > at least one. This usually means that no resource agents are installed or > that there is a setup problem. The following paths have been searched: ''. > The XDG_DATA_DIRS environment variable is set to > '/usr/local/share/:/usr/share/:/usr/share/gdm/', make sure this includes all > paths where Akonadi agents are installed to. > > Directory list is empty. > > Environment variable XDG_DATA_DIRS is set to > '/usr/local/share/:/usr/share/:/usr/share/gdm/' > > Test 13: SUCCESS > -------- > > No current Akonadi server error log found. > Details: The Akonadi server did not report any errors during its current > startup. > > Test 14: SUCCESS > -------- > > No previous Akonadi server error log found. > Details: The Akonadi server did not report any errors during its previous > startup. > > Test 15: SUCCESS > -------- > > No current Akonadi control error log found. > Details: The Akonadi control process did not report any errors during its > current startup. > > Test 16: SUCCESS > -------- > > No previous Akonadi control error log found. > Details: The Akonadi control process did not report any errors during its > previous startup. > > > > > On Sun, Aug 9, 2009 at 8:03 PM, Jeff Trull <jetrull@sbcglobal.net> wrote: > >> https://bugs.kde.org/show_bug.cgi?id=199624 >> >> >> Jeff Trull <jetrull@sbcglobal.net> changed: >> >> What |Removed |Added >> >> ---------------------------------------------------------------------------- >> CC| |jetrull@sbcglobal.net >> >> >> >> >> --- Comment #1 from Jeff Trull <jetrull sbcglobal net> 2009-08-10 >> 03:03:49 --- >> Hi Earl, >> >> I've tried to reproduce your error without much success. I have kubuntu >> and a >> Handspring Visor also. I don't know if I can help you, but here are a few >> questions that might help track this down: >> >> 1) I notice you are using KDE 4.2.4. Is this from Karmic? I have Jaunty >> and >> 4.2.2. kde-nightly gives me 4.3.something... >> 2) Do you have akonadi installed and the server running? Are the conduits >> enabled and pointing to the right "resources"? >> 3) it seems like "kpilot" itself is failing, which is interesting - I >> believe >> it's kpilotDaemon that does all the work. Normally we can get a debug log >> by >> doing running the two manually like this: >> >> killall kpilot kpilotDaemon >> kpilotDaemon --debug=9 > ~/kpilotDaemon.debug 2>&1 >> kpilot >> >> If you're able to run that way could you post the resulting debug log? >> >> -- >> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email >> ------- You are receiving this mail because: ------- >> You reported the bug. >> > >
Hi Earl, It sounds as if akonadi is not installed... and unfortunately this won't happen automatically - you would have to specifically install it (with apt-get or your favorite tool). I used this command, I think: sudo apt-get install akonadi and by the way, the debug log I was referring to is the actual file kpilotDaemon.debug, which should be present in your home directory. There's no need to post it if installing akonadi solves your problem.
Thanks for responding. Yes I did install akonadi once I realized it was not installed. However, the KPilot app wants me to select a calendar, etc. When I try to select the Contacts, To-do, and Calendar conduit I get an error that says "No collection selected yet. Make sure you select a collection before synchronizing. If you do not see any collections in the combobox, make sure that Akonadi started and that there is a valid resource for this data type". My question is, with the limited knowledge I have of this application, is it ok to NOT use the Contacts, To-do, Calendar conduit to get the application to run for the first time? Because when I ignore those conduits, the program comes back with a message saying " The configuration file is outdated. The configuration file has version 0, while KPilot needs version 520. Please run KPilot and check the configuration carefully to update the file." How do I run KPilot, when I get that error when I try to run it. Am I missing something, or is there a command line or script that I need to use to update the configuration file? You have been VERY helpful. I'm sure you know what to tell me to do. :) On Wed, 2009-08-12 at 05:28 +0200, Jeff Trull wrote: > https://bugs.kde.org/show_bug.cgi?id=199624 > > > > > > --- Comment #4 from Jeff Trull <jetrull sbcglobal net> 2009-08-12 05:28:09 --- > Hi Earl, > > It sounds as if akonadi is not installed... and unfortunately this won't happen > automatically - you would have to specifically install it (with apt-get or your > favorite tool). I used this command, I think: > > sudo apt-get install akonadi > > and by the way, the debug log I was referring to is the actual file > kpilotDaemon.debug, which should be present in your home directory. There's no > need to post it if installing akonadi solves your problem. >
Yes, I think you still have some configuration to do. This requires a FAQ - maybe I'll write it :) You have to go into the Akonadi configuration (System Settings -> Advanced -> Akonadi). Under "Akonadi Resources Configuration" there is one calendar (.ics) file and one contact (.vcf) file. Unfortunately they are not set up by default in Kubuntu - you have to select each one, click "modify", and then point them to the correct files, which in my case are: ~/.kde/share/apps/korganizer/std.ics ~/.kde/share/apps/kabc/std.vcf Now you have Akonadi acting as an agent, essentially, through which kpilot and kontact should access these files. The last step is to go into the kpilot settings and pick the std.ics and std.vcf files as "collections" for the Contact and Calendar sync (just click on the name and hit "apply" in each). That's what I had to do. As for the warning messages regarding setup, you are not the only one who finds them confusing - I believe there is at least one Launchpad bug filed on this, or maybe it's here in the KDE bugdb. I suggest ignoring them if my directions work :)
Thanks, that was very helpful. I have it all configured now. However, NOW the HotSync will not work. For some reason, KPilot can not open /dev/pilot which implies that it can not see the device. Mine is connected through USB, and I have HotSync configured to run on the USB conduit. Any suggestions? You seem to be the only person who really knows how to get this working. On Wed, 2009-08-12 at 23:04 +0200, Jeff Trull wrote: > https://bugs.kde.org/show_bug.cgi?id=199624 > > > > > > --- Comment #6 from Jeff Trull <jetrull sbcglobal net> 2009-08-12 23:04:14 --- > Yes, I think you still have some configuration to do. This requires a FAQ - > maybe I'll write it :) You have to go into the Akonadi configuration (System > Settings -> Advanced -> Akonadi). Under "Akonadi Resources Configuration" > there is one calendar (.ics) file and one contact (.vcf) file. Unfortunately > they are not set up by default in Kubuntu - you have to select each one, click > "modify", and then point them to the correct files, which in my case are: > > ~/.kde/share/apps/korganizer/std.ics > ~/.kde/share/apps/kabc/std.vcf > > Now you have Akonadi acting as an agent, essentially, through which kpilot and > kontact should access these files. The last step is to go into the kpilot > settings and pick the std.ics and std.vcf files as "collections" for the > Contact and Calendar sync (just click on the name and hit "apply" in each). > That's what I had to do. > > As for the warning messages regarding setup, you are not the only one who finds > them confusing - I believe there is at least one Launchpad bug filed on this, > or maybe it's here in the KDE bugdb. I suggest ignoring them if my directions > work :) >
Go into the Configure menu, General Setup -> Device, and set Pilot device to "usb:", that's four characters, ending in a colon.
Dude, You are the MAN. It works now! I can't tell you how much I thank you for your help. Skeet On Thu, 2009-08-13 at 06:55 +0200, Jeff Trull wrote: > https://bugs.kde.org/show_bug.cgi?id=199624 > > > > > > --- Comment #8 from Jeff Trull <jetrull sbcglobal net> 2009-08-13 06:55:16 --- > Go into the Configure menu, General Setup -> Device, and set Pilot device to > "usb:", that's four characters, ending in a colon. >
Jeff, I got my PDA working on Ubuntu. Now, if you could give me just a little more information I would appreciate it. I have downloaded a few eBooks onto my Acer and would like to know how to "install" them on the Handspring PDA. I remember that there was an "installer" for my iPaq that I had years ago. Does the same thing exist, and work on Ubuntu for this Handspring. BTW my Handspring is the Visor Edge. I finally figured out which one it is. :) Skeet On Thu, 2009-08-13 at 06:55 +0200, Jeff Trull wrote: > https://bugs.kde.org/show_bug.cgi?id=199624 > > > > > > --- Comment #8 from Jeff Trull <jetrull sbcglobal net> 2009-08-13 06:55:16 --- > Go into the Configure menu, General Setup -> Device, and set Pilot device to > "usb:", that's four characters, ending in a colon. >
Hi Earl, I'm really not sure about the eBooks, but conduits in kpilot are generally in "beta" shape right now so I wouldn't guess that sort of thing exists yet (unless the "file installer" does it?). Since things are working, would you mind closing this bug? Otherwise someone will come along and try to "fix" it again. I'll write up a FAQ and post on ubuntuforums.org.
Thanks to Jeff, this now works for me. I am closing the "bug". Thanks.
Thanks Jeff for picking this up. It would be great if you'd be able to add some info to a faq. Preferably here: http://techbase.kde.org/Projects/PIM/KPilot. Thanks again.