GNOME Bugzilla – Bug 368824
gpilotd doesn't appear to work with udev
Last modified: 2006-11-01 17:12:04 UTC
Please describe the problem: Prior to using SUSE 10.x /dev wasn't udev. When I upgraded to SUSE 10 and SUSE 10.1 /dev is udev and no gpilotd never seems to connect. pilot-xfer works just fine. Steps to reproduce: 1. use udev 2. setup pilot as USB, 115200, /dev/ttyUSB1 3. try to sync Actual results: >/opt/gnome/lib/gnome-pilot/gpilotd gpilotd-Message: gnome-pilot 2.0.13 starting... gpilotd-Message: compiled for pilot-link version 0.11.8 gpilotd-Message: compiled with [VFS] [USB] [IrDA] [Network] gpilotd-Message: Activating CORBA server gpilotd-Message: bonobo_activation_active_server_register = 0 gpilotd-Message: Watching Treo650 (/dev/ttyUSB1) gpilotd-Message: palm pda detected by HAL gpilotd-Message: setting PILOTRATE=115200 (gpilotd:589): gpilotd-WARNING **: pi_accept_to: Connection timed out (gpilotd:589): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs gpilotd-Message: palm pda detected by HAL gpilotd-Message: setting PILOTRATE=115200 (gpilotd:589): gpilotd-WARNING **: pi_accept_to: Connection timed out (gpilotd:589): gpilotd-WARNING **: pi_accept_to: timeout was 2 secs Expected results: The sync to occur. Does this happen every time? Yes. Other information:
This bug is probably a duplicate of bug 321947. What gnome-pilot package do you have installed? Can you update to gnome-pilot-2.0.13-45.src.rpm or later that should be in SUSE factory? Even better would be 2.0.14.
I have 2.0.13-43 installed. I'll see if I can get the new gnome-pilot installed, although the dependencies might be a problem.
I'm not familiar with how updates are managed in SUSE, but it seems bad that they haven't updated 10.1 to fix this bug. They patched their patch months and months ago. You might want to reopen the SUSE bug: https://bugzilla.novell.com/show_bug.cgi?id=165455 I'm going to close this bug as a duplicate of 321947. Feel free to reopen/update if you have ongoing problems. *** This bug has been marked as a duplicate of 321947 ***
I tried to get the source rpm mentioned in comment #1 and it won't build. config.status: executing intltool commands config.status: executing default-1 commands Configuration : gnome-vfs : yes network sync : yes usb : yes HAL/DBUS : yes gob : yes pilot-link : 0.11.8 + make make all-recursive make[1]: Entering directory `/local/jschewe/rpm/BUILD/gnome-pilot-2.0.14' Making all in po make[2]: Entering directory `/local/jschewe/rpm/BUILD/gnome-pilot-2.0.14/po' cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands make[2]: Leaving directory `/local/jschewe/rpm/BUILD/gnome-pilot-2.0.14/po' make[2]: Entering directory `/local/jschewe/rpm/BUILD/gnome-pilot-2.0.14/po' cd .. \ && CONFIG_FILES=po/Makefile.in CONFIG_HEADERS= CONFIG_LINKS= \ /bin/sh ./config.status config.status: creating po/Makefile.in config.status: executing depfiles commands config.status: executing intltool commands config.status: executing default-1 commands make[2]: *** No rule to make target `@ALL_LINGUAS@.po', needed by `@ALL_LINGUAS@.gmo'. Stop. make[2]: Leaving directory `/local/jschewe/rpm/BUILD/gnome-pilot-2.0.14/po' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/local/jschewe/rpm/BUILD/gnome-pilot-2.0.14' make: *** [all] Error 2 error: Bad exit status from /local/jschewe/rpm/tmp/rpm-tmp.68674 (%build) RPM build errors: Unknown option ? in suse_update_desktop_file() Bad exit status from /local/jschewe/rpm/tmp/rpm-tmp.68674 (%build)
you may be missing gettext?
>rpm -qa | grep gettext gettext-32bit-0.14.5-11 perl-gettext-1.05-11 gettext-0.14.5-11 gettext-devel-0.14.5-11
Don't think I can help much on this problem. Looks like there's something a bit broken with the SUSE source package. You could try downloading gnome-pilot 2.0.14. If it compiles for you out of the box you could see if you can update the source RPM to use the official 2.0.14 instead of the suse version. See also the following bug for a post-2.0.14 tarball that aims to fix some device creation timing issues: http://bugzilla.gnome.org/show_bug.cgi?id=362565 Hope you get through these problems. If pilot-xfer is working reliably, then we should be able to get gnome-pilot going.