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 (Ubuntu)
Status: Needs Info = Rejected
--
Crashs when syncing with TE2
https://launchpad.net/bugs/43767
--
desktop-bugs mailing list
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 (Ubuntu)
Assignee: (unassigned) = Ubuntu Desktop Bugs
Status: Unconfirmed = Needs Info
--
Crashs when syncing with
No, the problem is still there, and my dapper is up-to-date
--
Crashs when syncing with TE2
https://launchpad.net/bugs/43767
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
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
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 **:
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
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.
--
Crashs when syncing with TE2
https://launchpad.net/bugs/43767
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
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.
--
Crashs when syncing with TE2
