Re: No package 'gudev-1.0' found in 2.91.93 tar.gz distrib
Hi Marc, You probably need to install a libgudev-1.0-dev package, I suspect. Try apt-get build-dep gnome-pilot for starters. Matt -- Matt Davey What the world needs is more good readers, mcda...@mrao.cam.ac.uk not more good writers. -- Borges. On Mon, 2012-07-23 at 18:49 +0200, Marc BENVENISTE wrote: Hi, I ran onto the missing gudev-1.0 when trying to install gnome-pilot-2.91.93 on an Ubuntu 12.04 in a Gnome 3.4.1 session even though gir1.2-gudev-1.0 is installed and I have the ppa:gnome3-team/gnome3 repository in my software sources. Would appreciate your help cause I'm stuck in the ./configure step of the install. Thanks in advance. Some extra information: Code: sudo ldconfig -p | grep -i gudev libgudev-1.0.so.0 (libc6) = /usr/lib/i386-linux-gnu/libgudev-1.0.so.0 Code: sudo pkg-config --list-all | grep -i gudev gudev-sharp-1.0GUdev - GUdev Thanks a lot in advance, --Marc ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Transferring settings to a new device
You should be able to use the 'restore' feature in gnome-pilot. I don't have an install to hand, but as far as I remember you can right-click on the sync icon on your desktop bar and select restore... Alternatively, I believe that if you just attempt a sync, gnome-pilot will see an unrecognised ID and ask if you want to do a restore. If you have multiple palms known to gnome-pilot it'll let you choose one to restore. Personally, I'd backup your gnome-pilot directory first, just in case! Impressive you still have a functioning device. You've outlasted me by a few years at this stage :) Matt -- Matt Davey Never let a doctor examine you naked. mcda...@mrao.cam.ac.uk Make him put his clothes on first. On Tue, 2011-11-08 at 07:06 +0800, Oon-Ee Ng wrote: On Nov 7, 2011 11:25 PM, Daniel CLEMENT dcleme...@sfr.fr wrote: Hello, I've had the opportunity of replacing my aging Treo 680 with a new one, physically identical (though in better shape). I'd like to transfer, if possible, everything from the old one to the new one. What are my best options: 1) When pairing the new device, should I (could I) choose a different ID than the old one? (Syncing the old one won't be necessary afterward.) 2) After the pairing is done, is it correct / possible to restore a backup of the old device to the new one? My goal is to restore even the apps. this way, and I don't think it would be enough to sync for that. I do realize that some settings will need to be manually restored, but I'd like to automate the process as much as possible. TIA for advice - best regards, -- Daniel CLEMENT ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list I no longer use palm os but when I did nvbackup was the go-to app for these situations ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Current status (birthday supported?)
Hi, On Wed, 2011-05-11 at 08:11 +0800, Oon-Ee Ng wrote: Thanks Matt, A follow-up question, I'd assume that supporting birthdays is a matter of upgrading the vCard version supported (I'm assuming that's the internal format)? No, supporting birthdays is a matter of rewriting the address-conduit.c conduit to use the pilot-link Contacts API instead of the original Address API. The PalmOS 5 release introduced Contacts and changed the API, and database format, from the original AddressDB format. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Current status (birthday supported?)
Hi Oon-Ee, On Tue, May 17, 2011 at 5:16 PM, Matt Davey mcda...@mrao.cam.ac.uk wrote: Hi, On Wed, 2011-05-11 at 08:11 +0800, Oon-Ee Ng wrote: Thanks Matt, A follow-up question, I'd assume that supporting birthdays is a matter of upgrading the vCard version supported (I'm assuming that's the internal format)? No, supporting birthdays is a matter of rewriting the address-conduit.c conduit to use the pilot-link Contacts API instead of the original Address API. The PalmOS 5 release introduced Contacts and changed the API, and database format, from the original AddressDB format. Matt Ah, much more involved then. Nothing in gnome-pilot processes ContactsDB, then? Jpilot uses ContactsDB as well as AddressDB (selectable), I've taken a look at their structures, but have no idea on gnome-pilot internals. I suppose both projects are basically in maintenance mode due to PalmOS deprecation, though? That's pretty much right. I'm happy to integrate contributed code, but am unlikely to code this myself. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
gnome-pilot 2.91.92
gnome-pilot 2.91.92 'Ellie', 2011-03-20 gnome-pilot provides integration between gnome and palmos-based PDAs, including backup and synchronisation with evolution. This version of gnome-pilot requires gnome-3. It has been tested against gnome version 2.91.91. This version is largely complete, but has not been heavily tested, so there may well be problems still lurking. Note that there is no support for gnome-shell, but the panel-applet should work (ported from bonobo to dbus) in fallback mode. Significant changes and bug fixes since 2.32.0: - complete port to gtk3/gnome3, #590215 - update all libraries to major version 3, including conduits. Should allow parallel installs with gnome-2 if desired. - migrated applet to use libpanel4 (dbus instead of bonobo) #592604, #630725 - fix crash in configuration applet when configuring multiple Evolution conduits #644319 - fix crash in configuration applet caused by non-ASCII characters in owner name, introduced in migration to dbus in 2.32.0 - fix gob rules to support parallel builds, and todo conduit map-file patch #634874,634869. - Fix map-file path for todo conduit. #634869 - fix include problem when using a separate build directory. #634880 - Use dbus directly for device detection, instead of HAL. #593936 - Use gnome-doc-utils (Mario BlC3A4ttermann) Thanks to Matt McCutchen for several bug-fixes and improvements (#634874, #634869, #634880, #634873). Thanks to the translation team for their great work: - Daniel Mustieles (es) - Yinghua Wang (zh_CN) - Daniel Nylander (sv) - Andrea Zagli (it) - Kjartan Maraas (nb) - Antonio Fernandes C. Neto (pt_BR) - Inaki Larranaga (eu) ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: installing
Hi David, I wouldn't upgrade unless there's a reason to do so. The only significant changes between 2.0.17 and 2.32.0 (despite the jump in numbering) is to update most of the code to gnome3, and to merge the evolution conduits which evolution has removed. If your version of Evolution doesn't have the gnome-pilot conduits, then you will need v2.32.0. Matt p.s. there have not been any functional improvements to the evo conduits, sorry. So still no support for anniversaries, photos, etc. On Thu, 2011-02-24 at 19:22 -0500, aka.bugle wrote: Hello Pilotists, Should I update my gnome-pilot and gnome-pilot-conduits? Currently I'm using... Evolution 2.30.3 pilot-link 0.12.5 gnome-pilot 2.0.17-r1 gnome-pilot-conduits 2.0.17 I use Gentoo and emerged Evolution w/ the pda USE flag, so it would pull in pilot-link, gnome-pilot, and gnome-pilot conduits. it pulls in the versions above... the newest versions are in Gentoo portage ... gnome-pilot-2.32.0 and gnome-pilot-conduits-2.32.1 (marked ~86 for not stable rated yet) My other question is... Do I need to re-emerge Evolution after updating gnome-pilot and gnome-pilot conduits? (I'm guessing that its worth my while to update because of the address book conduit patches?) ((thanks go out to Matt and all for your amazing diligence w/ the bugs, and the seemingly long time it took for upstream to respond)) ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Entries not synced or with the wrong time
You should be able to build the more recent versions of gnome-pilot, such as gnome-pilot 2.32.0: http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.32/ However, these likely won't have fixed the conduit issues you mention. Those issues could, potentially, be due to recent changes in Evolution that have not been tracked by the conduits. What version of Evoution are you using? While you are debugging, it would be safest to set the sync mode to 'desktop overwrite PDA', so that at least you can trust the desktop :( Matt Matt Davey You will become one with the Universe next week, incurring mcda...@mrao.cam.ac.uk the wrath of all the Universe's old boyfriends. On Thu, 2011-01-20 at 08:52 +0100, Andreas Heinlein wrote: Hello, I have another problem with gnome-pilot sync'ing, and I hope you can help me again. Today I discovered on one of our palm devices that some appointments from evolution were missing on the handheld despite sync'ing multiple times. Even worse, on of the appointments existed on both sides, but with different times (6-8pm vs. 6:30-9pm). Even if these were both entered manually, they should have been treated as different appointments, I think. I then created another test appointment and sync'ed again, this entry was synced. I deleted it on the desktop and sync'ed once more, it was deleted from the palm, *and two, but not all of the other missing entries, were copied over*. I gave it another try and deleted the two xml files from ~/.evolution/calendar/local/system/*pilot*. This gave again duplicate entries on both sides, but all events were transferred this time. Only said entry with different times was overwritten, it now appeared twice with 6-8pm on both sides. I finally managed to clean up with deleting all duplicates on the desktop and doing a one-way sync to the palm. But the problem is: if there is the possibility that some appointments, possibly several weeks or even months in the future, are not sync'ed, the whole thing is next to useless. It was only by accident that I actually noticed this, it might as well have been a problem for the last weeks. Any idea how to deal with this? Is there any usable development version, or are these all only useful with GNOME 3? We are using 2.0.17 from Ubuntu 10.04 THanks, Andreas ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Building gnome-pilot
Hi Colin, It would be great if you had some time to contribute. As you can tell, gnome-pilot is a bit time-starved at the moment. Any time I've had to spend over the last while (year+) has been spent trying to keep it up to date with the gnome3/gtk3 changes (which have been considerable). I'm glad you figured things out despite the poor instructions. It might have been easier for you to start with the most recent .tar.gz release, as this includes a 'configure' script, rather than requiring the 'autogen.sh' step which is required when building from the checked out repository. Hope this helps. What features are you interested in working on? Matt DaveyMany hands make light work - but mcda...@mrao.cam.ac.uk Too many cooks spoil the broth. On Sat, 2011-01-22 at 20:10 -0500, Colin Williams wrote: Hey, I thought I'd try to do a bit of development work on gnome-pilot, as I have a palm Z22 and the current release has some features missing that I really needed. Anyway, I'm trying to get the development version and build it, and I've run into several problems. Some of these may be my inexperience with the tools, but I was hoping somebody could give me a hand. First, I tried to clone the git repository, using the command on the site, and I got the following: $ git clone git://git.gnome.org/gnome-pilot/ Initialized empty Git repository in /home/lackita/Documents/gnome-pilot/.git/ git.gnome.org[0: 209.132.180.173]: errno=Connection timed out fatal: unable to connect a socket (Connection timed out) Not a big deal, I just switched the protocol to http and it worked fine. My first question: Was there some configuration problem I needed to fix with git, is the command on the site incorrect, or is there a configuration error with the git repository? Second, I tried to build the code. To my surprise, I could not find a configure file. I also could not find an INSTALL file, which was my fallback. The README appears to be woefully out of date (it still had me fetching from the cvs repository at cvs.gnu-designs.com) but ended up suggesting autogen.sh which is what I needed to get moving. I think this was my own inexperience for the most part, but the README could be organized a little better. Colin ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: problems syncing
Hi Scott, A quick checklist: 1. Have you tried using pilot-xfer -p usb: -l? You might need to install the pilot-link package if you don't have pilot-xfer. 2. Before you installed the visor module (which you shouldn't need), did you use usb: as the device name, or ttyUSB0, or something else? 3. Have you looked at the gpilotd output while trying to sync? If not, then try this: run gpilotd from a terminal window before trying to configure gnome-pilot. Then run though the configuration and let us know what you see in the terminal window. Matt On Thu, 2010-10-21 at 01:24 -0700, Scott Warner wrote: Try as I may, I can't seem to get my Palm Tungsten E2 to sync. I am running Linux Mint 10 RC (won't sync in Mint 9 either). I have gnome-pilot applet 2.0.17. I added visor to my /etc/modules. I even did modprobe visor. But when I setup the device with the wizard, it never finds my palm. First time it told me I didn't have visor, but now it just does nothing at that point. Any other tips of how I can get it connected? Thanks, Scott ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
gnome-pilot-conduits 2.32.1 released
Gnome Pilot Conduits 2.32.1 has been released. Gnome Pilot lets you synchronize your gnome applications with your PalmOS(r) based devices. It can be used to back up your data, install files, or to synchronize your contacts, calendar, memos and tasks with Evolution. gnome-pilot-conduits contains a few conduits for gnome-pilot. Probably of most interest are the time-conduit, used to set the PDA time to the system time whenever you sync, and the memo_file conduit that can sync memos to a directory on your desktop. Only changes in this release: Include the translations in the release! #632025 Apologies to the translators for that slip-up, and thanks for recent translation updates: Matej Urbančič (sl), Marek Černocký (cz), Maxim V. Dziumanenko (uk), Jorge González (es) Release may be downloaded from: http://download.gnome.org/sources/gnome-pilot-conduits/2.32/ ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
gnome-pilot-conduits 2.32.0 released
(this time with download link!) Gnome Pilot Conduits 2.32.0 'Frankie' has been released. Gnome Pilot lets you synchronize your gnome applications with your PalmOS(r) based devices. It can be used to back up your data, install files, or to synchronize your contacts, calendar, memos and tasks with Evolution. gnome-pilot-conduits contains a few conduits for gnome-pilot. Probably of most interest are the time-conduit, used to set the PDA time to the system time whenever you sync, and the memo_file conduit that can sync memos to a directory on your desktop. Main changes in this release: Remove deprecated GTK API usage. Avoid use of libgnome and libgnomeui Migrate away from gnome-config to use of GKeyFiles under ~/.gnome-pilot Remove obsolete Mal conduit -- Avantgo RIP. Remove obsolete memo conduit (for Think Memo) You can download the release here: http://download.gnome.org/sources/gnome-pilot-conduits/2.32/ ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
gnome-pilot 2.32.0 released
gnome-pilot 2.32.0 'Frankie', 2010-09-26 Gnome Pilot lets you synchronize your gnome applications with your PalmOS(r) based devices. It can be used to back up your data, install files, or to synchronize your contacts, calendar, memos and tasks with Evolution. http://ftp.gnome.org/pub/GNOME/sources/gnome-pilot/2.32/gnome-pilot-2.32.0.tar.bz2 Significant code changes moving towards gnome-3: removal of libgnome, libgnomeui, removal of deprecated gtk API. Also, Evolution conduits have been migrated from evolution code base to gnome-pilot. Change versioning from 2.0.x to 2.32.x, to reflect significant code changes since 2.0.17. Many thanks to Halton Huo for work on many of the gnome-3 migration items below. Bug Fixes: - #594214: Remove deprecated GTK/glib symbols - #590215: Remove libgnome/libgnomeui dependency - #589501: convert applet to GtkBuilder - #597328: remove obsolete gpilotd-conduit-mgmt.h - #619315: Move evolution conduits from evo to gnome-pilot - #592604: Migrate from bonobo to dbus - #610782: support more versions of autoconf - #607142: Clean up of build system - #590225: remove gnome_help and gnome-open calls - #584894: pilot applet is not visible on the panel on gnome2.26 - #569481: Use stock gnome pda icon - #569193: remove obsolete SUSE-specific GNOMEPATH - #570724: avoid using deprecated gnome-i18n in favour or glib-i18n - #568404: only gpilotd binary needs to be linked with libhal - (Ubuntu bug #569601): no conduits loaded due to global variable namespace clash Thanks to the translations team, as ever. Matt Davey Did you hear that there's a group of South American Indians mcda...@mrao.cam.ac.uk that worship the number zero? Is nothing sacred? ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Any updates to fix syncing problems?
Hi Tom, On Fri, 2010-04-23 at 12:04 -0500, Tom Stone wrote: I have been hoping that some fixes might appear to the known syncing problems for USB and Bluetooth. I still cannot reliably sync using USB because of conflicts with modemmanager and networkmanager trashing the USBTTY devices. After extensive hunting, I found that the networkmanager people put it in the bug list but it isn't a high priority for them and it has languished. I still cannot use Bluetooth to sync with my Palm TX because the fix for Bluetooth crashing hasn't made it into the released code. It only is made available as a patch with no instructions on how to patch the code. I am not a linux guru and have not been able to figure out how to implement the patch. Can you point me to the specific patch you are talking about? Also, which version of linux are you using. I don't have much time to spend on gnome-pilot these days, but I might be able to help out. I know Palm OS devices are a dead end product line but there some of us that want to extend the life of these great devices because they work well. Like most people, I've moved on from Palm for day to day use, but I do have a fondness for them. The PalmV was near perfect for my use and it doesn't look like I'll ever have a phone with anything like its battery life! Matt Any help would be appreciated. With regards, Tom Stone ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt DaveyWhat do you call books that aren't cooked? mcda...@mrao.cam.ac.uk Rare. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: [OT] Compiling CryptoPadSlicer
On Sun, 2010-02-07 at 00:21 -0500, David A. Desrosiers wrote: On Sat, Feb 6, 2010 at 12:25 AM, Bruce Schultz bruce.schu...@gmail.com wrote: cryptops.c: In function ‘rw_record’: cryptops.c:119: error: too many arguments to function ‘dlp_ReadRecordByIndex’ cryptops.c: In function ‘main’: cryptops.c:292: error: too many arguments to function ‘pi_bind’ This app is 5 years old, and so much has changed in pilot-link from that time, that this would have to be ported over... buffers have changed, the underlying API has changed, even the way the Palm devices are connected to the socket has changed quite a bit. It might be easier to just rewrite it from the ground up, vs. trying to bring all of the legacy code to current. Another alternative is to download and compile pilot-pink 0.11.8 from http://gentoo.oregonstate.edu/distfiles/pilot-link-0.11.8.tar.bz2 and point cryptopadslicer at this version of p-l when building. I was able to get CryptoPadSlicer working on ubuntu 8.04 very easily (although had no files to test it on). You might have trouble compiling p-l 0.11.8 on more recent versions of linux. For Ubuntu 8.10, I had to edit two files: change iostream.h to iostream in ccexample.cc, and change open(filename, O_WRONLY | O_CREAT | O_TRUNC) to open(filename, O_WRONLY | O_CREAT | O_TRUNC, 0644) in pilot-schlep.c. pilot-xfer then crashed with a buffer overrun detected when starting up, but you might be able to run CryptoPadSlicer in offline mode. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt Davey Only when the tide goes out do you know who mcda...@mrao.cam.ac.uk is swimming naked. -- Warren Buffett ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: question about synching
Hi, I suspect the (evolution conduit) code does not support synching from anything other than a local addressbook. The other approach would be to sync the palm directly with google via syncml. This is not something I've tried or know anything about, but there's some info here: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=7cda5e4c32d5eec9hl=en Matt On Tue, 2010-02-02 at 07:50 -0800, Trevor Tolk wrote: I think I sent out a similar question recently. I use ubuntu 9.1, gnome pilot 2.15 (and I've tested with 2.17), and evolution. I setup evolution to sync to gmail. I have a Treo 700p. When I try to sync the palm to the gmail calendar and gmail contacts, it doesn't work. When I sync to the built-in evolution calendar and contacts, it works. Does anyone know how to make the palm sync properly with evolution when using gmail? -Original Message- From: jean j...@vlekkem.org Date: Tuesday, Feb 2, 2010 1:21 am Subject: question about synching To: gnome-pilot-l...@gnome.orgreply-to: The PalmOS\(tm\) integration package gnome-pilot-list@gnome.org Hi, Im using ii gnome-pilot2.0.17-0ubuntu2 A GNOME applet for management of your Palm P ii gnome-pilot-conduits 2.0.15-1.2 conduits for gnome-pilot ii libgnome-pilot22.0.17-0ubuntu2 Support libraries for gnome-pilot ii evolution 2.28.1-0ubuntu2 ETC on my ubuntu 9.10 system. I have a caldav calendar in evolultion, which turns up in the conduits list I select to sync my calender with on my palm treo 680. However calender items arent synched in any direction. When I use a normal calender everything works ok. (I have checked the 'copy calender for local operation' in evolution.) I have tried this on a fresh installed ubuntu 9.10 doesnt work either. I dont know if this is gpilot or evolution problem but I dont find anything about it on the net. Any ideas? regards, J ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt DaveyA hero is someone who can keep his mouth shut mcda...@mrao.cam.ac.uk when he is right. Yiddish Proverb. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Problems syncing calendar and addressbook with Treo 680
Hi Chris, On Mon, 2009-11-23 at 10:10 -0600, Chris Payne wrote: [...] Well, I did say I would help debug ;-) I followed those instructions (thanks for the link, I'm more of an rpm guy so those were helpful on this Ubuntu laptop). I commented the if statement as below: [...] and it indeed copied my Datebook/Calendar from the Treo to the proper calendar in Evolution as instructed. Presumably the Addressbook/Contacts will work as well now. Can you confirm the above the appropriate long term solution before I sync up the contacts and start syncing on a regular basis? Excellent! How very gratifying. Weird that your databases have that flag set. I have no idea why that should be. Your fix looks fine. I expect I'll make the same changes on trunk and it'll show up in the next release, whenever that may be. Matt Matt Davey It takes one drink to get me drunk, but I can't mcda...@mrao.cam.ac.uk remember if it's the 13th or 14th -- George Burns ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
gnome-pilot development
Work will start soon on the gnome-pilot source tree to migrate away from libgnome and several other deprecated modules, in line with gnome 3 development. This is likely to lead to a gnome-pilot 3.0 release sometime later in the year. If you are interested in helping, or keeping tabs on progress, we'll be posting updates to the gnome live page: http://live.gnome.org/GnomePilot Regards, Matt Matt DaveyOver-investment and over-speculation are often important; mcda...@mrao.cam.ac.uk but they would have far less serious results were they not conducted with borrowed money. -- Irving Fisher, 1933. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Syncing Question
Hi Josh, On Wed, 2009-07-22 at 13:54 -0400, Joshua Ronne Altemoos wrote: Hey Yall! Hey, I am using Ubuntu 9.04 and a Palm Centro (VZW 1.03) I got everything able to sync with Evolution, but for some reason it refuses to send birthdays, and anniversary. Yes, unfortunately birthdays, anniversaries and contact photos (at least) are not supported currently. There are a couple of bugs in Evolution contact handling that are blocking development of these features. The main one blocking me is: http://bugzilla.gnome.org/show_bug.cgi?id=556061 Also, is there a way to sync two calendars with a device? Evolution separates Birthdays and Anniversary into a separate calendar. If you have an up to date version of Evolution you can sync categories between Evo and Palm. It's not equivalent to separate calendars, of course, but you might be able to make some use of it. A feature request for gnome-pilot is to support mapping Evo calendars to palm categories, but that's not likely to happen any time soon unless someone steps up to implement it. Sorry not to be more encouraging. You can check out the jpilot package if you want more complete syncing without the Evolution integration. Matt Matt Davey Many candles can be kindled from one candle mcda...@mrao.cam.ac.uk without diminishing it. -- the Midrash ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: error message at gpilotd initialization
Hi Landis, On Mon, 2009-06-15 at 06:52 -0700, Landis McGauhey wrote: Nathan, thank you very much. Unfortunately, all of the USB nodes (there are several) available from the applet's drop-down list generate the same error message. By the way, the same is true of the USB nodes available from the drop-down list in JPilot. The error message you reported (Check your configuration, as you requested old-style usbserial 'ttyUSB' syncing...) is specific to gnome-pilot, so I presume you are talking about some other error message if you got the same error messages from JPilot? What version of pilot-link do you have installed? Can you confirm that you did try using usb: instead of /dev/ttyUSB0 or whatever? Can you try 'pilot-xfer -p usb: -l' from a terminal window? What happens? Matt Matt DaveyOver-investment and over-speculation are often important; mcda...@mrao.cam.ac.uk but they would have far less serious results were they not conducted with borrowed money. -- Irving Fisher, 1933. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: sync with palm tx excludes Location field from appointments
On Fri, 2009-03-20 at 20:39 -0400, Isaac Emesowum wrote: On Mon, 2009-03-16 at 09:53 +, Matt Davey wrote: [...] I'm attaching my modified Makefile. I've made very few changes from the version written by Paul Smith and Patrick Ohly. The main work was adding support for compiling gnome-pilot. It works by downloading everything it needs from svn. It's a little while since I used it. I had some trouble after Evo upgraded some of the libraries it depends on, as my running system (Ubuntu 8.04) had the older versions. So, I stuck with the Evo 2.24 branch. You can just blank that variable in the Makefile to go with trunk. I'm also attaching a version I hacked to use while offline, and just to avoid downloading unnecessary updates from svn. Matt Thanks very much Matt. Sorry for the late reply. The week days have been a little heavier than normal. The Makefile seems to fail while trying to build the gnome-pilot daemon. I also had to install pilot-link with a prefix of /opt/pl (The Makefile wanted it there). Here's some output from gnu make: Making all in gpilotd make[3]: Entering directory `/home/ice/dev/patch_work/evolutionsvn/obj/gnome-pilot/gpilotd' /usr/bin/gob2 --always-private-header -o ../libgpilotdCM -w ../../../gnome-pilot/gpilotd/gnome-pilot-conduit-management.gob ../../../gnome-pilot/gpilotd/gnome-pilot-conduit-management.gob: Error: Cannot open outfile: ../libgpilotdCM/gnome-pilot-conduit-management.c Hi Isaac, Looks like my fix for a different bug broke the ability of gnome-pilot to use separate build and source directories (as required by the evo-from-source makefiles). It's not generating certain source files in the right place. I'll try and fix this asap, but as a workaround, try the following: 1. cd into the gnome-pilot source directory 2. do 'make distclean; autogen.sh; make; make distclean;' 3. then retry your evolution build Matt Matt DaveyNot everything that counts can be counted, and not mcda...@mrao.cam.ac.uk everything that can be counted counts. - Einstein. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: sync with palm tx excludes Location field from appointments
On Sun, 2009-03-15 at 23:00 -0400, Isaac Emesowum wrote: On Sun, 2009-03-15 at 22:36 +, Matt Davey wrote: Isaac, Looks like you're heading, and being pointed, in the right direction. You may want to compile Evolution from source. I found it helpful to use the Makefile contributed by Patrick Ohly: http://mad-scientist.us/Makefile to get started. You'll have to edit it to include gnome-pilot (let me know if you'd like me to send you my edits) If you can, keep your changes limited to the Evolution conduits code (e.g. adding a new conduit but not requiring any changes to evolution or evolution-data-server components). Otherwise it is likely to take longer to get commit approval... Feel free to post patches to this list and I'll certainly help review and test. There are probably a few other lurkers might help out too. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Ahh, I see. From what I can tell, the difference between the two interfaces is simply a few extra fields in the pi-calendar.h version. From looking at the Evolution calendar conduit, it shouldn't be too hard to port the existing code to the new interface and replace the used Struct. Matt, I've grabbed Evolutions source from the Ubuntu Intrepid repository. I used apt-get source evolution and apt-get build-dep evolution. However, I should probably be using the latest version of Evolution from svn. Yes, please send me your edits as they will save me some time. Isaac, Just in case you hadn't spotted, the existing conduit code is required to support devices running older versions of PalmOS. The current devices have a compatibility layer that maps old fields to the new databases, allowing us to use a single conduit for all devices. When you add support for the new calendar database, you will have to ensure the old code continues to work. The simplest thing to do is to create a new conduit that registers for the new database, leaving the old conduit as is. If there is code you can share, or a smart way of using a single conduit, great, but I don't think that is trivial. I'm attaching my modified Makefile. I've made very few changes from the version written by Paul Smith and Patrick Ohly. The main work was adding support for compiling gnome-pilot. It works by downloading everything it needs from svn. It's a little while since I used it. I had some trouble after Evo upgraded some of the libraries it depends on, as my running system (Ubuntu 8.04) had the older versions. So, I stuck with the Evo 2.24 branch. You can just blank that variable in the Makefile to go with trunk. I'm also attaching a version I hacked to use while offline, and just to avoid downloading unnecessary updates from svn. Matt Matt Davey The Bermuda Triangle: Myth Or Fiction? mcda...@mrao.cam.ac.uk #!/usr/bin/make -f # # Build (debuggable) Evo from SVN # Run make help for some help, or see the comments below. # # Requires GNU make 3.80 or better. # # Author: Paul Smith psm...@gnu.org # Version: 2.12 # Date: 29 May 2008 # # -- # Copyright (C) 2007, 2008 Paul Smith # This Makefile is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the Free # Software Foundation; either version 3 of the License, or (at your option) # any later version. # # You should have a copy of the GNU General Public License on your system. # If not, see http://www.gnu.org/licenses/. # -- # # You can look here for more/alternate information: # http://www.go-evolution.org/Compiling_Evolution_from_SVN # # Enhancements/suggestions provided by: # Patrick Ohly patrick.o...@gmx.de # == # By default we build for Ubuntu (I'm testing on Ubuntu 8.04). # # If you want to build for another distro, see if it's listed in the DISTROS # variable (currently only Debian Ubuntu releases are listed) and, if so, # change DISTRO to your distro. You can do this in local.mk to avoid # changing this makefile. # # If your distro is not supported, you can set distro to empty and the check # for prerequisite packages will be skipped. Of course, if you don't have all # the proper development packages installed the build will fail. # == # v User Customization v # Feel free to change these if you like # What branch to work with. If not set, we use the trunk. Close to a # release, however, you might prefer to use the pending release. # E.g.: # BRANCH := 2.20 BRANCH := 2.24 # Where to install Evo. DO NOT use /usr here for any system controlled
Re: sync with palm tx excludes Location field from appointments
On Sun, Mar 15, 2009 at 6:03 PM, Nicholas Piper n...@nickpiper.co.uk wrote: You will need one that uses CalendarDB-PDat with the (new, unreleased) http://cvs.pilot-link.org/include/pi-calendar.h?view=log interface. That's my fault... I'm a couple of weeks delinquent on pushing out a new p-l release. Personal life had to take priority this month, unfortunately. I'll get it out soon... Isaac, Looks like you're heading, and being pointed, in the right direction. You may want to compile Evolution from source. I found it helpful to use the Makefile contributed by Patrick Ohly: http://mad-scientist.us/Makefile to get started. You'll have to edit it to include gnome-pilot (let me know if you'd like me to send you my edits) If you can, keep your changes limited to the Evolution conduits code (e.g. adding a new conduit but not requiring any changes to evolution or evolution-data-server components). Otherwise it is likely to take longer to get commit approval... Feel free to post patches to this list and I'll certainly help review and test. There are probably a few other lurkers might help out too. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot may be removed from default Ubuntu install
Hi Daniel, On Wed, 2009-03-04 at 17:12 +0100, Daniel CLEMENT wrote: Hello, On Tuesday 03 March 2009, 17:06 +, Matt Davey wrote: Ubuntu users: a bug/issue has been logged suggesting that gnome-pilot be removed from the default Ubuntu installation. If you want to register your opinion, the issue is logged here: https://bugs.launchpad.net/bugs/334446 with a forum discussion here: http://ubuntuforums.org/showthread.php?t=1080350 I think I'll post a comment there. IMHO when I tried Ubuntu some 2 yrs ago, the Gnome-Pilot was one of these things that made this distro feel so user-friendly to me. I appreciate this software, which integrates nicely with Evolution, and the support we get from this forum. Thanks for your words of support! [...] One comment reads: From the launchpad page, it appears development upstream has stopped. I don't quite understand. [...] The poster is unaware of the 2.0.16 and 2.0.17 gnome-pilot releases. I guess Ubuntu haven't picked them up. I think there was another post correcting this error. However, reading the various comments, I found some of them less than friendly... If I were a developer, I wouldn't have found this pleasant to read. That's why I posted my previous message. There were very few voices coming from owners of Palm devices. [...] Palm certainly won't drop _any_ form of sync operation. I see they have a new device under webOS about to be released. OTTH, some users manage to install an open source system on their treo/palm. But what will Gnome-Pilot become in the middle of all this? This is an interesting question. My own guess is that it is most likely that a project like opensync will support the new palm devices: http://en.opensuse.org/OpenSync/SyncML-OBEX-Client gnome-pilot is deeply embedded with pilot-link which in turn in inherently based on the PalmOS Desktop Link Protocol. We don't yet know what webOS syncing will look like, but my guess is nothing like DLP and pilot-link/gnome-pilot will become obsolete. [...] I definitely hope Gnome-Pilot will at least remain _available_ to Ubuntu users, and that the Ubuntu and Gnome-Pilot teams will continue to communicate. I'd be confident that gnome-pilot will remain available for several years to come. Matt Matt Davey Socrates said man is never free, but Socrates mcda...@mrao.cam.ac.uk never windsurfed. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: I seem to be getting two copies of gpilotd started (xubuntu 8.10)
Hi Chris, On Tue, 2009-02-03 at 17:37 +, Chris G wrote: I'm running gpilotd to synchronize a Treo 680 with Evolution under xubuntu 8.10. I installed the gpilot package in the normal way using synaptic and it works OK, the only problem was that no applet icon appeared in the xfce panel. So I installed XfApplet which allows gnome applets to be put in the Xfce panel and installed gpilot-control-applet with it. That worked too, I can now see the gpilot daemon applet in the xfce panel. So far so great. However :-), when I start the system up now an error box pops up saying Cannot run druid if PDAs or devices already configure. This sounds as if it's saying I'm trying to start two gpilotd processes, how can I prevent this? There had to be a 'however'! That error should only occur if you run gpilotd-control-applet with the --druid option after configuring gnome-pilot. When you have the error window on the screen, what output do you get from running ps auxww | grep gpilotd from a terminal window? Matt Matt Davey Madam, I had a wonderful evening, but this mcda...@mrao.cam.ac.uk wasn't it. -- Groucho Marx. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Treo 680 won't seem to take Evolution data
On Thu, 2009-01-22 at 13:12 -0500, ray field wrote: I recently installed Intrepid and for the most part things have gone pretty well between gnome-Pilot, my 680, and Evolution -- in fact much more nicely than they ever went with my Treo and Suse 9(.1?) one very annoying problem, however: I have been able to move appointments tasks and (and everything else) to Evolution from the Treo -- however I can't seem to get the Treo to accept appointments I've made in Evo's calendar. under gnome-pilot I have Conduit Actions Action: Synchronize One time action: None Conduit Settings Sync with Personal and Sync Private Records and Split Multi-Day Events are both checked one thing I've noticed is after an (unsuccessful) sync, the Conduit Settings are reset/blanked out. Hmmm. Nothing springing to mind here. For the record, what version of evolution/evolution-data-server/pilot-link(libpisock)/gnome-pilot are you running? Also, can you run gpilotd in a terminal window and then sync? What console output do you get? To run gpilotd in a terminal window: 1. remove pilot applet from taskbar 2. killall gpilotd 3. /usr/bin/gpilotd Matt Davey The journey of a thousand miles begins with mcda...@mrao.cam.ac.uk a broken fan belt and a leaky tire. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Sync Treo 650 via Bluetooth on Ubuntu 8.10
On Sat, 2009-01-03 at 13:54 -0800, Toast wrote: So I can sync Treo with gnome-pilot via USB, and can access Treo with pilot-link via Bluetooth... can't quite get gnome-pilot to sync via Bluetooth. I've tried all (perhaps) of the guides and have searched this lists' archives - to no avail. Is this even possible? any success stories? hints? blatent help? Hi Dan, Rereading your posts, I see that you are using gnome-pilot 2.0.15. Bluetooth support is in gnome-pilot 2.0.16, and the newly released gnome-pilot 2.0.17 fixes a bug that prevented device detection working with recent HAL releases. Note that there is a pilot-link bug that means gnome-pilot will crash after a bluetooth sync. The patch for that is here: http://bugs.pilot-link.org/file_download.php?file_id=681type=bug and should be fixed when pilot-link 0.12.4 is released. Matt Matt Davey A woman drove me to drink and I didn't even have the mcda...@mrao.cam.ac.uk decency to thank her. - W.C. Fields ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
RE: gnome-pilot 2.0.17 released
On Thu, 2009-01-08 at 05:01 -0800, Reitsma, Rene - COB wrote: Matt, Thanks for the gnome-pilot 2.0.17 announcement. I was hoping it would fix my long-term HAL/Z22 problem and immediately tried installing it. I run Fedora 9 (2.6.27.9-73.fc9.i686) and the gnome-pilot 'configure script' complains about pi-version.h lacking (I yum erased gnome-pilot 2.0.16 before trying the install) I googled this a bit and saw some posts saying that pi-version.h is part of pilot-link. However, 'yum info pilot-link' says that I have pilot link installed just fine (version 0.12.3 release16.fc9). Can you shed light on this? Sure. pi-version.h will be part of the development package for pilot-link. On fedora, this means installing 'pilot-link-devel' corresponding to your pilot-link package. See, for example: http://rpmfind.net//linux/RPM/fedora/9/i386/pilot-link-devel-0.12.3-13.fc9.i386.html There will probably be some other packages you need to install -devel versions for before you can build from source. Matt RR -Original Message- From: gnome-pilot-list-boun...@gnome.org [mailto:gnome-pilot-list-boun...@gnome.org] On Behalf Of mcda...@mrao.cam.ac.uk Sent: Thursday, January 08, 2009 1:10 AM To: The PalmOS(tm) integration package; gnome-annou...@gnome.org Subject: gnome-pilot 2.0.17 released Gnome Pilot 2.0.17 'Pippi' has been released. Gnome Pilot lets you synchronize your gnome applications with your PalmOS(r) based devices. It can be used to back up your data, install files, or to synchronize your contacts, calendar, memos and tasks with Evolution. http://download.gnome.org/sources/gnome-pilot/2.0/gnome-pilot-2.0.17.tar .gz http://download.gnome.org/sources/gnome-pilot-conduits/2.0/gnome-pilot-c onduits -2.0.17.tar.gz Bug Fixes: - #484509: Avoid obsolete HAL info.bus API. Use hal pda.platform property instead (keep info.bus for backwards compatibility). With thanks to Frederic Crozat. - #528701: remove unused applet desktop file - #508262: fix long-standing build-order bug by moving libgpilotdcm code to gpilotd/ directory. - #491921: stray slash breaks rpath for libraries Updated translations: ar (Djihed Afifi) ca (Gil Forcada) el (Simos Xenitellis) en_GB (Philip Withnall) fr (Stephane Raimbault) it (Luca Ferretti) fi (Ilkka Tuohela) nb (Kjartan Maraas) ne (Pawan Chitrakar) oc (Yannig Marchegay) pt_BR (Jonh Wendell) sv (Daniel Nylander) vi (Clytie Siddall) ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt DaveyWhat's the difference between a brassiere and a brazier? mcda...@mrao.cam.ac.uk Just try warming your hands on a brassiere. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: bluetooth sync with treo 650
On Sat, 2009-01-03 at 11:22 -0800, Toast wrote: Hey thanks! this worked: pilot-xfer -l -p bt: - I didn't know that the port could, simply, be called bt: Now, has anyone got the 650 to work via BT with gnome-pilot??? ...I guess that's another list... (crossposting to gnome-pilot-list) gnome-pilot 2.0.17 will support bluetooth sync (it's been in the source tree nearly 12 months). With any luck I'll get this released this week. I just have a little bit of tidying up to do. Keep an eye on gnome-pilot-list for a release announcement. Matt thanks again. ___ Public archival of this list without permission is prohibited. http://lists.pilot-link.org/mailman/listinfo/pilot-link-general Matt DaveyWhat do you call books that aren't cooked? mcda...@mrao.cam.ac.uk Rare. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
status of the addressbook conduit
I just thought I'd post a quick message about my work on the addressbook conduit. If you currently find the contacts/addressbook conduit unreliable, buggy or just incomplete, read on. There are two relevant patches at present: * category support for addressbook conduit, and fixing the first-name/last-name split bug. This patch is attached to bug #201167 (http://bugzilla.gnome.org/show_bug.cgi?id=201167) and has been awaiting review since October 12th. * various changes to fix several data loss and data corruption bugs in the addressbook conduit. I have for a long time had problems where phone/email fields would lose data, get reordered, get duplicated, etc., and the conduit was generally unreliable. I have, I believe, fixed the majority of these bugs and I submitted a bug report and patch to the Evolution bugzilla (bug #556061 http://bugzilla.gnome.org/show_bug.cgi?id=556061) on October 12th, but it has not yet been accepted. The reason is that there is a possibility of side-effects outside the addressbook conduit (these could certainly be fixed if they arose). If you need these bugs fixed, please feel free to comment on the above bug reports to let the Evo maintainers know that these bugs are real and are affecting users. Thanks, Matt Matt Davey Madam, I had a wonderful evening, but this mcda...@mrao.cam.ac.uk wasn't it. -- Groucho Marx. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot config question
Hi Simon, [note to self: it's time to release 2.0.17] On Tue, 2008-12-02 at 12:03 -0800, Simon Roberts wrote: Hi all, I'm trying to use my palm device (Sony Clie, Palm OS 4.1) with the gnome pilot applet to sync with Evolution under Open SuSE 11.0. I've done this before with OpenSuSE 10.3, but since the upgrade, it's not working. I find that the device works just fine with the jpilot application. Pressing hotsync causes /dev/ttyUSB1 to show up, and that application syncs just fine. However, when I add the gnome pilot applet to my toolbar and go through the setup, it gets to the part where it's supposed to do that first sync (yes, I've used this with sync sofware before) and the thing just hangs. Your issue is almost certainly due to changes in hal that occurred after the release of gnome-pilot 2.0.15. Take a look at this recent posting for more info and a patch: http://mail.gnome.org/archives/gnome-pilot-list/2008-November/msg1.html You should raise a bug against OpenSuse. By the way, a workaround is: 1. kill any running gpilotd 2. stop hald 3. configure your palm using 'gpilotd-control-applet' 4. restart hald Matt Matt DaveyPeople demand freedom of speech as a compensation for [EMAIL PROTECTED] the freedom of thought which they seldom use. -- -Soren Kierkegaard ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: anyone fancy testing this address-conduit patch?
Hi Tom, On Mon, 2008-11-17 at 22:42 +0100, Tom Billiet wrote: Hi Matt, It took me a long time to get it tested. First because of a lack of time, and secondly because I took my z22 for a ride in the washing machine. It takes an awful long time to get the water out of the touchscreen, but magically everything seems to be working, and it still had all my data. Actually I must say I was quite surprised it survived it :-) That is good news indeed. Nice surprise! Anyway, I got now to testing it. I applied your patch against the svn version of evolution and e-d-s from today, and it compiles fine (on archlinux). It also tried 1. and 2. you mentioned, and it seems to be working ok. I'm not sure how to test the other points. So the basic testing I've done looks fine. It's good to see some bugs to get solved. Many thanks for the testing. Did you sync with a previously synced device+addressbook? I suspect there's a possibility that all (or many) addresses could get duplicated on first syncing with the new logic, because the desktop will now package an address in a slightly different way (basically, I've aimed to avoid re-ordering fields on the pilot as much as possible). I'm having a bit of a job persuading the Evolution maintainers to commit the e-d-s part of the patch (see bug 556061: http://bugzilla.gnome.org/show_bug.cgi?id=556061 ) as my fix for the reordering problems could change behaviour that is being relied upon by other workarounds. Unfortunately, without the changes on the e-d-s side I can't fix the pilot bugs. Hopefully it's just a case of getting consensus that a) there are bad bugs b) they need to be solved at the e-d-s layer and not worked around elsewhere and c) if we miss any cases elsewhere we can address them as they are identified. Part of the problem is the lack (to my knowledge) of any regression test suite for evolution. It's a complex beast, and it's all too easy to introduce bugs when trying to fix other ones. Thanks again, Tom, Matt Btw: my email address has changed, so do not try to contact me anymore on my old address, I won't receive your mails. Kind regards, Tom - Original Message - From: Matt Davey Time: 05-10-08 23:52 Dear code monkeys, I'm attaching two patches, one for evolution-data-server and one for evolution. Together, they seem to fix some pretty bad bugs in the address conduit. I would appreciate it if anyone out there was willing to test these patches (Tom, Nathan?). The diffs are against Evolution branch 2.24 as the trunk would require me to upgrade my glib and a bunch of other stuff, or build from gargnome, neither of which I fancy just now. 2.24 was only branched a couple of weeks ago, so it is pretty up to date. I haven't yet attempted any support for the new Contact fields. This patch is just to fix existing addressbook bugs. The sync logic, particularly for the phone and email fields has changed considerably. Bugs I've tried to fix: 1. The 'first-name / family-name' split on the palm was not respected when writing to the desktop. It went via 'full_name'. See bug #269342 for some more info. (aside: IMO Evo full_name munging is far too fragile to be worth using and I wish they'd get rid of it. It's never going to reliably separate first/last names when challenged by, say Mary Anne Bloggs and John Mc Neill) 2. If you erased a phone field on the Palm, it wouldn't be erased on the desktop. 3. The 'OTHER' phone fields were broken in various ways. This is actually already fixed on the 2.24 branch (and trunk) since revision 9380 (see bug #547223) 4. There were many ways for phone fields to be re-ordered. I've tried to avoid this wherever possible. 5. Evolution was careless about ordering of multiple email/phone entries in the vcard. For example, if you imported a 'vcard' with 3 emails, and then saved it immediately, you would find the 3 entries would be reversed. This sort of thing could upset the palm. 6. If you had an entry on both desktop and palm, and say you had three phone numbers labelled 'home' on the palm. Then that entry could be deleted if you changed the desktop record and synced again. I will probably have to break down the patch into a few components before submitting to the Evolution maintainers, but I'd appreciate it if anyone was able to do some testing or take a look over the changes in the meantime. Thanks, Matt Matt Davey I like to browse in occult bookshops if for no other reason than [EMAIL PROTECTED] to refresh my commitment to science. -- Heinz Pagels ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot
Re: Treo 680 sync with Ubuntu 8.10
Hi Keith, On Wed, 2008-11-05 at 12:01 +, Keith Burdon wrote: Hi I have recently upgarded to Ubuntu 8.10. I now find that I cannot sync my Treo 680 which did sync Ok in Ubuntu 8.04. If you check the list archives, you will see a post this week from David Liu with your exact problem: http://mail.gnome.org/archives/gnome-pilot-list/2008-November/msg0.html The fix requires a patch to the gnome-pilot package shipped by Ubuntu. I have added my comments to Ubuntu bug 282491: https://bugs.launchpad.net/ubuntu/+source/gnome-pilot/+bug/282491 I suggest Ubuntu users subscribe to that bug to be alerted when a patched package is available. A workaround is to stop hald, restart gnome-pilot, and then restart hald: In a terminal window: - sudo /etc/init.d/hal stop killall gpilotd /usr/bin/gpilotd sudo /etc/init.d/hal start Matt Matt DaveyMany hands make light work - but [EMAIL PROTECTED] Too many cooks spoil the broth. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Evolution with exchange
Hi Jamie, On Mon, 2008-10-06 at 11:17 +0100, Jamie Dow wrote: Matt others, I'm now back at my Fedora machine (at work) and I can't even try your suggestion. As soon as I set the conduits to the relevant Exchange calendar / addressbook / todos and then click on OK, when I open up the same conduit settings immediately afterwards the setting for which of the Evolution calendar/addressbook/todos to sync has gone blank. It just does not seem to want to accept the exchange settings. I wasn't aware of that bug, but I can reproduce it. The good news is that the blank field seems to be entirely cosmetic - the configuration change has in fact been made. If you close the config window and reopen it, you'll see the selected calendar correctly set. Matt I've tried changing the make available offline setting for each of these, and it makes no difference. I'm totally at a loss as to what to do here. It's very annoying. (Am trying to ditch windows, but if I can't sync my PDA with my work calendar and contacts, I'm going to be very much stuck with it.) Cheers for any advice. Jamie On Thu, 2008-10-02 at 21:05 +0100, Jamie Dow wrote: Many thanks, Matt. I'll give this a try. There aren't 2 PDA objects configured. But I'll try the one time action of copying the data to PDA. Hadn't thought of that. Best, Jamie -Original Message- From: Matt Davey [EMAIL PROTECTED] Reply-To: The PalmOS(tm) integration package gnome-pilot-list@gnome.org To: The PalmOS(tm) integration package gnome-pilot-list@gnome.org Subject: Re: Evolution with exchange Date: Thu, 02 Oct 2008 09:40:38 +0100 Hi Jamie, On Wed, 2008-10-01 at 22:00 +0100, Jamie Dow wrote: Hi, I'm using Evolution as my PIM client at work, and instead of (what most other users have) Outlook. [...] My question is whether it is possible to get the exchange conduits for Calendar, Address, Task, etc. to point to the exchange based calendar, addressbook, and so on. [...] When I configure the conduits to point to the correct calendar / addressbook / etc., I sync and - hey presto! - the conduits have magically changed to point to a different calendar / address book.. Anyone know why this is happening, and whether it is possible to sync successfully with the exchange data that evolution-exchange enables me to access via evolution? I have never used Evolution with Exchange, but I'm surprised by the symptoms you describe. Any chance you have two PDA objects configured, and you changed the conduit settings on the wrong one? If that's not the case, it sounds like a bug in the conduit. It might be worth trying a one time action of copy to PDA to see if that works (assuming you don't mind wiping the calendar/addressbook data on your PDA. Matt Matt Davey By doing just a little every day, I can gradually let the [EMAIL PROTECTED] task completely overwhelm me. -- Ashleigh Brilliant ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt Davey The vast majority of numbers are unused. [EMAIL PROTECTED] -- Detroit Free Press, August 11, 1999. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Starting gnome-pilot minimised to tray / getting usb: sync to work first time
On Fri, 2008-10-03 at 23:04 +0100, Jamie Dow wrote: OK. Thanks, Matt, that's helpful. Is there an equivalent way of adding *that* applet when in KDE. When I choose add Applet to the panel, it offers me a list of KDE native applets, but not the pilot applet you mention. It's not obvious how to add it .. No, the 'panel' is specific to gnome. for now, I'm going with a little script in my Autostart folder to start the daemon. But I'm liking the panel option, if there's a way of getting it to work. In kde you should just run gpilotd from a startup script, as you suggest. Matt Matt Davey The mind is not a vessel to be filled [EMAIL PROTECTED] but a fire to be kindled. -- Plutarch ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
anyone fancy testing this address-conduit patch?
Dear code monkeys,
I'm attaching two patches, one for evolution-data-server and one for
evolution. Together, they seem to fix some pretty bad bugs in the
address conduit. I would appreciate it if anyone out there was willing
to test these patches (Tom, Nathan?).
The diffs are against Evolution branch 2.24 as the trunk would require
me to upgrade my glib and a bunch of other stuff, or build from
gargnome, neither of which I fancy just now. 2.24 was only branched a
couple of weeks ago, so it is pretty up to date.
I haven't yet attempted any support for the new Contact fields. This
patch is just to fix existing addressbook bugs. The sync logic,
particularly for the phone and email fields has changed considerably.
Bugs I've tried to fix:
1. The 'first-name / family-name' split on the palm was not
respected when writing to the desktop. It went via 'full_name'.
See bug #269342 for some more info. (aside: IMO Evo full_name
munging is far too fragile to be worth using and I wish they'd
get rid of it. It's never going to reliably separate first/last
names when challenged by, say Mary Anne Bloggs and John Mc
Neill)
2. If you erased a phone field on the Palm, it wouldn't be erased
on the desktop.
3. The 'OTHER' phone fields were broken in various ways. This is
actually already fixed on the 2.24 branch (and trunk) since
revision 9380 (see bug #547223)
4. There were many ways for phone fields to be re-ordered. I've
tried to avoid this wherever possible.
5. Evolution was careless about ordering of multiple email/phone
entries in the vcard. For example, if you imported a 'vcard'
with 3 emails, and then saved it immediately, you would find the
3 entries would be reversed. This sort of thing could upset the
palm.
6. If you had an entry on both desktop and palm, and say you had
three phone numbers labelled 'home' on the palm. Then that
entry could be deleted if you changed the desktop record and
synced again.
I will probably have to break down the patch into a few components
before submitting to the Evolution maintainers, but I'd appreciate it if
anyone was able to do some testing or take a look over the changes in
the meantime.
Thanks,
Matt
Matt Davey I like to browse in occult bookshops if for no other reason than
[EMAIL PROTECTED] to refresh my commitment to science. -- Heinz Pagels
Index: addressbook/gui/contact-editor/e-contact-editor.c
===
--- addressbook/gui/contact-editor/e-contact-editor.c (revision 36550)
+++ addressbook/gui/contact-editor/e-contact-editor.c (working copy)
@@ -1078,7 +1078,7 @@
for (l = attr_list; l; l = g_list_next (l)) {
EVCardAttribute *attr = l-data;
- e_vcard_add_attribute (vcard, e_vcard_attribute_copy (attr));
+ e_vcard_append_attribute (vcard, e_vcard_attribute_copy (attr));
}
}
Index: addressbook/conduit/address-conduit.c
===
--- addressbook/conduit/address-conduit.c (revision 36550)
+++ addressbook/conduit/address-conduit.c (working copy)
@@ -64,6 +64,12 @@
#define WARN g_warning
#define INFO g_message
+/* note: evolution GUI contact editor does not preserve EVOLUTION_PILOT_SLOT_PARAM values.
+ * that's okay, though, because we only need to remember these values if the
+ * desktop record has not changed since last sync.
+ */
+#define EVOLUTION_PILOT_SLOT_PARAM X-EVOLUTION-PILOT-SLOT
+
enum {
LABEL_WORK,
LABEL_HOME,
@@ -660,90 +666,112 @@
return FALSE;
}
-static gboolean
-is_syncable (EAddrConduitContext *ctxt, EAddrLocalRecord *local)
+static EVCardAttributeParam *
+get_pilot_slot_param (EVCardAttribute *attr)
{
- EContactField next_mail, next_home, next_work, next_fax;
- EContactField next_other, next_main, next_pager, next_mobile;
- gboolean syncable = TRUE;
- int i, l = 0;
+EVCardAttributeParam *param = NULL;
+GList*param_list;
+GList*l;
- /* See if there are fields we can't sync or not in priority order */
- get_next_init (next_mail, next_home, next_work, next_fax,
- next_other, next_main, next_pager, next_mobile);
+param_list = e_vcard_attribute_get_params (attr);
- for (i = entryPhone1; i = entryPhone5 syncable; i++) {
- int phonelabel = local-addr-phoneLabel[i - entryPhone1];
- const char *phone_str = local-addr-entry[i];
- gboolean empty = !(phone_str *phone_str);
+for (l = param_list; l; l = g_list_next (l)) {
+const gchar *str;
- if (empty)
- continue;
+param = l-data;
- for ( ; priority_label[l] != -1; l++)
- if (phonelabel == priority_label[l])
-break;
+str = e_vcard_attribute_param_get_name (param);
+if (!g_ascii_strcasecmp (str
Re: Starting gnome-pilot minimised to tray / getting usb: sync to work first time
Hi Jamie,
On Thu, 2008-10-02 at 21:09 +0100, Jamie Dow wrote:
OK, I think that my original question was confused, and you've shed
light on what was really required.
I don't think I shed quite enough light yet :)
I've found that with syncing via usb: when I initially try and sync,
it doesn't work. Then if I run the configuration applet, the sync does
work.
I'm guessing that the key thing that's making the difference is that
running the applet ALSO serves to start the daemon.
So, what in fact I need to do is get the daemon to be initiated on
startup. And I assume that I can do that just by sticking a script
into my autostart folder with the command gpilotd.
There are three components to gnome-pilot:
o gpilotd: the daemon
o configuration applet: the GUI for changing settings. This can
be launched from Evolution under Edit-Synchronization Options...
o panel applet: This shows status on the panel when you are
synchronizing and a progress window. Adding this to the panel,
as described in my last mail, should mean gpilotd starts when
you start your gnome-session.
Matt
Cheers
Jamie
-Original Message-
From: Matt Davey [EMAIL PROTECTED]
Reply-To: The PalmOS(tm) integration package
gnome-pilot-list@gnome.org
To: The PalmOS(tm) integration package gnome-pilot-list@gnome.org
Subject: Re: Starting gnome-pilot minimised to tray
Date: Thu, 02 Oct 2008 09:43:40 +0100
Hi again,
On Wed, 2008-10-01 at 22:03 +0100, Jamie Dow wrote:
Hi,
Second question: is it possible (what would be the options from the
command line) to start the gnome-pilot (gpilotd-control-applet)
minimised to the system tray?
This relates in teh first instance to my Kubuntu 8.04 (KDE 3.9)
system. But I'd also be interested in how it might work for my work
Fedora 9 (Gnome) system.
On gnome, what you should do is add the gnome-pilot 'applet' to the
panel (right click on a blank area, select 'add to panel...' and search
for 'pilot applet' which should have a sync icon). This will then be
added to your gnome session and will start automatically. You can click
on the icon to launch the configuration applet
('gpilotd-control-applet'). The communication daemon (gpilotd) runs in
the background.
Matt
Matt DaveyDid you hear about the new corduroy pillow?
[EMAIL PROTECTED] It's making headlines all over town.
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Matt Davey You can't have everything. Where would you put it?
[EMAIL PROTECTED] -- Steve Wright
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Evolution with exchange
Hi Jamie, On Wed, 2008-10-01 at 22:00 +0100, Jamie Dow wrote: Hi, I'm using Evolution as my PIM client at work, and instead of (what most other users have) Outlook. [...] My question is whether it is possible to get the exchange conduits for Calendar, Address, Task, etc. to point to the exchange based calendar, addressbook, and so on. [...] When I configure the conduits to point to the correct calendar / addressbook / etc., I sync and - hey presto! - the conduits have magically changed to point to a different calendar / address book.. Anyone know why this is happening, and whether it is possible to sync successfully with the exchange data that evolution-exchange enables me to access via evolution? I have never used Evolution with Exchange, but I'm surprised by the symptoms you describe. Any chance you have two PDA objects configured, and you changed the conduit settings on the wrong one? If that's not the case, it sounds like a bug in the conduit. It might be worth trying a one time action of copy to PDA to see if that works (assuming you don't mind wiping the calendar/addressbook data on your PDA. Matt Matt Davey By doing just a little every day, I can gradually let the [EMAIL PROTECTED] task completely overwhelm me. -- Ashleigh Brilliant ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
admin: apologies if you're trying to contact the list owner
The gnome-pilot-list-owner address is currently receiving a huge volume of mail. This is because spammers have chosen to use gnome-pilot-list and gnome-pilot-list-owner as their forged from address for outgoing spam. On Friday we received over 1,000 messages. Apologies if you have been trying to contact the list-owner address, as genuine messages are likely to get lost in the noise just at the moment. Please feel free to cc me at this address if you have been ignored. Regards, Matt Matt DaveyTwo cannibals eating a clown. One says to the other [EMAIL PROTECTED] Does this taste funny to you? ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Installing gnome-pilot 2.0.16
Hi again, answers inline. On Fri, 2008-09-12 at 17:04 +0200, Daniel Clément wrote: Hello Matt, Thank you for your help, Le jeudi 11 septembre 2008 à 14:26 +0100, Matt Davey a écrit : Hi Daniel, [...] I suggest you take a look at the recent discussion on this list. The thread started here: http://mail.gnome.org/archives/gnome-pilot-list/2008-August/msg00011.html Regards, Matt Matt Davey Diplomacy is letting them have it your way. [EMAIL PROTECTED] Indeed this thread made things a little clearer (I only searched for gnome-pilot 2.0.16 in the archive). It's true that my Evolution-related conduits were gone. Now I can see how to restore them. (Strangely, they are here under /usr/share/gnome-pilot-conduits even though the gnome-pilot-conduits 2.0.15 package is suppressed...) The evolution conduits are part of the evolution distribution, not gnome-pilot-conduits. Then, your advice was to search for a the GNOME_PilotApplet.server file. I was unable to locate it under /lib/bonobo/servers/ (I don't have a /lib/bonobo/ directory, perhaps because I have suppressed the original gnome-pilot package). I presume it was removed when you removed the gnome-pilot 2.0.15 package? But I do have one such file under /usr/local/lib/bonobo/servers, along with a GNOME_Pilot_Daemon.server. There I must confess my poor knowledge... what should I do with them? I don't know how to get the gnome-pilot daemon started, neither to access its settings from the system menu! On my ubuntu install, I have a file /etc/bonobo-activation/bonobo-activation-config.xml that lists the directories in which the system searches for .server files. Add /usr/local/lib/bonobo/servers to the list. Shame on my ignorance... Not at all! Matt Matt Davey I stopped believing in Santa Claus when I was six. [EMAIL PROTECTED] Mother took me to see him in a department store and he asked for my autograph. -- Shirley Temple Black ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Installing gnome-pilot 2.0.16
Hi Daniel, On Wed, 2008-09-10 at 17:17 +0200, Daniel Clément wrote: Dear list members, I'm having trouble installing gnome-pilot 2.0.16, compiling it from source. (Ubuntu Hardy) I think I have all the required packages (with much trial and error; I'm not an expert at compiling) but... - after installing (along with the 2.0.16 conduits), my gnome-pilot about box still says 2.0.15. Yet, there was a bluetooth option in the conduits... not working. So I thought I should have suppressed the old packages (2.0.15) before, but... - if I do so, I cannot even start PalmOS Devices under the system menu: Cannot connect to the GnomePilot daemon. I'd be glad if someone could help me. TIA, I suggest you take a look at the recent discussion on this list. The thread started here: http://mail.gnome.org/archives/gnome-pilot-list/2008-August/msg00011.html Regards, Matt Matt Davey Diplomacy is letting them have it your way. [EMAIL PROTECTED] ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Treo 755p and General Tips
Hi Jay, On Mon, 2008-09-01 at 11:51 -0400, Jay Bloodworth wrote: The immediate issue: I'm trying to get my Treo 755p to talk to gnome-pilot. This is under Fedora 8. I go through the configuration wizard, but the sync times out before a connection is made. Relevant dmesg follows: hub 2-0:1.0: unable to enumerate USB device on port 4 usb 7-2: new full speed USB device using uhci_hcd and address 12 usb 7-2: configuration #1 chosen from 1 choice usb 7-2: New USB device found, idVendor=0830, idProduct=0061 usb 7-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5 usb 7-2: Product: Palm Handheld usb 7-2: Manufacturer: Palm, Inc. usb 7-2: SerialNumber: PalmSN12345678 This repeats a number of times, perhaps once per attempt to hotsync, certainly more than once per time I've plugged in the USB cable. There is no /dev/pilot. Isn't udev supposed to create this? The larger issue: I can't find any documentation about how the various technologies and configuration files relating to gnome-pilot interact. Based on searching, it seems my problem could be related to udev, libusb, devices.xml, hal, or goodness knows what else. It's very difficult to know where to start troubleshooting. The most useful support documentation for gnome-pilot currently is probably the archives of this mailing list, followed (hopefully) by the Gnome Live wiki page: http://live.gnome.org/GnomePilot The runtime help (launchable from the configuration applet or the panel applet) also contains reasonable information. The README under /usr/share/doc/gnome-pilot is pretty out of date. For your current problem, my guesses are either: 1. You haven't specified usb: as your device file name. If there is no /dev/pilot then that probably means your system is set up to disable the 'visor' usbserial driver and should be using libusb directly. Instead of specifying '/dev/pilot' use 'usb:'. 2. It is possible you are affected by bug #484509: http://bugzilla.gnome.org/show_bug.cgi?id=484509 This is a bug caused by changes in HAL since your version of gnome-pilot was released. There is a workaround, discussed on this list, of suspending the 'hald' process when starting (or restarting) gpilotd. Better, of course, is to apply a patch and rebuild gnome-pilot from source, or get your fedora package maintainer to do so. Hope this helps, Matt Matt DaveyWhat do you call books that aren't cooked? [EMAIL PROTECTED] Rare. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
RE: Evolution Contacts -- PalmOS Contacts DB mapping
mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list -BEGIN PGP SIGNATURE- Version: PGP Desktop 9.8.3 (Build 4028) Charset: us-ascii wj8DBQFItbMm3fPbFEOFPCwRAim9AJ0dO/I2oHH2IGvft5uq2KUXj/96mACfYOVS 07ml7wH/A2qOrYR/5Q60Lc4= =uZM/ -END PGP SIGNATURE- ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt DaveyIf you think education is expensive, try ignorance. [EMAIL PROTECTED]-- Derek Bok ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
RE: How to add conduits after recompilation
On Thu, 2008-08-21 at 22:07 +0800, z w wrote: Hi Matt, [...] Is there a safe way to have a clean install without manually compiling and installing Evolution ? I mean use OpenSUSE's rpms, and only gnome-pilot compiled manually. This is outside the scope of this list, but the steps are along these lines: 1. Download the gnome-pilot SOURCE RPM for your current distributed version. 2. Create a 'patch' file for your required changes. 3. Unpack the source rpm (install it) and add your patch file alongside the existing patches - pretty much all distribs will make some changes to the distributed sources. 4. Edit the 'spec' file to list your patch file so that it gets applied. Also, change the package 'version' number so that it is recognised as 'more recent' than your installed copy. 5. rebuild the binary RPMs from your modified source RPM folder. 6. install. 3) Sync of Memos is broken, neither Synchronization nor Copy from PDA nor Copy to PDA work, same situation for both Treos. 4) With Treo 680, when I disable all but Memo sync, only Memo sync happens (but not works really). [] - ememoconduit-Message: pre_sync: Memo Conduit v.0.1.6 ememoconduit-Message: Memo Conduit v.0.1.6 ememoconduit-Message: Using timezone: /softwarestudio.org/Tzfile/Asia/Beijing (gpilotd:3832): gpilotd-WARNING **: Copy from PDA failed! gpilotd-Message: Synchronization ended I don't know what is causing this message. It probably indicates a bug somewhere in the memo conduit and/or gnome-pilot, but may be triggered by somewhat corrupt databases on your treo or evolution. The error message is quite generic, so it's not clear where the problem lies, sorry. Matt Matt DaveyIn Milan, traffic lights are regulations, in Rome they are [EMAIL PROTECTED]suggestions, in Naples they are Christmas decorations. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: improving the Evolution addressbook conduit
Hi Alex, On Fri, 2008-08-22 at 05:06 -0700, Alex Lancaster wrote: MD == Matt Davey writes: MD I'm beginning to take a look at the Evolution conduits, and have MD started with the addressbook conduit. MD I'm aiming to start by fixing some data corruption bugs that have MD annoyed me for a while. An early win is fixing the 'other' field MD bug: http://bugzilla.gnome.org/show_bug.cgi?id=547223 There are MD several other bugs that need fixing and lead to data rot. Once MD that is out of the way I'll look at adding support for ContactsDB MD and the 'new' fields such as birthdays and photos. Support for MD ContactsDB will require some limited new API on the gnome-pilot MD side. Won't this require some changes on the pilot-link level to talk to ContactsDB? I seem to recall from a posting by David Desrosiers some time back that there was some initial work done in pilot-link but that is currently incomplete. I haven't yet looked in detail at the pilot-link support. The basics are there, which might be sufficient. At one stage jpilot had better Contacts support and I'm not sure if that's all been rolled in to pilot-link. We'll have to check that out. Also, we'll have to decide whether to have backwards compatibility for pilot-link versions that don't support ContactsDB. That would complicate the code but it's usually worth the trouble. It would be best that, where it makes sense to do so, code that is developed to parse ContactsDB could be pushed into pilot-link (as the lower level in the stack). That way applications outside the gnome-pilot universe such as jpilot and the Perl bindings for pilot-link (I use these to sync my Treo with BBDB via syncbbdb) could also benefit. Of course I'm assuming that sync via the Evolution conduits uses at least some of the code in pilot-link, and I haven't looked at the code to know how it is actually currently designed/implemented, so I'm probably way off base here. Absolutely. That is the design goal. Internally, Evolution conduits use the pilot-link structures and methods for unpacking and packing the palm DB structures. Matt Matt DaveyIf the rich could hire other people to die for them, the [EMAIL PROTECTED] poor could make a wonderful living - Yiddish Proverb ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: How to add conduits after recompilation
Hi again, answers inline. On Wed, 2008-08-20 at 14:40 +0800, z w wrote: Hi, Still not receive replies to my questions. I've checked my settings in the mailinglist, I should receive each message. Your mailing list settings were set to 'digest' so you were not getting individual messages. I've changed this for you now. So I have to reply in yet another new thread. Matt, Thanks very much, you were right, my problems were due to different installation locations. By copying Evolution's conduit files to /usr/local/share..., after a reboot, I see these conduits in the gnome-pilot settings. My Treo 650 works fine now. Great. New problems: My Treo 680 is randomly working. The difference is : For Treo 650, I must press the Hotsync button for beeing detected by udev, then /dev/ttyUSB0, 1 and /dev/pilot are created. But for Treo 680, these files are created as soon as it's connected to the USB cable. And the sync functions once / 3-4 times. And after that, the Treo 650's sync is blocked. Without getting into details, the Treo 680 has differences that seem to make it hard to use with the 'visor/ttyUSBx' connections and gnome-pilot. You can search this list and the 'pilot-link-general' list to learn more. You will probably have better results if you can use 'libusb' syncing. This is now the default on Ubunutu, for example, but you can try following the libusb HOWTO if your distribution is using visor: http://code.pilot-link.org/README.libusb Worse: I expected that both Treos get synced to the same Evolution. But the result is all data are duplicated in Evolution ! [...] This doesn't surprise me. The entries will have different 'unique IDs' on each Treo, so they will cause duplicates. I would have thought it's pretty unusual to need to sync two palm devices with the same Evolution install. I know there is code there to deal with a single palm and multiple desktops, but it is possible that we would need to add something to detect multple palms and a single desktop and use the same 'slow sync' code path in that case. The obvious workaround is to have one of the Treos set to 'copy to PDA'. This will mean that changes made on that Treo will NOT show up in Evolution, but it should mean that you can sync with both devices without getting duplicates. Now I'm trying to remove all that duplicated data. Notice in Windows with Outlook/Pocket Mirror, the sync works very fine with the two Treos. I am not familiar with how this setup deals with multiple devices, so can't comment. I wonder how gnome-pilot is designed to sync multiple devices. Suppose that I sync the two Treos with Evolution, and remove duplicated data in Evolution, after a new sync, can I expect that both Treos reflect the new data state ? And then can modifications made in both Treo be propagated to each other ? No, I don't think this will work. If you can live with only making changes on one Treo, then I think you can get a good working setup. Matt (I've still one Treo without corrupted data, so I want to be sure before syncing data back to it) Thanks, Matt DaveyI wonder if other dogs think poodles are members of a [EMAIL PROTECTED] weird religious cult. -- Rita Rudner ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
RE: How to add conduits after recompilation
Hi again, On Wed, 2008-08-20 at 22:43 +0800, z w wrote: [...] During the time I tried everything to make it work, I've already tested usb:, and it worked when /dev/ttyUSB1 worked. But in the README.libusb, it's stated that I should put visor in the blacklist. I don't understand how both usb: and /dev/ttyUSB1 could function at the same time. Neither do I :) But if usb: works for you, stick with it and hopefully it'll do a better job for the Treo680. This doesn't surprise me. The entries will have different 'unique IDs' on each Treo, so they will cause duplicates. I would have thought it's pretty unusual to need to sync two palm devices with the same Evolution install. I know there is code there to deal with a single palm and multiple desktops, but it is possible that we would need to add something to detect multple palms and a single desktop and use the same 'slow sync' code path in that case. Is there a way to verify unique IDs on both Treos, by a pilot-link command for example ? I'm not sure what you mean, but I really don't think syncing two devices bidirectionally is going to work with gnome-pilot right now. If you want to see the Treo's unique IDs you can look in the files ~/.evolution/addressbook/local/system/pilot-map-*.xml I travel a lot between two countries, so I get two Treos with 2 SIM cards, one for each country. It's why I need to sync these two Treos. Okay, that makes some sense. I don't know much about Treos but I'm amazed there isn't a GSM/CDMA version that can be used worldwide. The obvious workaround is to have one of the Treos set to 'copy to PDA'. This will mean that changes made on that Treo will NOT show up in Evolution, but it should mean that you can sync with both devices without getting duplicates. I've already thought to this workaround. But another inconvenience is that, in gnome-pilot's settings, the copy to PDA is on the conduit, shared by both devices. That means that I have to change it each time, depending on the Treo I'm syncing. There is a great chance to make mistakes. It's better if this setting is on the device setting. The copy to PDA is on the conduit screen but the settings are PER-PDA. Select the PDA from the drop-down list, and configure your per-PDA conduit settings. Notice in Windows with Outlook/Pocket Mirror, the sync works very fine with the two Treos. I am not familiar with how this setup deals with multiple devices, so can't comment. I don't know how Pocket Mirror managed to sync the two Treos, but it does it. May be it keeps track of unique IDs and a mapping between the two devices ? I suspect it does a 'slow sync' - ignoring the unique IDs and comparing the contents of each record to perform matches. Matt Matt Davey The journey of a thousand miles begins with [EMAIL PROTECTED] a broken fan belt and a leaky tire. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: How to add conduits after recompilation
Hi again, On Mon, 2008-08-18 at 13:05 +0800, z w wrote: Hi, Because of the bug 484509 (http://bugzilla.gnome.org/show_bug.cgi?id=484509), I've recompiled the source code of gnome-pilot. After installation of required depending packages, and applied the patch correcting the bug, I've successefully installed the new version. good going so far... But since then: 1) I can no longer see gpilotd-applet on the gnome panel (but it's running). 2) Via Evolution, I get the settings, but in the conduit list, I lost all evolution related conduits. I suspect that your installation of gnome-pilot has not gone into the same place on the system as your distribution-supplied version. For item 1), you should find the file GNOME_PilotApplet.server. This contains the pathnames for the panel applet. You have probably got one installed under /lib/bonobo/servers/ and you may have another (your new one) installed under /usr/local/lib/ Item 2) is similar. Your evolution install is probably compiled to put its conduit definition files into /usr/share/gnome-pilot/conduits/, whereas your new gnome-pilot may be looking for them under /usr/local/share/... If so, you may just be able to copy the system installed evolution files called e-address.conduit, e-todo.conduit, etc, into /usr/local/share/gnome-pilot/conduits/ It's probably safer to keep your (new) gnome-pilot under /usr/local rather than /usr, unless you know what you are doing, as you are likely to confuse your package manager! Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Future of gnome-pilot?
Hi Andreas, On Tue, 2008-08-05 at 16:21 +0200, Andreas Ritter wrote: Hello! As I was curious if gpilot would sync especially birthdays in (near) future, I found this thread. Tom's recent post partially answers your question. J-Pilot has just a new release, which can greatly sync all new PalsOS5-Fields, even pictures work great! The question could be also stupid, but why can't you coopearate with j-pilot? Isn't it possible to integrate this code in gpilot? or look at j-pilot's code and know how to to that in gpilot? Yes we should absolutely use the jpilot work to aid development of the gnome-pilot conduits, but it sounds as though there is a fair bit of additional work on the Evolution side. We just haven't had the resources. I'm hopeful that I'll be able to spend some time on the conduits over the next 6 months to address the top requested items: birthdays, photos, corrupted addressbook fields, possibly multiple-calendar sync, etc. I'll need to get my head into the Evolution code as I'm not familiar with it at all. So, but anyway: Thanks for your work, I'm using it for many years!!! Thanks, that's always nice to hear. Matt Matt DaveyHow do you turn a duck into a soul singer? [EMAIL PROTECTED] Put it in the oven until its Bill Withers. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Development /w Evolution Conduits
Hi David, On Fri, 2008-08-01 at 16:11 -0700, David Wade Hagar wrote: I would love to help out with the development of the Evolution conduits. I'm not the best programmer, but I'll throw down with trying to get it to work. great stuff. I'm attaching a Makefile that I've recently started using to compile evolution and gnome-pilot from source. I've only made a few edits from a version I downloaded from here: http://mad-scientist.us/evolution.html This makes it easy to check out the current svn versions of evolution and gnome-pilot and get it all built with debugging. I've noticed that its already a known issue about the address book fields, but additionally, there is lack of support in the calendar for the Location field. Also, categories in contacts don't sync either. This is all, sadly, true. Also, there's no support for birthdays, photos, etc, in Contacts. I started taking a look at the problem with the field corruption in the addressbook. I found that a conversion between ical format and back again seemed to be losing data, but I didn't have time to get to the bottom of it (and my gdb seemed to be having some problems with my built-from-source build). I suggest you dive in, start familiarising yourself with the code (maybe look at the Location field as an initial exercise?) and stay in touch. Regards, Matt Matt Davey What the world needs is more good readers, [EMAIL PROTECTED] not more good writers. -- Borges. #!/usr/bin/make -f # # Build (debuggable) Evo from SVN # Run make help for some help, or see the comments below. # # Requires GNU make 3.80 or better. # # Author: Paul Smith [EMAIL PROTECTED] # Version: 2.12 # Date: 29 May 2008 # # -- # Copyright (C) 2007, 2008 Paul Smith # This Makefile is free software; you can redistribute it and/or modify it # under the terms of the GNU General Public License as published by the Free # Software Foundation; either version 3 of the License, or (at your option) # any later version. # # You should have a copy of the GNU General Public License on your system. # If not, see http://www.gnu.org/licenses/. # -- # # You can look here for more/alternate information: # http://www.go-evolution.org/Compiling_Evolution_from_SVN # # Enhancements/suggestions provided by: # Patrick Ohly [EMAIL PROTECTED] # == # By default we build for Ubuntu (I'm testing on Ubuntu 8.04). # # If you want to build for another distro, see if it's listed in the DISTROS # variable (currently only Debian Ubuntu releases are listed) and, if so, # change DISTRO to your distro. You can do this in local.mk to avoid # changing this makefile. # # If your distro is not supported, you can set distro to empty and the check # for prerequisite packages will be skipped. Of course, if you don't have all # the proper development packages installed the build will fail. # == # v User Customization v # Feel free to change these if you like # What branch to work with. If not set, we use the trunk. Close to a # release, however, you might prefer to use the pending release. # E.g.: # BRANCH := 2.20 BRANCH := # Where to install Evo. DO NOT use /usr here for any system controlled by a # package manager (rpm, dpkg) PREFIX := /opt/evo # Where to build objects. Currently not all packages work properly outside of # their own directories, even though the GNU coding standards require it. OBJDIR := obj #OBJDIR := . # What distro you use, for checking that all prerequisite packages for a # successful build are installed. The currently supported distros are # listed in the DISTROS variable below. # If yours is not one of these, set this to empty and take your chances! DISTRO := hardy # Comment this out if you don't want to use ccache CCACHE := ccache # Set this to empty if you want to see the rules being run V := @ # Enable/disable optional packages ENABLE_gtkhtml := y ENABLE_exchange := y ENABLE_webcal := y ENABLE_gnome-pilot := y # You can override the above by creating local.mk setting these vars # if you don't want to modify this makefile. -include local.mk # ^ User Customization ^ # == # - You don't need to touch anything below here!! - # - (unless you really know what you're doing...) - # These are the prerequisite packages needed on the system before we can build # Evo. There are different ways to check for them, based on distro. DISTROS := feisty gutsy hardy etch feisty-PREREQS := \ gtk-doc-tools subversion flex bison build-essential \ libldap2-dev libnss-dev libnspr-dev libgail-dev evolution-dev \ icon-naming-utils
Re: sync calendar
Hi, On Tue, 2008-07-29 at 11:04 +0200, Xavier Pegenaute wrote: Hi, Using evolution, can I sync my palm with more than one calendar (I have at least 2 calendars from google calendars) ? At present, the Palm calendar app does not have separate calendars. You can choose which Evolution calendar the palm calendar should be synchronised with, but that's all. Palm contains 'categories', which are also available in Evolution (but not shown by default, I think). It might be an interesting idea to optionally map 'categories' to 'calendars' for the calendar app. We'd have to make this optional, so that we didn't break the conduit for people currently relying on categories, but it would probably work reasonably well for supporting multiple calendars. Matt Matt Davey Never test the depth of the water with both feet. [EMAIL PROTECTED] ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Restoring from backup
Hi Michelle,
On Mon, 2008-07-14 at 20:19 +0200, Michelle Baert wrote:
Hi,
My question might look simple but I couldn't find an answer in web
pages.
I've used gnome-pilot (with applet and evolution) for months, it's
configured to make backup at every hotsync, but I realize now I don't
know how to restore files from these backups, after :/ a hard reset of
my Palm (TX).
The first thing I recommend (you've probably done so already) is to make
a copy of your backup directory to avoid losing it!
After a hard reset, gnome-pilot attempts to recognise your palm from
some internal system info. It it gets a match it should attempt to
restore from your backup directory. Are you getting any diagnostics
from gnome-pilot? If not, you could try running gpilotd from the
command line to see the output ('killall gpilotd; /usr/bin/gpilotd
(or /usr/libexec/gpilotd)').
My backup-conduit file is like this:
[Pilot_1936]
backup_dir=/home/mich/pim/palm/backup
updated_only=true
remove_deleted=false
no_of_backups=3
exclude_files=
In gpilotd-control-applet, backup conduit is enabled, but the one time
action combo offers no choice but None.
I tried to restore (after a hard reset) with
pilot-xfer, but it fails on many files.
pilot-xfer -r /home/mich/pim/palm/backup -p usb: (or -p /dev/ttyUSBxx
or whatever you're using) should work. One caveat is that I believe it
requires the named directory ONLY contains .pdb and .prc files. If you
have anything else, including sub-directories, move them out of the way
and try again.
Let us know how you get on.
Matt
Matt Davey Science is to computer science as hydrodynamics is to plumbing.
[EMAIL PROTECTED] -- Stan Kelly-Bootle
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Future of gnome-pilot?
Hi Gerhard, On Thu, 2008-07-03 at 21:10 +0200, Gerhard wrote: Hi! Maybe it's a stupid question: is gnome-pilot still under development or is it dead? Because there are a lot of Palms (Treo, Centro,...) with PalmOS 5.x. And it's not possible to sync all contact information with evolution via gnome-pilot (birthday, anniversary, photo, ...) It's not a stupid question. gnome-pilot development is not dead - the most recent release was in January and included support for Bluetooth syncing. Since then there have been a few bug fixes that have not yet been released. The Evolution conduits are actually part of the Evolution project (in principle, any project can choose to build a gnome-pilot conduit via the plugin architecture). These conduits have been worked on within the past year. The most recent changes were to add decent category support to the datebook, todo and memos conduits. This work has primarily been done by Nathan Owens and Tom Billiet, as far as I know. The two items highest on my list for the Evo conduits are: 1. Addressbook fields tend to get messed up when syncing. I find that phone numbers and email addresses, for example, tend to end up duplicated across multiple fields (Other, Home, Business... for example). 2. Support for photos, birthdays, anniversaries for OS5 Contacts database. I do not have much time to spend on these items, but am likely to start looking at them if volunteers don't turn up soon! Matt Matt Davey I am a marvelous housekeeper. Every time I leave a man [EMAIL PROTECTED] I keep his house. --- Zsa Zsa Gabor ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Patch: detection of Palm with latest HAL no longer working
Hi Frederic, I finally got around to integrating your patch. It is now committed to SVN, and includes backwards compatibility for the older HAL structures. I tested it on Ubuntu 8.04, which includes both HAL structures, so not a 100% test, but I'm confident it's working for both cases. Matt On Thu, 2008-04-17 at 12:16 +0200, Frederic Crozat wrote: Le mardi 25 mars 2008 à 10:24 +, Matt Davey a écrit : Hi Frederic, First, I apologize for my slow response, I got busy in finishing Mandriva 2008 Spring and I also attended conference in the mean time. On Fri, 2008-03-21 at 19:10 +0100, Frederic Crozat wrote: Hi, we switched in Mandriva to hal 0.5.11 (rc2 at the moment, final is pretty imminent) and info.bus is no longer advertised as part of usb devices (key has been deprecated). Thanks for pointing this out. I would like to support hal backwards compatibility for the moment, so how about we check for pda.platform first, and then fall back to devices.xml and info.bus (or another, supported, way to query USB vendor/device IDs)? That way we avoid requiring the most up to date HAL version for gnome-pilot - if someone wants the new bluetooth support on an existing installation, they shouldn't need to upgrade HAL. Yes, fallback is probably better than my dirty search and replace patch ;) The attached patch changes this check with a check on pda.platform. Those keys have been recently added in hal-info to detect all known Palms (supported by pilot-link) so device permissions can now be handled by hal / ConsoleKit / PolicyKit. I think a good patch or hal_device_added logic (including usage of devices.xml) could be removed since most of the information needed for device detection is now directly available from HAL, including the right device to use (when using visor module). How robust do you think the usbserial tty device identification can be? I'd love to be proved wrong, but I'd be surprised if this had actually been solved! There have been many attempts over the years, and if you have a device that behaves differently and confuses HAL, you'd be pretty annoyed if there isn't a workaround. Well, ATM, hal doesn't do any USB tty device identification. It only uses USB ids. And we know usb ID are not reliables for USB tty, since several Palm devices share same usb ID and uses different tty. My suggestion was for people using libusb pilot-link and not for visor module based pilot-link. I do agree that letting HAL do more work is the right thing to do, but it has to make life easier for the users. A would be useful to rework the config applet to do more automated detection of usb/serial/net/bluetooth devices - listen to everything and configure the first palm that connects. Then it would need to be integrated with nautilus new volume manager so it would be auto-started when a palm is started but was never configured. Matt DaveyI do not agree with a word you say, but I will defend [EMAIL PROTECTED] to the death your right to say it. Voltaire ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot gnubie
Hi Paul, Thanks for the gpilotd session output. It appears that gnome-pilot is having trouble talking to evolution-data-server. Either it is not running, or there is some other problem. I haven't heard of this issue before, but Google showed up two related reports: http://ubuntuforums.org/archive/index.php/t-281807.html http://mail.gnome.org/archives/evolution-list/2005-November/msg00285.html Neither of these are recent, and neither has any resolution attached, unfortunately. So, is evolution-data-server running? (I'm guessing it probably is). Are there any Evolution experts out there who can shed some light / make some educated guesses? Matt On Tue, 2008-06-17 at 12:00 -0400, Paul King wrote: A typescript (plain ascii text) file of the shell session has been sent as an attachment. Thanks Paul King On Tue, 2008-06-17 at 12:51 +0100, Matt Davey wrote: Oops, forgot one thing: On Tue, 2008-06-17 at 12:37 +0100, Matt Davey wrote: Okay, let's get some more information. Try running gpilotd from the command-line and send us the output: 1. open a terminal. 2. remove the gnome-pilot applet from the taskbar (the hotsync icon) if it is there. 2a. Now kill any running gpilotd: killall gpilotd 3. start gpilotd in the terminal (usually /usr/bin/gpilotd or /usr/libexec/gpilotd) 4. Now do a sync. 5. Post the output from the terminal to this list. If you are getting data backed up but Evolution addresses etc. are not getting synced, then there is some problem with the Evolution conduits. Either they are not recognised by gnome-pilot, not enabled, not running at sync time or not running correctly. Have you double-checked the conduit settings in the gnome-pilot configuration applet? If you have multiple addressbooks, for example, is gnome-pilot synching with the right one? Matt DaveyA hero is someone who can keep his mouth shut [EMAIL PROTECTED] when he is right. Yiddish Proverb. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list #0; ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt Davey Numeric stability isn't that important when you're guessing. [EMAIL PROTECTED] ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot gnubie
Hi Paul, On Sun, 2008-06-15 at 08:33 -0400, Paul King wrote: On Sun, 2008-06-15 at 14:47 +1000, Andrew Greig wrote: Hi Paul, Start by installing evolution-pilot, using whatever package manager suits your distro. I can't find anything comparable for Debian (Ubuntu 8). apt-get can't find anything called evolution-pilot. Even search strings like evolution pilot (no quotes and with or without a hyphen) on the Ubuntu site yield absolutely nothing. Doing this in Google only leads me to rpm packages, and I am not sure I would want to use alien unless I am desperate. Don't worry, the evolution conduits come in the base evolution package on Ubuntu. Then go to EditSynchronisation Options and follow the bouncing ball. This brings up an instance of Gpilot. My info is already there. I am still not convinced that Evolution is aware of any of this info. I think what you're missing is the need to enable the Evolution conduits. When you bring up the configuration applet for gnome-pilot, click on Conduits, make sure your PDA is selected (you have probably only got one configured) and then make sure the Evolution conduits are Enabled (EAddress, ECalendar, EMemos, ETodo). You can then decide if you want to synchronise, overwrite the desktop from the PDA or overwrite the PDA from the desktop. Matt Matt Davey To err is human, to moo bovine. [EMAIL PROTECTED] ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Which Palms work well?
As regards gnome-pilot support, I don't believe there are many models with reported problems. The Lifedrive is certainly one exception. If you identify a model you're interested in getting, try searching this list's archives. Many of the difficulties lie in problems on the desktop side that cause problems for almost all devices. To make sure you don't get hit by those problems, look for a model that can support bluetooth or network hotsync (bluetooth sync is supported by gnome-pilot since 2.0.16). The other main type of problem is bugs and incompleteness in the conduits. For example, the Evolution conduits don't yet support syncing of birthdays or photos in the addressbook. If you get an old palm model you won't have support for birthdays or photos in the addressbook either, but I don't know if you'd consider that 'working better' with gnome-pilot! Matt On Thu, 2008-06-12 at 20:20 +0200, Patric Schira wrote: Hi Jonathan, not the newest model - but my Palm M515 works pretty well with gnome-pilot. HTH Patric Am Donnerstag, den 12.06.2008, 17:56 +0100 schrieb Jonathan Ellis: Hi, I am thinking of buying a Palm. Is there a list of which ones work well with Gnome-Pilot and which ones are reliable? I had a Palm III ages ago but it was awful: when the non-rechargeable batteries ran out it only gave a minute to replace them or you lost all data. Now I am getting frustrated with my Windows Mobile PDA which crashes and loses all its data often enough to be a pain. Also It is difficult to sync Windows Mobile 3 devices to Linux at the moment - they are working on it. So I am hoping to get a Palm in the hope it will be more reliable and I can sync it more easily. Any help would be greatly appreciated. Thanks Jonathan ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt DaveyAnyone who, like me, has been educated in English public [EMAIL PROTECTED] schools and served in the ranks of the British Army is quite at home in a third world prison. -- Roger Cooper ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Palm Life Drive and Evolution Pilot
Hi Andrew, On Wed, 2008-06-11 at 10:38 +1000, Andrew Greig wrote: Hi all, My struggle to get a Palm Life Drive working under libusb has been going on for over a year. I have resigned myself to the fact that I will have to continue to work with visor because even if it is slower it works for me. The problem now is to figure out why gnome-pilot will not sync with the Palm Life Drive, when Jpilot and Pilot-xfer both work under visor. One workaround, just to get things going, is to configure network hotsync. This should avoid the various known problems with the lifedrive and usb syncing. It's certainly frustrating if it works under pilot-link and jpilot but not gnome-pilot. There was a time when new kernel/udev revisions would break some systems and repair others -- I'm guessing it's down to timing, but without a device to test, it's hard to fix. What I could imagine would be some tunable parameter in gnome-pilot where you could control the delay between device detection and attempting to sync. In terms of debugging, the usual thing is to run gpilotd in a console and see what messages show up. Does it attempt a connection, or does it never realise a device is trying to sync? One possible thing to try would be to run gpilotd in a console, press 'control-z' to suspend it, press hotsync on your lifedrive, and then 'fg' to continue gpilotd. If gpilotd is trying to sync 'too soon' after the sync is started this might just work. If so, it would be new information... If there is anyone out there successfully syncing gnome-pilot with a lifedrive, speak up! Matt Matt Davey You can't have everything. Where would you put it? [EMAIL PROTECTED] -- Steve Wright ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: TX aborts gplilotd sync
On Tue, 2008-05-27 at 14:42 -0400, Jim McKean wrote: Was working as recently as friday. Terminal output is below. In this example, I think all conduits are disabled and it still aborts. Same if they are on. Unbuntu Hardy gnome-pilot 2.0.15-2ubuntu3 gnome-pilot applet 2.0.15 Note what appears to be a glibc error message: *** glibc detected *** gpilotd: corrupted double-linked list: 0x080f0460 *** Hi Jim, I'm doubting this problem is rooted in the gnome-pilot code. Try googling for closedir+0x28 double free, or even just closedir+0x28. Here's one posting that might give the flavour: http://lists.digium.com/pipermail/asterisk-users/2007-February/179580.html It might be worth trying to rebuild the gnome-pilot package on your system, in case there has been some binary incompatibility introduced in a system library (though I don't see anything obvious in your list of updated packages). I'd suggest you open a bug on bugzilla.gnome.org to track this, rather than posting to this list. Post a reference to the bug ticket here, so people can follow the discussion if they want. Other things to try, to generate more info: install the gnome-pilot-dbg package to get a backtrace with symbols, and start gpilotd within 'valgrind'. This will generate quite a bit of output but might catch something significant. You could attach the output to a bug report. Regards, Matt synaptic logs shows the following updates since last good sync. [snip] *** glibc detected *** gpilotd: corrupted double-linked list: 0x080f0460 *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb735cd0d] /lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb73604f0] /lib/tls/i686/cmov/libc.so.6(closedir+0x28)[0xb73826b8] /usr/lib/gnome-pilot/conduits/libbackup_conduit.so[0xb6c660dd] /usr/lib/libgpilotdconduit.so.2[0xb7f3c46f] /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x129)[0xb758c759] /usr/lib/libgobject-2.0.so.0[0xb75a0d1d] /usr/lib/libgobject-2.0.so.0(g_signal_emitv+0x13e)[0xb75a2d9e] /usr/lib/libgpilotdconduit.so.2(gnome_pilot_conduit_backup_restore+0x240)[0xb7f3cd10] gpilotd[0x80523bc] /usr/lib/libglib-2.0.so.0(g_list_foreach+0x21)[0xb7506731] gpilotd(gpilot_initial_synchronize_operations+0xbb)[0x8053149] gpilotd[0x804e9c5] gpilotd[0x804ec30] gpilotd[0x804ef98] gpilotd[0x804fb2e] /usr/lib/libhal.so.1[0xb74ccda9] /usr/lib/libdbus-1.so.3(dbus_connection_dispatch+0x397)[0xb74989f7] /usr/lib/libdbus-glib-1.so.2[0xb75c54cd] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x178)[0xb7508bf8] /usr/lib/libglib-2.0.so.0[0xb750be5e] /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x6c)[0xb750c3ac] gpilotd[0x8050af4] gpilotd(main+0x106)[0x8050cd8] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb7307450] gpilotd[0x804d7d1] === Memory map: 08048000-0805c000 r-xp 08:07 67253214 /usr/bin/gpilotd 0805c000-0805d000 rw-p 00014000 08:07 67253214 /usr/bin/gpilotdAborted ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gpilotd sync stopped working
Hi Adam, On Sun, 2008-04-27 at 18:36 -0400, Adam C Powell IV wrote: Hello, I'm running Debian lenny (testing) with pilot-link 0.12.3-4 and gnome-pilot 2.0.15-2.1. Sometime in the past 3-4 weeks (don't know exactly what upgrade), sync stopped working. I plug in my Treo 700, hit sync, and nothing happens. None of my old tricks involving timing a gpilotd restart or continue with the sync work (tried everything from 10 secs before to 10 secs after at 1 sec intervals). And nothing shows up in .xsession-errors when I sync, it's as if gpilotd doesn't know anything is going on. [snip] Any ideas on what could be wrong with my setup? Hmm. One possibility is that HAL has been updated (see thread from Frederic Crozat from March 21st last). You might be able to check this by suspending hald and restarting gpilotd. gpilotd should fall back to polling /proc for detection of USB devices. If that's not the case, please send gpilotd console output. Matt Matt Davey Many candles can be kindled from one candle [EMAIL PROTECTED] without diminishing it. -- the Midrash ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Treo 680 - Birthday, Photo sync
On Thu, 2008-03-20 at 21:19 +0100, gerhard.rauniak wrote: Hi! Is it possible to sync the birthday and photo data with evolution? I really miss it. Not at present, unfortunately. It requires some work in the evolution addressbook conduit. Matt Matt DaveyWhy do they only eat one egg in France? [EMAIL PROTECTED] Because in France, one egg is an oeuf. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Gnome-Pilot on Kubuntu
Hi again, On Mon, 2008-03-10 at 12:00 -0700, Rick Knight wrote: Matt Davey wrote: Hi Rick, Glad the install of gnome-pilot 2.0.16 worked pretty well. On Mon, 2008-03-10 at 09:47 -0700, Rick Knight wrote: [...] And this error (repeated for each conduit)... (gpilotd-control-applet:18420): libgpilotdcm-WARNING **: unable to g_module_open (/opt/gnome2/lib/evolution/2.12/conduits/libeaddress_conduit.so), reason /opt/gnome2/lib/libedataserverui-1.2.so.8: undefined symbol: e_source_peek_color_spec Can you suggest a way around these errors? Hmmm. This suggests your svn install of evolution is a bit broken. libedataserverui is complaining that it can't find the definition of 'e_source_peek_color_spec', which should be defined in 'libedataserver'. I suspect that libedataserverui is picking up your system installed version of 'libedataserver', instead of your newly compiled version (assuming you do have 'libedataserver' compiled from svn and living in /opt/gnome2/lib). You can run 'ldd /opt/gnome2/lib/libedataserverui-1.2.so.8 | grep libedataserver' to see where it is finding libedataserver. If it is picking up the wrong version, that probably points to a bug in evolution-data-server, as it should have a newer version for libedataserver to prevent it picking up the old version. Matt [...] Thanks again Matt, Here's the output of ldd /opt/gnome2/lib/libedataserverui-1.2.so.8 | grep libedataserver... libedataserver-1.2.so.9 = /opt/gnome2/lib/libedataserver-1.2.so.9 (0xb7e85000) It looks like it's pointing to the correct file. Anything else I can try? In that case we need to check which 'libeaddress_conduit.so' is being picked up by your gnome-pilot installation - do you have versions from a previous evolution installation? Run 'ldd' on 'libeaddress_conduit.so' - it could be picking up a mixture of libedataserver* libraries. The available conduits are found by searching for all *.conduit files in a known directory - usually /usr/lib/gnome-pilot/conduits. If you have got the wrong paths in these .conduit files, it will pick up the wrong conduit.so files. You want to make sure the .conduit, conduit.so, libe* files are all coming from your svn build. Matt Rick ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt Davey It's time to invent some new cliches. [EMAIL PROTECTED] ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Gnome-Pilot on Kubuntu
Hi Rick, On Fri, 2008-03-07 at 15:01 -0800, Rick Knight wrote: I'm trying to install gnome-pilot on my Kubuntu Feisty box and need some help. I have installed Evolution 2.12 from svn and it's working fine. I installed from svn because the Kubuntu package is fairly old and lacks a feature I need (print setup). I want to use gnome-pliot with evolution but the Kubuntu package doesn't seem to find my evolution installation. Now I'm trying to install gnome-pilot from svn to the same location I have evolution installed in but I'm running into a problem. When I run make it builds for a bit and then stops with this error... gnome-pilot-conduit-config.gob: In function 'gnome_pilot_conduit_config_sync_type_int_to_str': gnome-pilot-conduit-config.gob:54: error: 'GnomePilotConduitSyncTypeCustomStr' undeclared (first use in this function) [snip]... I can think of two things to try: 1. Run 'make -k' followed by 'make'. See the README file on the 'build order' bug for details. This is gnome bug 508262: http://bugzilla.gnome.org/show_bug.cgi?id=508262 2. Try building from the recently released gnome-pilot 2.0.16 distribution rather than svn. Matt Matt Davey I do not know myself, and God forbid [EMAIL PROTECTED] that I should. -- Johann von Goethe ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Gnome-Pilot on Kubuntu
Hi Rick, Glad the install of gnome-pilot 2.0.16 worked pretty well. On Mon, 2008-03-10 at 09:47 -0700, Rick Knight wrote: [...] Matt, Thanks for the suggestion. I've downloaded and successfully built 2.0.16. I'm even able to sync some data, mainly a backup of my device. I've enabled the Evolution conduits and when try to syncronize, I get this error ... (gpilotd-control-applet:18420): libglade-WARNING **: could not find glade file 'gpilotd-capplet.glade' You can ignore this error. It's a harmless side effect of fixing bug #508268. If anyone knows how to suppress this warning message from glade_xml_new(), let me know... And this error (repeated for each conduit)... (gpilotd-control-applet:18420): libgpilotdcm-WARNING **: unable to g_module_open (/opt/gnome2/lib/evolution/2.12/conduits/libeaddress_conduit.so), reason /opt/gnome2/lib/libedataserverui-1.2.so.8: undefined symbol: e_source_peek_color_spec Can you suggest a way around these errors? Hmmm. This suggests your svn install of evolution is a bit broken. libedataserverui is complaining that it can't find the definition of 'e_source_peek_color_spec', which should be defined in 'libedataserver'. I suspect that libedataserverui is picking up your system installed version of 'libedataserver', instead of your newly compiled version (assuming you do have 'libedataserver' compiled from svn and living in /opt/gnome2/lib). You can run 'ldd /opt/gnome2/lib/libedataserverui-1.2.so.8 | grep libedataserver' to see where it is finding libedataserver. If it is picking up the wrong version, that probably points to a bug in evolution-data-server, as it should have a newer version for libedataserver to prevent it picking up the old version. Matt Matt DaveyLogic, my dear Zoe, is merely the ability to be [EMAIL PROTECTED] wrong with authority - Dr Who ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Further adventures trying to build gnome-pilot
Hi Evan, On Mon, 2008-01-07 at 20:30 -0500, Evan wrote: I poked around a little more, and found that I needed to use gob2 to turn all of the .gob files into .c and .h files, which the compiler had previously been missing. It gets somewhat further, but now it appears I am missing /gpilotd/gnome- pilot-conduit-private.h which has no corresponding .gob file to process. Where is this mysterious file? gnome-pilot-conduit-private.h is generated from gnome-pilot-conduit.gob. This should happen automatically if gnome-pilot-conduit.c or gnome-pilot-conduit.h is missing. If you ran gob2 by hand you probably forgot to use the --always-private-header option. You shouldn't be hitting any of these problems. If autogen is running for you, do a 'make distclean ./autogen.sh make make install'. Matt Matt Davey Confucius say: To understand recursion, you must [EMAIL PROTECTED] first understand recursion. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Further dev work?
Hi Evan, On Tue, 2008-01-01 at 16:31 -0500, Evan wrote: I have kludged together something that should hopefully add a install file option to the right-click menu. When clicked, it should pop up a gtk message box informing the user that they should drag the file onto the applet. I understand the concept of compiling and make files and that sort of thing, but having only ever used .net and java before, I'm not sure what process to follow to test my code. It seems to me that the first step would be to download the entire source directory so that the compiler can build/link it properly. Is there an easy way to do that, or will I have to download each file individually? Looks like you will be on a bit of a learning curve! You can check out the gnome-pilot source tree using 'svn': svn co http://svn.gnome.org/svn/gnome-pilot/trunk gnome-pilot To build from source you will need to install a number of development packages (to install the header files for all the packages gnome-pilot needs to integrate with). You will also need to install any missing build tools like autoconf and libtool. On Ubuntu, for example, I needed to install the following: libpanel-applet2-dev libdbus-glib-1-dev gob2 libtool libgnomeui-dev libhal-dev libgnome2-dev and many others (I didn't keep a list, unfortunately...) Once that is in place, you should be able to build using: autogen.sh make install I often use 'autogen.sh --prefix=/tmp/gp' to build a version of gnome-pilot that installs in /tmp/gp to avoid clobbering the system version. It's okay for testing, but you won't have access to the system conduits, for example. Matt Matt DaveyIf the rich could hire other people to die for them, the [EMAIL PROTECTED] poor could make a wonderful living - Yiddish Proverb ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Further dev work?
On Wed, 2008-01-02 at 10:36 -0500, Evan wrote: I installed all of the ones you mentioned, all of their dependencies and recommended packages. I've gotten most of what I think I need installed, but the autogen.sh fails with the following: configure: error: Unable to find pi-version.h I did a couple of searches in synaptic, but nothing turned up. Which package(s) do I need to install now? libpisock-dev You can install 'apt-file' to make it easier to find packages supplying particular files: apt-get install apt-file apt-file update apt-file search pi-version.h M Matt Davey Statistics are like bikinis. What they reveal is interesting, [EMAIL PROTECTED]what they conceal is vital. -- Kenneth Clarke ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Further dev work?
On Fri, 2007-12-28 at 16:22 -0500, Evan wrote: I found the code for drag n' drop, as well as what I think are the gtk bindings nearer the bottom. I also skimmed through the basics of gtk here: http://www.gtk.org/tutorial/ Where exactly is the gnome_pilot_client_install_file that is being called? I searched through a couple of possible files but couldn't find it. The 'install_file' method is actually defined in gpilotd/gnome-pilot-client.gob, which is processed to create gpilotd/gnome-pilot-client.c You'll pretty soon discover that the gnome-pilot code is not pretty, unfortunately. The good news is that you probably don't need to look at much of it to work on the code. I'd encourage you see what you can do to improve the 'drag and drop' functionality. Here are some ideas for features. 1. PDB/PRC files may always be installed. We could add support for wrapping image files as done in 'par' and we could add support for text files by converting to memos or 'DOC'. We should not accept files that we can't convert to PDBs (or alternatively we could support upload to removable media in a user-specified folder). These options would need to be controlled via a 'per pda' set of preferences. 2. File installation is virtually a 'hidden feature' at the moment. We could add 'install file...' as another option in the right-click menu for the applet. This would pop up a file browser and let you select a file to install. 3. We should add error handling when files can't be installed rather than having them sit in the queue, e.g. if the removable media directory didn't exist. 4. Add management for the queue of files to install (see what's scheduled, per pda, and allow removal). Of these, number 1 is probably the most useful, but none of them are trivial. I noticed that lines 1292-1299 are commented out, and seem to refer to the ability to drag a text-file to the applet and have it install as a memo rather than a file. From what I understand about gnome-pilot, this doesn't sound too hard (maybe just extract the text and pass it to evolution as a new memo? is there an api for that?). There is code in the 'memo-file' conduit (in gnome-pilot-conduits) that supports conversion between text and memos. I suspect, though, that people wanting desktop support for memos will just paste text into Evolution and use the evolution memo conduit. Would this be a good basic project to help get me started, or is it more complicated then it looks? I would suggest adding support for image files, and blocking non pdb/prc files would be a useful starting point. As Tom has pointed out, we need image support for when we come to support the Contacts database. It may be more complicated than you think, but we can try to help here. Happy New Year, Matt Evan On Dec 28, 2007 3:23 PM, David A. Desrosiers [EMAIL PROTECTED] wrote: On Fri, 2007-12-28 at 12:18 -0800, Reitsma, Rene - COB wrote: I mailed to this listserv some time ago when after a kernel update in July 2007 my Z22 stopped syncing. My mail generated some discussion which I have followed but I have lost track of whether or not anyone got the Z22 to work, and if so, how. pilot-link 0.12.3 contains some fixes/workarounds that directly apply to the Z22 issue. If you aren't using the libpisock version mated to 0.12.3, then I would strongly suggest building it and then building the necessary components that work with it, and try again (or wait for someone to build packages based on those versions and ship them to your distro's package repository). I know that the people with Z22 devices that tried these workarounds have it working, so it should work for you as well. -- David A. Desrosiers [EMAIL PROTECTED] Skype...: 860-967-3820 ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Further dev work?
On Fri, 2007-12-28 at 11:09 -0500, Evan wrote: Bug tracking is: http://bugzilla.gnome.org/browse.cgi?product=gnome-pilot I've started looking at some of the source code, and as a sort-of test, tried to find the code that handles files being dragdropped onto the panel applet. My assumption was that it would be in http://svn.gnome.org/svn/gnome-pilot/trunk/applet/pilot.c but I haven't found it. Am I looking in the wrong file, or do I just need to look closer? That's the right file, Evan. Search for 'drop' and you'll see the signals being connected up to be handled by 'dnd_drop_internal' which then calls 'gnome_pilot_client_install_file'. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Further dev work?
On Sun, 2007-12-23 at 12:57 -0500, Evan wrote: Is any further work being done on gnome-pilot at all? The last update to the site was nearly a year ago. Hi Evan, gnome-pilot itself is pretty stable. Most of the updates occur in the evolution source tree, as that's where the Evolution conduits reside. As it happens, I'm taking a look at the gnome-pilot code at the moment with a view to adding in Bluetooth support. More on that anon. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Palm sorta not syncing calendar to Evolution
On Thu, 2007-12-20 at 12:11 -0500, Jim McKean wrote: This is a strange problem. A calendar entry placed on the Palm is synced to Evo calendar. A calendar entry placed on Evo calendar (it is an Exchange calendar account) does NOT sync to the Palm even if conduit is pointed to the Exchange account. A calendar entry placed on a personal account, syncs to the Palm as long as the conduit has been set properly. Calendar conduit is set to synchronize There are no error messages. It appears to finish fine. The appointment is just not synced. I don't have any help for you, but I recently noticed that I have several contacts in Evolution that do not show up on my Palm, even though they originated on my Palm and I don't remember editing them in years. Conduit set to synchronise. No errors. Very strange. Might be time for me to finally get intimate with the evo conduits... Does this behaviour sound familiar to other people? Matt Not sure when it last worked properly. Palm TX - non new application Ubuntu Gutsy Evo 2.12.1-0ubuntu1 Evo-exchange 2.12.1-0ubuntu1 gnome-pilot 2.0.15-2ubuntu2 gnome-pilot-conduits 2.0.15-1ubuntu1 libgnome-pilot2 2.0.15-2ubuntu2 libpisock9 0.12.2-9ubuntu3 libpisync0 12.2-9ubuntu3 Any help appreciated Matt DaveyMany hands make light work - but [EMAIL PROTECTED] Too many cooks spoil the broth. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot crashes treo 650: UPDATE
John, Does gnome-pilot connect after a reboot? Does it help if you disable 'hald' before starting gpilotd? Matt On Sun, 2007-11-25 at 20:27 -0600, John Leidel wrote: Yep yep... did that this afternoon as well... the best i could with the somewhat broken opensuse 10.1 updater. [arg!] On Mon, 2007-11-26 at 10:56 +0900, W.Kenworthy wrote: Make sure you have the latest OS update - some of the earlier versions were less than ... stable ... :) BillK On Sun, 2007-11-25 at 18:56 -0600, John Leidel wrote: a quick update to the note I previously posted to the list... I tried setting up gpilotd to point directly to /dev/ttyUSB0. Once a hotsync operation is requested from the treo, this *immediately* forces a hard reboot of the treo device this may mean that I need to play with the udev device permissions. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Fedora 8 and Palm TE with libusb workarounds
On Wed, 2007-11-14 at 16:31 -0400, George N. White III wrote:
I recently did a fresh install of Fedora 8. Under Fedora 7, I had built
pilot-link with libusb enabled. The F8 pilot-link rpm has a
udev rules file but doesn't install it.
George,
Thanks for the info. The best thing to do here is to search or open an
issue at bugzilla.redhat.com. If the shipping udev rules in F8 are not
correct for you then that is something they should want to fix.
Matt
$ head /usr/share/pilot-link/udev/60-libpisock.rules
# udev rules file for pilot-link's libpisock library, enabled for libusb
#
SUBSYSTEMS!=usb, ACTION!=add, GOTO=libpisock_rules_end
# Sony handheld devices
ATTRS{idVendor}==054c, ATTRS{idProduct}==0038, GROUP=dialout,
MODE=0664
ATTRS{idVendor}==054c, ATTRS{idProduct}==0066, GROUP=dialout,
MODE=0664
ATTRS{idVendor}==054c, ATTRS{idProduct}==0095, GROUP=dialout,
MODE=0664
ATTRS{idVendor}==054c, ATTRS{idProduct}==009a, GROUP=dialout,
MODE=0664
ATTRS{idVendor}==054c, ATTRS{idProduct}==00da, GROUP=dialout,
MODE=0664
This differs from the rules I was using for F7:
$ head /etc/udev/rules.d/60-libpisock.rules # $Id:
60-libpisock.rules,v 1.4 2007/02/16 18:26:41 desrod Exp $
#
# udev rules file for pilot-link's libpisock library, enabled for libusb
#
SUBSYSTEMS!=usb, ACTION!=add, GOTO=libpisock_rules_end
# Sony handheld devices
ATTRS{idVendor}==054c, ATTRS{idProduct}==0038, MODE=0664,
RUN+=/sbin/pam_console_apply -c
/etc/security/console.perms.pilot-link $env{DEVNAME}
ATTRS{idVendor}==054c, ATTRS{idProduct}==0066, MODE=0664,
RUN+=/sbin/pam_console_apply -c
/etc/security/console.perms.pilot-link $env{DEVNAME}
ATTRS{idVendor}==054c, ATTRS{idProduct}==0095, MODE=0664,
RUN+=/sbin/pam_console_apply -c
/etc/security/console.perms.pilot-link $env{DEVNAME}
Even after creating a dialout group and adding my login to it,
there were permission issues using pilot-xfer. Reverting to
the old configuration files from F7 seems to be working.
Matt DaveyCannibalism is a particularly antisocial form of behaviour.
[EMAIL PROTECTED]-- In Cannibalism: ecology and evolution among
diverse taxa, Oxford University Press, 1992
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Home - Office Sync
Sorry for top posting. Rusty gives a good run through of some examples of syncing to two computers. The main effect is that if you have made changes to a record on the palm and on the sync target, the changed records should be duplicated. If you are syncing to two different machines and make changes on the desktops as well as your Zire, this duplication could happen quite frequently. Matt On Wed, 2007-11-07 at 14:57 -0700, Rusty Carruth wrote: Well, I don't think I've missed any replies, so here goes mine. Sorry if I *did* miss a reply and this is a waste of everyone's time! Daniel Rindt wrote: Hello List, iam using Zire31 with gpilot :). My Question is, can i sync on 2 Places without Problems? I want sync in Office to Zire and at Home and back. Is that possible without Problems? I think you mean - can you sync at home to one computer, and then sync at work with a different computer, and will you have problems. Lets consider the situation. Say that the Zire has items a, b, and c. When you start, Home has none of the file,s and neither does work. You sync at home, now : Zire a, b, c Home: a, b, c Work: empty Now, you go to work and sync, so work has a, b,c Now, you change 'a' on the Zire, and sync at work: Zire:a1, b, c Home: a, b, c Work, a1, b, c Now, you go home and change 'b', then sync: Zire:a1, b1, c Home: a1, b1, c Work: a1, b, c Go back to work, change c, sync: Zire: a1, b1, c1 Home: a1, b1, c Work: a1, b1, c1 Note that, as long as you do not change the files on home or work, you are pretty safe here. So, what happens if you start changing the files on the 'backup' machines (the non-zires)? Starting from the above, lets go home and change c there (creating c'), then sync. OOPS! We just wrote c', which loses the changes we made to get c1! Probably not what you wanted :-) Hope this helps, and isn't TOO far off the mark! ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gpilot sync crash by syncing the ToDo
Daniel, Glad that we have a diagnosis. I have added a note to the redhat bugzilla ticket to suggest that the required patch could be added to the evolution package for fc7. There is no evolution release on the 2.10.* line that includes the patch, which was committed in September. I think you would need 2.11.92+ or 2.12.x. Matt On Fri, 2007-11-02 at 19:30 +0100, Daniel Rindt wrote: Am Freitag, den 02.11.2007, 09:02 + schrieb Matt Davey: On Thu, 2007-11-01 at 19:55 +0100, Daniel Rindt wrote: Hello List Members, iam not sure if my problem is belonging to this list. but iam try to find help here. As Attachment i had sended a backtrace from bugbuddy. they collects the output after gpilotd is crashing by doing a sync. Many thanks for helping me. Daniel, Greetings Matt, Is this bug reproducible? Iam not sure. What data should i provide? If so, can you avoid the bug by disabling the 'todo' conduit? Yes, if the plugin disabled then works fine. If so, do you have any 'todo' entries that have no 'due date'? Yes. You may be affected by a bug in the evolution todo conduit that is discussed here: https://bugs.launchpad.net/bugs/81170 This bug has been fixed in the evolution code base, but might not yet be available in fc7. I'm setting now a due-date on each task and it works now. seems that my problem is belonging to this bug. fc7 contains the following versions from evolution and gpilot: gnome-pilot-2.0.15-5.fc7 gnome-pilot-conduits-2.0.15-3.fc7 evolution-data-server-1.10.3.1-2.fc7 evolution-2.10.3-4.fc7 in which version is this bug fixed? Matt - thanks for the information. Daniel Matt Daniel ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt Davey If I have not seen as far as others, it is because giants [EMAIL PROTECTED] were standing on my shoulders. -- Hal Abelson ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Home - Office Sync
On Fri, 2007-10-19 at 16:13 +0200, Daniel Rindt wrote: Hello List, iam using Zire31 with gpilot :). My Question is, can i sync on 2 Places without Problems? I want sync in Office to Zire and at Home and back. Is that possible without Problems? If you make changes to the same records at home and at the office you can be left with duplicate records that you need to clean up yourself. But that's better than losing changes, which is why it works like that. Other than that, things should work as you expect. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: MAL conduit doesn't work
Hi, Ridiculously tardy response (almost 8 months) but here goes. On Wed, 2007-02-28 at 14:12 -0500, David A. Desrosiers wrote: On Wed, 2007-02-28 at 12:03 -0600, Stuart Luppescu wrote: For some reason, the MAL conduit hasn't worked since last summer. In fact, trying to sync with MAL used to crash gpilotd, so I disabled it. I recently upgraded to gnome-pilot (and conduits) 2.0.15 so I tried MAL again. It didn't crash, but I'm now getting these messages: I'm sure it hasn't been ported to the changes in pilot-link 0.12.x that have been released in the last handful of versions. Quite a lot has changed and mal needs to be updated. The mal-conduit code in gnome-pilot was forked years ago and was updated in time for gnome-pilot-conduits 2.0.15. I checked my user name and password on the avantgo web site, and made sure they were what was entered in the Avantgo settings dialog on my Palm, but no success. I have just dusted off my avantgo setup and successfully synced with gnome-pilot 2.0.15. Make sure you are using an up to date version of libmal.prc, avantgo.prc and MobileLink.prc which you can get from the Avantgo website (just install the windows .exe and you'll find the .prc files installed under the Avantgo folder). The OS4 versions I used to use crashed on my OS5 Clie. After installation I opened up the AGConnect app on the palm and put in 'sync.avantgo.com' on port 80, filled out my username and password, and successfully synced. Hope it works for you, Matt Matt Davey Numeric stability isn't that important when you're guessing. [EMAIL PROTECTED] ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
RE: z22 F7 problem
On Wed, 2007-10-10 at 15:17 -0700, Reitsma, Rene - COB wrote: Not to confuse matters, but I believe that I once mentioned that my Z22 syncs fine with Ubuntu/gpilot: On Ubuntu: uname Linux skip-bo 2.6.15-29-386 #1 PREEMPT Mon Sep 24 17:18:25 UTC 2007 i686 GNU/Linux This seems to be a kernel problem. I was able to sync fine using the initial fedora-7 installation (kernel 2.6.21-1.3194.fc7). I then updated just the kernel, to 2.6.22.9-91.fc7, and could then duplicate Tom's symptoms (only syncs once per reboot). I'll add to my thread on the hal-list to see if they have any ideas. Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Billiet Sent: Wednesday, October 10, 2007 1:25 PM To: The PalmOSlt; tmgt; integration pacakge Subject: Re: z22 F7 problem - Original Message - From: Evan Time: 10-10-07 22:13 I'm syncing a Z22 on Ubuntu 7.10 beta, and it works fine for me with the visor module on either jpilot or gnome-pilot, as long as I set the device to /dev/ttyUSB1. What version numbers can I provide that might help? Hmm, I couldn't get the z22 syncing anymore with the visor module, whatever I tried. That's why I started working on libusb, which is now partially working. Assuming ubuntu 7.1 is pretty new, I think this will also include a very recent kernel. Can you give me which kernel and which udev version you are using? Kind regards, Tom Billiet ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: palm usb_device doesn't seem to disconnect
On Wed, 2007-10-10 at 18:35 +0100, Matt Davey wrote: Dear all, There have been reports that gnome-pilot can only sync once after each reboot. Recently a user seems to have tracked this down to HAL behaviour, in which the 'device_added' event only fires once, even if the palmos device is physically unplugged from the host. This doesn't sound right to me. I wonder if this behaviour is a known regression in HAL, or is it intended for some reason I'm not fathoming? Apologies if this is a FAQ - I didn't spot it after a quick scan through the list archives for the last couple of months. System info from the reporter: hal: 0.5.9.1 hal-info: 0.20070831 kernel: 2.6.22-ARCH udev: 115 The gnome-pilot-list thread is here: http://mail.gnome.org/archives/gnome-pilot-list/2007-October/msg00022.html Further update: I have now reproduced this problem myself and have narrowed it down to a regression between two kernel versions: I was able to sync fine using the initial fedora-7 installation (kernel 2.6.21-1.3194.fc7). I then updated just the kernel, to 2.6.22.9-91.fc7, and could then duplicate Tom's symptoms (only syncs once per reboot). 'lshal' retained the info on the 'usb_device' entry even after disconnecting my palmos device. Again, is this a known issue? Should I take to greg-k-h? Thanks, Matt Matt Davey Did you hear about the new corduroy pillow? [EMAIL PROTECTED] It's making headlines all over town. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: palm usb_device doesn't seem to disconnect
On Thu, 2007-10-11 at 10:27 +0100, Bastien Nocera wrote: On Thu, 2007-10-11 at 10:19 +0100, Matt Davey wrote: On Wed, 2007-10-10 at 18:35 +0100, Matt Davey wrote: Dear all, There have been reports that gnome-pilot can only sync once after each reboot. Recently a user seems to have tracked this down to HAL behaviour, in which the 'device_added' event only fires once, even if the palmos device is physically unplugged from the host. [...] Further update: I have now reproduced this problem myself and have narrowed it down to a regression between two kernel versions: I was able to sync fine using the initial fedora-7 installation (kernel 2.6.21-1.3194.fc7). I then updated just the kernel, to 2.6.22.9-91.fc7, and could then duplicate Tom's symptoms (only syncs once per reboot). 'lshal' retained the info on the 'usb_device' entry even after disconnecting my palmos device. Again, is this a known issue? Should I take to greg-k-h? I'm not sure this is relevant, but most of my problems with device nodes not going away were fixed with a newer udev (at the time). That was my bug report: https://bugzilla.redhat.com/show_bug.cgi?id=203932 Hmm. As far as I remember, when I reproduced this issue the device nodes did indeed disappear, including the /proc/bus/usb/ entries. It was just the lshal entry that hung around. I can check this evening (12 hours). And it seems to work fine for me. Maybe it's time to go add Bluetooth support to gnome-pilot? :) Sigh... yes we probably should, now that pilot-link supports it etc. Would you be happy to test? There's always network syncing as a workaround... Matt DaveyIf you think education is expensive, try ignorance. [EMAIL PROTECTED]-- Derek Bok ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
palm usb_device doesn't seem to disconnect
Dear all, There have been reports that gnome-pilot can only sync once after each reboot. Recently a user seems to have tracked this down to HAL behaviour, in which the 'device_added' event only fires once, even if the palmos device is physically unplugged from the host. This doesn't sound right to me. I wonder if this behaviour is a known regression in HAL, or is it intended for some reason I'm not fathoming? Apologies if this is a FAQ - I didn't spot it after a quick scan through the list archives for the last couple of months. System info from the reporter: hal: 0.5.9.1 hal-info: 0.20070831 kernel: 2.6.22-ARCH udev: 115 The gnome-pilot-list thread is here: http://mail.gnome.org/archives/gnome-pilot-list/2007-October/msg00022.html Thanks, Matt Davey (gnome-pilot maintainer) Matt Davey I do not know myself, and God forbid [EMAIL PROTECTED] that I should. -- Johann von Goethe ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Problems with file conduit and Treo 680
I have the same timing issues with a Treo 700p, but worse, because if I don't pause the gpilotd daemon before plugging in to charge (no hotsync), it infinite-loops. With pilot-xfer, I need to hit hotsync 1-5 seconds before running pilot-xfer. This is with libusb instead of visor, I can't get visor to work at all with the 700p. Adam, Do you get into an infinite loop if you start pilot-xfer before plugging in the 700p? If not, we should try to find out how gpilotd gets stuck. Have you tried attaching with gdb and seeing what bit of code it is in via a stack trace? I guess the pilot-link people should try to see how they can distinguish the charging connection from a sync attempt... Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: cannot even log in with IIIc
On Mon, 2007-09-17 at 13:14 -0700, Rusty Carruth wrote: Ok, so I've got a Palm IIIc (color) that worked some years ago, with much older software. I had upgraded some time back, and my sync quit working. Hi Rusty, Here's a checklist: 0. What version of pilot-link and gnome-pilot do you have? 1. Can you sync using Windows with your IIIc and the same cables? We need to rule out problems with your cables first. 2. Try getting 'pilot-xfer -p /dev/whatever -l' working first. This is the basic test of linux connectivity. Without this, jpilot/kpilot/gnome-pilot are not going to work. Make sure you kill any gpilotd/gpilot-applet processes before trying pilot-xfer. 3. First try with your DB9 cable. Run pilot-xfer -p /dev/ttyS0 -l, if you're sure you're connected to ttyS0. What do you get? You can try turning on pilot-link debugging by setting the environment variables: env PILOT_DEBUG=DEV SLP CMP PADP NET SOCK \ PILOT_DEBUG_LEVEL=DEBUG pilot-xfer -p /dev/ttyS0 -l 4. As regards USB, connect USB and attempt a sync. If you don't see any palm-related messages with a 'dmesg' command, you are in trouble. I can't see why you wouldn't unless you have a faulty USB cable or hub. Maybe a dead hub port? That should get you started, anyway. Matt So, I upgraded again, to Debian 4.0, hoping that things would get better. OTHER things are very nice, but I still cannot get my Palm IIIc to sync with my Linux/Debian laptop. The charging cable I have has 2 ways to hook it up to the computer: 1 - using 9-pin serial 2 - using USB (which you need if you want to charge your Palm) When I connect the PDA via the DB9 serial to my laptop, start up hotsync on Palm, run kpilot, wait for it to say 'device link ready', then hit 'sync' on the Palm (with Local connection using direct serial) - Palm beeps and says 'Identifying user' then times out. Kpilot says 'Unable to read system information from Pilot' The above is with Kpilot configured to use /dev/ttyS0, which is where I have the PDA plugged in, at 9600 (No workarounds) So, I decide to try USB: Disconnect the DB9 from the laptop, change Pilot Device to 'usb:' (without the quotes, of course), and hit 'sync' on the Pilot. It says 'connecting with the desktop using direct serial' and goes no further. I look in /var/log/interesting log files, and I notice NOTHING relating to the USB port other than 'hub 1-0:1.0: over-current change on port 1' (and I see when I connected my USB mouse about 1/2 hour earlier. In other words, USB works, as I use it for my mouse and my memory stick and my ...). I look in /proc/bus/usb and see only things I expect there (3 hubs and the mouse). I had tried some stuff I found about fiddling with udev and putting visor into the blacklist (for modprobe and/or hotplug), so I tried that before the above usb attempt (actually, I've seen no difference between before and after trying different howtos. I even tried modprobe-ing visor (which loaded, but ddidn't seem to do anything else)... I tried IR once, but have no clue what I'm doing there, so gave up pretty fast. So - given that I want to hotsync my Palm IIIc (color) using Linux, using ANY of the above (serial, USB, IR), does anyone have any ideas/pointers_to_howtos/whatever? Thanks! rc ps - the above info is INTENDED to go to the gnome-pilot-list! Unfortunately, I have NO CONTROL over the stupid disclaimer below, which should NOT go out with this email, but which I cannot stop.. sorry about that, please ignore the below silly disclaimer: ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list Matt DaveyBeware of Greeks bearing gifts - but [EMAIL PROTECTED] Don't look a gift horse in the mouth. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Some records not synced to the palm
On Fri, 2007-09-14 at 11:50 +0200, Gregor Hlawacek wrote: On Wed, 2007-09-12 at 12:24 +0100, Matt Davey wrote: On Fri, 2007-09-07 at 09:15 +0200, Gregor Hlawacek wrote: On Fri, 2007-09-07 at 07:12 +, Gregor Hlawacek wrote: Hi! I am using gpilotd 2.0.15 together with pilot-link 0.12.2 Using libusb I can sync my TX. However, some of the refords are not synced. I have to correct my self it seems that nothing at all is synced from evolution to the palm whereas the other direction works. hi! thanks for the hint Looks like an instance of: http://bugzilla.gnome.org/show_bug.cgi?id=429423 which should be fixed by the recent commit for bug 201167: http://bugzilla.gnome.org/show_bug.cgi?id=201167 I tried to apply the patches to evolution 2.10.2 but failed for the first one the second worked. I am not sure I don't completly understand the corresponding messages if I have to also apply the first patch (evo.patch). It is complaining about a large number of missing files. However, category syncing no works. Still nothing is synced from the calendar to the pilot. The error stays the same Nathan and Tom are probably the authorities on this one. If possible, I'd suggest trying the recently released Evolution 2.11.92. I don't know whether all required patches were attached to bug 201167. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Some records not synced to the palm
On Fri, 2007-09-07 at 09:15 +0200, Gregor Hlawacek wrote: On Fri, 2007-09-07 at 07:12 +, Gregor Hlawacek wrote: Hi! I am using gpilotd 2.0.15 together with pilot-link 0.12.2 Using libusb I can sync my TX. However, some of the refords are not synced. I have to correct my self it seems that nothing at all is synced from evolution to the palm whereas the other direction works. Looks like an instance of: http://bugzilla.gnome.org/show_bug.cgi?id=429423 which should be fixed by the recent commit for bug 201167: http://bugzilla.gnome.org/show_bug.cgi?id=201167 Which has gone in to Evolution 2.11.92. Matt Matt Davey I do not know myself, and God forbid [EMAIL PROTECTED] that I should. -- Johann von Goethe ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Pilot synch issues
On Wed, 2007-09-12 at 09:45 +0200, Frederic Crozat wrote: Le mercredi 12 septembre 2007 à 09:59 +1000, Andrew Greig a écrit : Date: Tue, 11 Sep 2007 09:32:07 +0200 From: Frederic Crozat [EMAIL PROTECTED] Subject: Re: Pilot synch issues To: The PalmOSlt; tmgt; integration pacakge gnome-pilot-list@gnome.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-15 Le mardi 11 septembre 2007 ? 08:55 +1000, Andrew Greig a ?crit : Hi, I have now installed Mandriva 2007 PWP on a spare hard disk. Clean install - no dual boot, no errors reported. Installed evolution-pilot via urpmi (Disk 4) and set up Synchronisation options as usb(Radio button) usb: and a speed of 57600. No synch and connection timed out. I don't see the point in testing with 2007.0, anyway. And also make sure you have the latest kernel available as update for 2007.0. It just seemed the quickest way to get a clean slate. And no worries about data loss as it was not my main drive. But you are still not running with all bugfix / security update, on both of your system. You haven't the latest evolution bugfix update for 2007.1. What now, please? How about running pilot-xfer -p usb: -l while logged as a user (while making sure gpilotd is not running) and try to run sync on your Palm and see what pilot-xfer says ? bash-3.1$ pilot-xfer -p usb: -l Listening for incoming connection on usb:... No response to hot synch button. I've been away for a while and am just catching up on gnome-pilot-list... Apologies if I've missed something earlier in the thread. Andrew, have you tried playing with the timing of starting 'pilot-xfer' and pressing initiating the sync on the palm? In the recent Newbie questions thread, the user eventually managed to sync his Treo 700p by starting the sync _just_before_ running the pilot-xfer command. This was with a libusb setup. Other than that, Frederic is probably better placed to help you troubleshoot problems with a Mandriva distribution. Matt Did you ensure visor module didn't get loaded on your system (with /sbin/lsmod) when after you pressed sync ? (it should but it is best to ensure that) . Did you switch back your PalmDrive to non Drive mode ? And it would be great if you could reply to your emails when you post a follow-up, so threading is kept. I apologise for that. When I was working in the 2007 drive I had no access to the thread, but it seemed there was much to cut and paste from the console. I will confine myself to replies from this drive (2007.1) from now on. Still broken. Matt DaveyPornography: It's not the teat, it's the tumidity [EMAIL PROTECTED] -- William Safire ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: etodo and ememo not synchronizing at all
On Mon, 2007-03-19 at 01:19 +0100, Marcio Cordero wrote: Am Donnerstag, den 15.03.2007, 18:15 -0700 schrieb Nathan Owens: --- Marcio Cordero [EMAIL PROTECTED] wrote: Hi all I have this very strange problem for a long time and would finally like to find an answer. I can sync prefectly my calendar and contacts but not my memos and todos. I hard-resetted my palm a few days ago and did a copy to PDA sync in the hope of solving the problem: It did copy but since then, it's the old story: not able to sync and not working even if I try to copy to PDA or to the PC. Syncing doesn't show any errors at all and sometimes todos get synced but if it ever happens, it's always randomly and happens from the palm to the PC. I setup ememo and etodo to sync private records as well. I'm synchronizing through USB cable. You may be interested that this bug is probably an instance of: http://bugzilla.gnome.org/show_bug.cgi?id=201167 a solution for which has gone in to Evolution 2.11.92. Matt Matt Davey You can't have everything. Where would you put it? [EMAIL PROTECTED] -- Steve Wright ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Problems importing data with palm
On Sat, 2007-05-26 at 11:28 +0200, Xavier Pegenaute wrote: Dear, I was trying to use gnome-pilot with OpenSuse 10.2, and it seems that is working but only extract empty data from pilot. The output from gpilotd is this one: - (gnome-pilot:11164): eaddrconduit-WARNING **: Address has only one line: [] eaddrconduit-Message: Syncable eaddrconduit-Message: delete_record: delete ['' '' ''] (gnome-pilot:11164): eaddrconduit-WARNING **: Address has only one line: [] eaddrconduit-Message: Syncable eaddrconduit-Message: delete_record: delete ['' '' ''] eaddrconduit-Message: for_each ending eaddrconduit-Message: add_record: adding ['' '' ''] to desktop eaddrconduit-Message: add_record: adding ['' '' ''] to desktop ... --- Repeated for every contact that I have in my palm. I am thinking that it has to be in relation with the pattern matching of the fields in the record, exactly with the possibility of language name fields. Actually my palm is running in English language, and my computer is working in Spanish environment. Any one know how can I obtain more info? or how to fix this problem? You could try setting the PILOT_CHARSET environment variable (see my previous post to this list). This may help by ensuring correct translation of address text, but I don't hold out much hope (incorrect charset should give you incorrect characters, not empty strings). I have been trying to take look to the source code but I did not found this conduit in the svn (conduits) neither in gnome-pilot svn. The evolution conduits are part of the Evolution svn tree. Thanks Regards. You're welcome, Matt Matt DaveyMany hands make light work - but [EMAIL PROTECTED] Too many cooks spoil the broth. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: can't sync with Tungsten T2
I've heard lots of people say that the cables cause problems. I don't think it's the physical cable that causes the issue, but syncing over usb that is unreliable. I know I can't get my Treo 680 to sync via the cable (or at best it's very intermittent) but it works over bluetooth pretty reliably (bar the timezone issue!). Can you try a sync via bluetooth? Or over the network somehow? You might have more luck. I've no idea what causes the issues over the cable, but others on the list will know more than me. Cheers - Callum. daz wrote: I found Bug #66355 gpilotd locks up my Palm Z22 and (after installing pilot-xfer) have tried [EMAIL PROTECTED]:~$ pilot-xfer -p /dev/pilot -l Listening for incoming connection on /dev/pilot... But nothing happens. I don't think that its the cable, as the charging light is on, and /dev/pilot is definitely created when I hit the hotsync button. One thing worth checking is whether /dev/pilot is getting linked to the right ttyUSB device. Usually /dev/pilot does the right thing, but given that you are getting a -202 aka timeout error from pilot-link, I would try replacing /dev/pilot with both /dev/ttyUSB0 and /dev/ttyUSB1. You can also try with pilot-xfer -p /dev/ttyUSB0 -l. Your sync is not getting as far as connecting to the T2, so your immediate problem doesn't seem to lie with the conduits. Matt Darren On Sun, 2007-08-19 at 09:02 +1000, daz wrote: I removed the applet, ran a killall gpilotd, started gpilotd manually, then hit the hotsync button: [EMAIL PROTECTED]:~$ /usr/bin/gpilotd gpilotd-Message: gnome-pilot 2.0.15 starting... gpilotd-Message: compiled for pilot-link version 0.12.1 gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] gpilotd-Message: Activating CORBA server gpilotd-Message: bonobo_activation_active_server_register = 0 gpilotd-Message: Watching Cradle (/dev/pilot) gpilotd-Message: Found 4766, 0001 gpilotd-Message: Using net TRUE gpilotd-Message: Found 0502, 0736 gpilotd-Message: Using net TRUE gpilotd-Message: Found 091e, 0004 gpilotd-Message: Using net TRUE lots of these then, gpilotd-Message: Using net TRUE gpilotd-Message: Found 12ef, 0100 gpilotd-Message: Using net TRUE gpilotd-Message: setting PILOTRATE=57600 (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to returned -202: Resource temporarily unavailable (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs Then I disconnected the PDA: gpilotd-Message: Client seems ok gpilotd-Message: Client seems ok gpilotd-Message: monitor_on(pilot_name=PalmT5,client_id = IOR:01001b00...) gpilotd-Message: corba: notify_on(event_type=CONNECT,callback=IOR:01001b00...) gpilotd-Message: corba: notify_on(event_type=DISCONNECT,callback=IOR:01001b00...) gpilotd-Message: Shutting down devices gpilotd-Message: Rereading configuration... gpilotd-Message: Watching Cradle (/dev/pilot) Now I disable all the conduits and hit the hotsync button: gpilotd-Message: setting PILOTRATE=57600 (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to returned -202: Resource temporarily unavailable (gnome-pilot:29864): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs Now its frozen again and I'm not getting the same stuff as above when I disconnect the PDA (dunno what happened there...). On Sat, 2007-08-18 at 18:34 +0100, Matt Davey wrote: I've just recently installed Ubuntu 7.04 from a downloaded CD image. I'm running on an IBM A31 laptop. Gnome-Pilot-Applet is 2.0.15 I've been unable to sync my Palm Tungsten T2 via the USB port. It just freezes completely and requires a soft reset to come back to life (even the light that indicates that its charging stays on!). Have you downloaded all available updates for your Ubuntu installation? There are several bugs this could be, including: https://launchpad.net/ubuntu/+source/gnome-pilot/+bug/19528 As suggested, you can run gpilotd in a terminal to get more information about where it crashes. My guess is that it is crashing in the Evolution calendar conduit. If you're not sure, try disabling all the conduits and see if you can sync. If that works, try re-enabling them one at a time to narrow it down. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list ___ gnome-pilot
Re: can't sync with Tungsten T2
I've just recently installed Ubuntu 7.04 from a downloaded CD image. I'm running on an IBM A31 laptop. Gnome-Pilot-Applet is 2.0.15 I've been unable to sync my Palm Tungsten T2 via the USB port. It just freezes completely and requires a soft reset to come back to life (even the light that indicates that its charging stays on!). Have you downloaded all available updates for your Ubuntu installation? There are several bugs this could be, including: https://launchpad.net/ubuntu/+source/gnome-pilot/+bug/19528 As suggested, you can run gpilotd in a terminal to get more information about where it crashes. My guess is that it is crashing in the Evolution calendar conduit. If you're not sure, try disabling all the conduits and see if you can sync. If that works, try re-enabling them one at a time to narrow it down. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Syncing one of multiple calendars
On Wed, 2007-08-15 at 00:06 +0100, Callum Macdonald wrote: G'day, Thanks for the great work on gpilot, it's a life saver for palm users like me who switched to Linux. Now that's always a good opener :) I have 4 calendars in Evolution. Three local, one web. I've just got a new Treo 680 and I'm having the same problem that I had with my previous Treo 650. The calendar will sync once and only once. After that, I can't get data to move from the treo to the pc or the other way. I've tried synchronise, copy from pda, and copy to pda but none of the options have any effect on either my pc or my pda. Weird. The first thing to do is to start 'gpilotd' from a terminal window. That should let you see some messages indicating why the conduit is running into problems. To do this, remove the applet from the panel (the little 'sync' icon that changes colour when syncing), then open a terminal window and run '/usr/libexec/gpilotd', or '/usr/bin/gpilotd'. It might live somewhere else on your distribution, I guess. The other information that will be relevant is to tell us which version/package of the following components you have installed: gnome-pilot evolution evolution-data-server pilot-link That should be a good start. Matt Matt Davey It takes one drink to get me drunk, but I can't [EMAIL PROTECTED]remember if it's the 13th or 14th -- George Burns ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Help with palm
On Mon, 2007-06-25 at 17:05 -0700, Nathan Owens wrote: --- Nathan Owens [EMAIL PROTECTED] wrote: I haven't been able to find the OpenSuSE source for Evolution 2.8.3, but I have found it for 2.8.2 at http://download.opensuse.org/distribution/10.2/repo/src-oss/suse/src/. It has a patch for pilot-link 0.12, so I'll start there. Hopefully it will turn something up. To reply to my own e-mail: I looked at the 2.8.2 version of the OpenSuSE source code, and it seems that EAddress and the other conduits seem to be broken. Of course, I may be wrong because I had to manually apply the patches, but I'm seeing over at Novell that this is definitely happening: https://bugzilla.novell.com/show_bug.cgi?id=235668. I've posted basically the information below on the bug site as well. One reason for the failure is that local_record_to_pilot_record() and ecard_from_remote_record() were not converted to use the pi_buffer_t structure. The function calls to the pilot-link functions pack_Address() and unpack_Address() haven't been converted from pilot-link 0.11.x to 0.12.x. Mainly, I think the problem stems from the fact that they need to completely update the patch. The name of the patch in the source RPM is evolution-2.2.0-port-to-pilot-link-0.12.patch, so it's pretty old (and probably based on a preX build). I'll be attaching a patch at the the Novell bug site soon. It's basically going to be taking the original patches for the pilot-link conversion and remove the pilot-link 0.11.8 pieces of the code. This will leave only the 0.12 pieces of the pilot-link code in the conduits, which should allow the Evolution conduits to compile directly on OpenSUSE 10.2 and above. Great stuff. What a mess! Thanks for digging in to this one. Matt Matt Davey What the world needs is more good readers, [EMAIL PROTECTED] not more good writers. -- Borges. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Help with palm
On Mon, 2007-06-25 at 04:38 -0700, Nathan Owens wrote: Let's try this again - sorry for the delay (thanks for e-mailing me about not getting a response - much better than letting this die). --- Xavier Pegenaute [EMAIL PROTECTED] wrote: Ok, About the personal data in the pdb file, in the last mail I have not written all the output, after these strings there was my contacts data. OK. That's good that the information is there. My palm is the LifeDrive model. Matt: have you heard of problems with the LifeDrive? I remember seeing something on the list a while ago (though I don't think it was related to this problem), but nothing comes up when searching the archives. There used to be some issues on the pilot-link side, related to the fact that the LiveDrive has a hard disk that maintains a USB connection all the time, not just during a sync. I don't know much more than that, and it doesn't sound particularly related. I haven't unpacked the evolution 2.8.3 tarball, but it is dated Jan-29, which is after the pilot-link 0.12 patch was applied to the trunk (Jan 8). As there's no 2.8.3 label that I can see, it's just possible that it includes the patch? Otherwise, best look at the evo source package from SuSE... [snip] Matt Matt Davey By doing just a little every day, I can gradually let the [EMAIL PROTECTED] task completely overwhelm me. -- Ashleigh Brilliant ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot and pilot-xfer restore don't work
On Thu, 2007-05-03 at 11:22 -0400, David A. Desrosiers wrote: On Thu, 2007-05-03 at 16:18 +0100, Matt Davey wrote: I tried rmmod visor but got the same dialog again. visor will be reloaded by udev when you attempt a sync, unless it is blacklisted... I don't think this is true, unless udev changed behavior very recently But Adam had rmmod'ed visor... so I guess visor would be reloaded on the next sync. I didn't mean to imply it would be reloaded if already present! to facilitate this. What happens if you have 4 Palm devices (or 7 or 30) all synchronizing across the various visor interfaces, and all of them completing at different times? If visor was reloaded when the first one completed, or when one disconnected prematurely, etc... it would cause bad mojo ;) Matt Davey What do you get the man who has everything? [EMAIL PROTECTED] A burglar alarm. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot and pilot-xfer restore don't work
On Fri, 2007-05-04 at 07:43 -0400, David A. Desrosiers wrote: On Fri, 2007-05-04 at 06:21 -0400, Adam C Powell IV wrote: But the udev auto-loading visor is the only explanation that makes sense... I just tried blacklisting visor and adding the 60-libpisock.rules file to /etc/udev/rules.d as described in the README, did /etc/init.d/udev restart (even rebooted), but it doesn't work: connecting the device always loads visor and interferes with libusb. :-( A few things come to mind: If you blacklisted visor, removed it, restarted udev and its STILL loading, then its being loaded by something else. A cron job? Something else in /etc/modules? Something distribution-specific? I'd rgrep /etc/ for visor and see what comes up. re. distribution-specific: did you use the right location for your blacklist file? Not sure what's right in your case... I guess you could restart udev and check the access time on your blacklist file gets updated (ls -lu). Now I have another problem: a 700p which doesn't restore at all with usbserial. I haven't seen anything on the pilot-link or gnome-pilot lists on this, and the web is not much help. Did you add the 700p's vendor/prod structures to the .rules for for udev using pilot-link? I don't think we've ever had a user with a 700p before using udev, so that entry may need to be updated so that libusb can hook in and handle it at connect time (likewise for the visor module, that'll need to be updated and rebuilt as well; it doesn't require a kernel rebuild, you can just build and install the patched module directly). Alternatively, you should be able to do: modprobe visor vendor=0x0830 product=0x61 (use the correct vendor/product IDs for your 700p -- you can use lshal during a sync attempt to find the IDs). Matt If people have ideas on getting libusb to work I'm happy to keep trying for a couple of days, but fortunately they also gave me a fixed 600 to fall back on. If you rmmod visor, cradle your Palm device, and hit HotSync... does the system log show any visor-related messages at all? If so, then I'd backtrack from there and see why. Also, make sure you're running a current version of udev. I'm running 108-0ubuntu4 here and it works great. You don't need the latest bleeding edge version (and DO NOT build it from source and try to install it yourself, you will break things). You just need something current. If you're still having trouble, catch me/us on irc and we'll help real-time; irc.pilot-link.org, port 6667 for cleartext, 994 for ircs. Matt Davey Wagner has lovely moments but awful quarters of an hour. [EMAIL PROTECTED] -- Gioacchino Rossini. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: gnome-pilot and pilot-xfer restore don't work
Hi Adam,
On Wed, 2007-05-02 at 08:28 -0400, Adam C Powell IV wrote:
Hello again,
[gnome-pilot specific so I'm not copying pilot-link-devel]
On Mon, 2007-04-30 at 07:28 -0400, Adam C Powell IV wrote:
Greetings,
I'm having trouble restoring a Treo 600 (PalmOS V5.2H) using gnome-pilot
and pilot link in Debian etch (2.0.15-2 and 0.12.1-5 respectively).
First, the Restore... menu item in the gnome-pilot applet menu seems
completely useless. The ellipsis suggests a follow-on dialog, but there
is none, nor any menu item check, nor any other indication that it has
been selected. Furthermore, whether I use it or not, it tries to sync
the pilot, unless it has just been blanked, in which case it tries to
restore it, so Restore... has no discernible effect whatsoever.
It's embarrassing to admit (as I'm the gnome-pilot maintainer...), but I
don't think I've ever tried the 'Restore...' applet option. I'm not
sure what it's supposed to do: possibly it's supposed to allow you to
choose which backed-up state to restore onto the next device to connect
-- i.e. click 'Restore', then you're invited to sync a device and it'll
get overwritten with the previously backed-up data. But don't quote me
on that.
Second, gnome-pilot always hangs while restoring the device, going up to
100% CPU and sitting there until the Treo times out. If I move aside
the file which seemed to cause this, it hangs on another file, and so
on. This behavior is identical to that reported by Krzysztof Porowski
four years ago, and nobody followed up to his questions, nor has this
problem been addressed since. This is also Debian bug #146346 reported
five years ago next week, and forwarded to this list, but with no
helpful or corrective replies. gnome-pilot restore is very broken.
... in your case, certainly. I have used the restore feature several
times recently without problems. I wasn't aware of this bug, and would
be a bit surprised if it was entered into gnome-pilot bugzilla. I don't
know what's at the root of the problem, but will try to reproduce it
myself for starters. As I said, I've definitely had recent success with
restore to a palmv over serial a connection.
My Treo hard crashed again yesterday (replacement on the way), so I got
a chance to try this out with strace. It is hanging on Installing
Blazer Cache... and strace leading up to that shows:
open(/home/hazelsct/MyNewPilot/Blazer Cache.pdb, O_RDONLY) = 41
fstat64(41, {st_mode=S_IFREG|0644, st_size=2821647, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb6c8e000
fstat64(41, {st_mode=S_IFREG|0644, st_size=2821647, ...}) = 0
[...]
select(40, [39], NULL, NULL, {30, 0}) = 1 (in [39], left {30, 0})
read(39, \1\253\0\0\0\n, 6) = 6
select(40, [39], NULL, NULL, {30, 0}) = 1 (in [39], left {30, 0})
read(39, \241\1\0\0 \4\0`\240\0, 10) = 10
writev(38, [{GIOP\1\2\1\0\200\0\0\0, 12},
{\220\220\324\277\0\0\0\0\0\0\0\0\34\0\0\0\0\0\0\0c\274..., 128}], 2) = 140
_llseek(41, 36864, [36864], SEEK_SET) = 0
_llseek(41, 36864, [36864], SEEK_SET) = 0
_llseek(41, 36864, [36864], SEEK_SET) = 0
_llseek(41, 36864, [36864], SEEK_SET) = 0
_llseek(41, 36864, [36864], SEEK_SET) = 0
_llseek(41, 36864, [36864], SEEK_SET) = 0
then the llseek() repeats indefinitely. If I move Blazer Cache out of
the way, it hangs on another file.
Any ideas?
Have you tried using a different connection type? Try a network sync,
if you can configure that with your Treo. Failing that, have you tried
both a libusb sync and a usbserial sync?
Matt
Matt Davey What do you call a fish with three eyes?
[EMAIL PROTECTED] A fiiish.
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: etodo and ememo not synchronizing at all
On Fri, 2007-04-27 at 12:17 +0200, Marcio Cordero wrote: Hi Veerapuram nope, it doesn't crash. Since I last tried I reinstalled everything and even deleted every gpilot file in my home directory. At the beginning I could easily sync. Today I made a new task on the palm and tried to sync. Now, gpilotd crashes. After installing bug-buddy, I saved the bug report. Do you need the whole thing? I post the end here and attach the file. The versions may have changed (I' using Mandriva 2007 spring now): Evolution 2.10.0 and gnome-pilot-conduits 2.0.15, pilot-link 0.12.1 Palm device: Treo 650 with orange customizations. [] #38 0x0022 in ?? () No symbol table info available. #39 0x in ?? () No symbol table info available. #0 0xbfffe410 in __kernel_vsyscall () The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] snip It starts ages before with different hex numbers like the ones above... I hope this helps debug. A stack trace like this isn't much help, unfortunately. A developer needs a stack trace with debugging symbols in order to find out what code is implicated. You can find details of how to get a full stack trace here: http://live.gnome.org/GettingTraces You'll want to install debug packages for gnome-pilot, gnome-pilot-conduits, pilot-link, and evolution*, for starters. Matt Davey The journey of a thousand miles begins with [EMAIL PROTECTED] a broken fan belt and a leaky tire. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: New to the list, simple question I hope
Hello Everyone! I'm using Ubuntu. Sync is setup fine. How do I install files to the palm? What files do you want to install? If you want to install a prc or a pdb file, you can open a terminal window and use: gpilot-install-file --now file.prc Alternatively, you should be able to drag and drop a prc or pdb file onto the 'sync' applet icon in the panel bar. Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: problem syncing on OpenSUSE 10.2
Problem solved. That's great. given that OpenSUSE 10.1 with garnome 2.16.2 installed inside worked for syncing..I got to thinking why not try build the evolution-2.8.2.1 and evolution-pilot-2.8.2.1 rpms using the src it compiles. so I did... I used the spec file from the OpenSUSE 10.2 distribution and applied the 4 patches that the garnome installer applies...took about 3 hours. I then rpm -Uvf the 2 new rpms and oualla...now I can sync my treo. I tried modifying records on the treo and synchronizing - it picks em up now. Intriguing. I guess that means the problem is somewhere in the evolution source RPM. The most likely culprit is the porting of evolution conduits to the pilot-link 0.12 API. I took a look at the garnome distribution, and it includes a evolution-2.5.4-fix-conduits.patch. I'd be interested in comparing that patch to the changes made in the Suse patch. Where should I post these rpms? If you can put them up somewhere temporarily I'd be happy to host them on my downloads site. We could then put a link up on the wiki. Mail me privately and we'll sort it out. others may find em helpful. I expect they will. And time-saving :) You should also inform Suse by raising a bug if you haven't already: http://en.opensuse.org/Submitting_Bug_Reports Good sleuthing... Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: SLED 10 gnome-pilot doesn't communicate with my Treo 600
In a nutshell, pilot-xfer -p /dev/pilot -L works (I get a nice list of all the DB's on my Palm) but gnome-pilot doesn't seem to do anything during initial configuration. When I run gnome-pilot I tell it my palm is on /dev/pilot, which it is, and I have the necessary rights as I've changed udev to set permissions of 777 on ttyUSB* devices. Not sure what output to give, as no errors are produced. My phone simply times out and there's no output past the point in the gnome-pilot applet wizard where it tells me to turn on my palm device to read the user name already stored on it. Okay, if you've got pilot-link working then there shouldn't be any big problems getting gnome-pilot to work. First of all, what version of gnome-pilot are you running, and what palm device do you have? Does your palm device display any error messages or does it just sit there and time out? If gnome-pilot can't manage to read the user-name and device ID from your palm device, then it usually means that your device has a USB device/vendor ID pair that isn't a known device. This could happen with a new device and/or an old-ish version of gnome-pilot. The other thing that can happen is that there are timing problems between the device attempting a sync and udev creating the device. One thing you could try, to investigate this, is to stop the hald process just before you start gpilotd (in then uses a different method of detecting USB devices). The best thing to do is: 1. exit any running gnome-pilot applet in the taskbar. 2. kill any running 'gpilotd' process 3. start 'gpilotd' by hand in a terminal window. It usually lives either in /usr/libexec or /usr/bin 4. Now start up gpilotd-control-applet in another terminal window and try to config. Console messages will appear at the terminals, which may give you some hints. Also, it can be worth changing the 'timeout' value for the device in the configuration applet. Settings 0, 2, 10, 100 should span all behaviours. Let us know how you get on, Matt ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Re: Uuploading files to a palm - How to?
On Mon, 2007-01-22 at 13:08 +0100, Adriano wrote: How can I upload files from the computer to the Palm (a Palm m500 PDA)? I might be a bit dense, but the obvious didn't work. I'm not sure what the obvious approach was... You should be able to drag a .pdb or .prc file onto the panel applet icon. The file should be installed on your next sync. Alternatively, you can use gpilotd-install-file from the command line. Matt Matt Davey The journey of a thousand miles begins with [EMAIL PROTECTED] a broken fan belt and a leaky tire. ___ gnome-pilot-list mailing list gnome-pilot-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
