Ubuntu
gnome-pilot package

Crashs when syncing with TE2

Bug #43767 reported by Simon Van der Linden
8
Affects Status Importance Assigned to Milestone
gnome-pilot (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-pilot

I'm using bluetooth sync.

After the installation wizar, it recognizes well my user, but when I try to sync, gnome-pilot crashs and let his progress window open, while my Palm is in the "User identification" pass

See original description
Revision history for this message
Matt Davey (mcdavey) wrote :

More info please!
Do you get any error message?
Try starting '/usr/libexec/gpilotd' from a terminal window (you might have to kill any running gpilotd process first using 'killall gpilotd').
Cut and paste the gpilotd output after a crash.

Revision history for this message
Simon Van der Linden (svdlinden) wrote :

ocace# 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]

(gnome-pilot:5809): gpilotd-WARNING **: Number of devices is configured to 0

(gnome-pilot:5809): gpilotd-WARNING **: No accessible devices available

(gnome-pilot:5809): gpilotd-WARNING **: Number of pilots is configured to 0
gpilotd-Message: Activating CORBA server
gpilotd-Message: bonobo_activation_active_server_register = 0

Revision history for this message
Simon Van der Linden (svdlinden) wrote :

In fact, if I start it manually like that, it doesn't crashs and everything goes fine.

But if I only try a sync when I just started my gnome session, it crashs, without any warning or error. The window is blank and my bluetooth connection is "sleeping". Nothing else.

I use gnome-pilot-applet, and I set sync action on memos, address book, calendar and todos.

Revision history for this message
Simon Van der Linden (svdlinden) wrote :

completely unstable,
sometimes it works, sometimes it doesn't

and it doesn't sync all records with evolution, only some of them, without any reason.

Revision history for this message
Matt Davey (mcdavey) wrote :

This may well be related to:
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/39518

i.e. a kernel bug that affects ttyUSB devices. Try upgrading your kernel and see if the problem resolves itself.

Revision history for this message
Simon Van der Linden (svdlinden) wrote :

No, the problem is still there, and my dapper is up-to-date

Revision history for this message
Matt Davey (mcdavey) wrote :

What version is your kernel? Do: 'uname -r' in a terminal. The bug I referred to above claims a problem with 2.6.15 was resolved with a pre-release of the 2.6.17 kernel which has not been officially released yet.

I'm not saying the problem is resolved in up-to-date dapper. I believe there may be a problem with the currently shipped dapper kernel.

Revision history for this message
Daniel Holbach (dholbach) wrote :

A new version (2.0.14) was uploaded to Edgy. It'd be nice if you had a chance to test this and report back, if the problem still persists.

Changed in gnome-pilot:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien Bacher (seb128) wrote :

no reply, closing for now. Feel free to reopen if you have a chance to try the new version and still get that bug with it

Changed in gnome-pilot:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.