11:24 a.m.
HI,
I am trying to run sync-ui on my ubuntu desktop. Lanches fine, I setup account for
scheduleworld and pressed "Sync Now" button. I am getting "Fatal database
error" . What am I missing? I do have evolution-data-server on my system.
Thanks
Raji
5:58 p.m.
On Fr, 2010-02-19 at 00:24 +0000, Bommaraju, Rajyalakshmi wrote:
I am trying to run sync-ui on my ubuntu desktop. Lanches fine, I
setup
account for scheduleworld and pressed “Sync Now” button. I am
getting “Fatal database error” . What am I missing?
What errors do you get when running the command line? What is in the
syncevolution-log.html? Which version do you use? For your work you
pretty much need the current "master" branch, so I assume you compiled
from source, right?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
5:27 a.m.
Yes, I compiled source from 'master' and installed. To debug, I ran sync from
command line, it just says 'synchronization process died prematurely', status 500.
I tried loglevel 4,did not get any more information about the error.
I created an event in the evolution and scheduleworld to make sure calendars are
accessible.
-Raji
-----Original Message-----
From: Ohly, Patrick
Sent: Thursday, February 18, 2010 10:59 PM
To: Bommaraju, Rajyalakshmi
Cc: SyncEvolution
Subject: Re: [SyncEvolution] Sync-UI on ubuntu desktop
On Fr, 2010-02-19 at 00:24 +0000, Bommaraju, Rajyalakshmi wrote:
I am trying to run sync-ui on my ubuntu desktop. Lanches fine, I
setup
account for scheduleworld and pressed "Sync Now" button. I am
getting "Fatal database error" . What am I missing?
What errors do you get when running the command line? What is in the
syncevolution-log.html? Which version do you use? For your work you
pretty much need the current "master" branch, so I assume you compiled
from source, right?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
5:33 a.m.
On Fr, 2010-02-19 at 18:27 +0000, Bommaraju, Rajyalakshmi wrote:
Yes, I compiled source from 'master' and installed. To debug,
I ran
sync from command line, it just says 'synchronization process died
prematurely', status 500. I tried loglevel 4,did not get any more
information about the error.
Please quote the complete output.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
5:37 a.m.
invalid tag <filename> at line 25 col 4
invalid tag <lenientmode> at line 1465 col 10
[ERROR] caught signal 11, shutting down
Segmentation fault
________________________________________
From: Ohly, Patrick
Sent: Friday, February 19, 2010 10:33 AM
To: Bommaraju, Rajyalakshmi
Cc: SyncEvolution
Subject: RE: [SyncEvolution] Sync-UI on ubuntu desktop
On Fr, 2010-02-19 at 18:27 +0000, Bommaraju, Rajyalakshmi wrote:
Yes, I compiled source from 'master' and installed. To debug,
I ran
sync from command line, it just says 'synchronization process died
prematurely', status 500. I tried loglevel 4,did not get any more
information about the error.
Please quote the complete output.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
5:42 a.m.
Here are the log files.
_______________________________________
From: syncevolution-bounces(a)syncevolution.org [syncevolution-bounces(a)syncevolution.org] On
Behalf Of Bommaraju, Rajyalakshmi [rajyalakshmi.bommaraju(a)intel.com]
Sent: Friday, February 19, 2010 10:37 AM
To: Ohly, Patrick
Cc: SyncEvolution
Subject: Re: [SyncEvolution] Sync-UI on ubuntu desktop
invalid tag <filename> at line 25 col 4
invalid tag <lenientmode> at line 1465 col 10
[ERROR] caught signal 11, shutting down
Segmentation fault
________________________________________
From: Ohly, Patrick
Sent: Friday, February 19, 2010 10:33 AM
To: Bommaraju, Rajyalakshmi
Cc: SyncEvolution
Subject: RE: [SyncEvolution] Sync-UI on ubuntu desktop
On Fr, 2010-02-19 at 18:27 +0000, Bommaraju, Rajyalakshmi wrote:
Yes, I compiled source from 'master' and installed. To debug,
I ran
sync from command line, it just says 'synchronization process died
prematurely', status 500. I tried loglevel 4,did not get any more
information about the error.
Please quote the complete output.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
SyncEvolution mailing list
SyncEvolution(a)syncevolution.org
http://lists.syncevolution.org/listinfo/syncevolution
5:49 a.m.
On Fr, 2010-02-19 at 18:37 +0000, Bommaraju, Rajyalakshmi wrote:
invalid tag <filename> at line 25 col 4
invalid tag <lenientmode> at line 1465 col 10
[ERROR] caught signal 11, shutting down
Segmentation fault
Ahem, mentiong that it segfaults would have been *very* useful
information ;-}
The error messages above that come from libsynthesis and point towards
using an out-dated version of it. Which version are you using (use ldd
to check)? How are you compiling?
If that is the one you compiled yourself and not the one from Ubuntu,
then please update your libsynthesis checkout to the latest master.
If you happen to pick up the system's libsynthesis by accident, then
consider compiling with "--disable-shared" and that can't happen
anymore.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
6:45 a.m.
Patrick and Jussi,
There is no way to set proxy through UI. I configured proxy through command-line and used
that configuration to sync using UI but it is not user friendly way. I think we need an
option to set the proxy.
Thanks for help Patrick & jussi, I got syncevolution working .
-Raji
-----Original Message-----
From: Ohly, Patrick
Sent: Friday, February 19, 2010 10:49 AM
To: Bommaraju, Rajyalakshmi
Cc: SyncEvolution
Subject: RE: [SyncEvolution] Sync-UI on ubuntu desktop
On Fr, 2010-02-19 at 18:37 +0000, Bommaraju, Rajyalakshmi wrote:
invalid tag <filename> at line 25 col 4
invalid tag <lenientmode> at line 1465 col 10
[ERROR] caught signal 11, shutting down
Segmentation fault
Ahem, mentiong that it segfaults would have been *very* useful
information ;-}
The error messages above that come from libsynthesis and point towards
using an out-dated version of it. Which version are you using (use ldd
to check)? How are you compiling?
If that is the one you compiled yourself and not the one from Ubuntu,
then please update your libsynthesis checkout to the latest master.
If you happen to pick up the system's libsynthesis by accident, then
consider compiling with "--disable-shared" and that can't happen
anymore.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
7:05 a.m.
On Fr, 2010-02-19 at 19:45 +0000, Bommaraju, Rajyalakshmi wrote:
There is no way to set proxy through UI. I configured proxy through
command-line and used that configuration to sync using UI but it is
not user friendly way. I think we need an option to set the proxy.
In Moblin and a Linux desktop, proxy settings should be part of the
system, not of a particular program. In contrast to the SyncEvolution
command line, sync-ui integrates with Moblin and GNOME and thus doesn't
need separate settings for that.
In other words, if you have a GNOME desktop, set the proxies there and
it will work without doing anything in SyncEvolution.
Thanks for help Patrick & jussi, I got syncevolution working .
What exactly was the reason for the segfault? If there is a version
incompatibility, then it shouldn't manifest itself as a segfault.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
8:29 a.m.
It got fixed when I reconfigured it with --disable-shared. My machine had another version
that came with Ubuntu.
-Raji
-----Original Message-----
From: Ohly, Patrick
Sent: Friday, February 19, 2010 12:05 PM
To: Bommaraju, Rajyalakshmi
Cc: SyncEvolution
Subject: RE: [SyncEvolution] Sync-UI on ubuntu desktop
On Fr, 2010-02-19 at 19:45 +0000, Bommaraju, Rajyalakshmi wrote:
There is no way to set proxy through UI. I configured proxy through
command-line and used that configuration to sync using UI but it is
not user friendly way. I think we need an option to set the proxy.
In Moblin and a Linux desktop, proxy settings should be part of the
system, not of a particular program. In contrast to the SyncEvolution
command line, sync-ui integrates with Moblin and GNOME and thus doesn't
need separate settings for that.
In other words, if you have a GNOME desktop, set the proxies there and
it will work without doing anything in SyncEvolution.
Thanks for help Patrick & jussi, I got syncevolution working .
What exactly was the reason for the segfault? If there is a version
incompatibility, then it shouldn't manifest itself as a segfault.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
1:40 a.m.
On Fr, 2010-02-19 at 21:29 +0000, Bommaraju, Rajyalakshmi wrote:
It got fixed when I reconfigured it with --disable-shared. My
machine
had another version that came with Ubuntu.
I can't reproduce the segfault. Even when picking the latest available
libsynthesis0 (3.2.0.35+ds1-1 from Lucid), a self-compiled syncevolution
won't accidentially run with that:
$ /tmp/local/bin/syncevolution funambol/tmp/local/bin/syncevolution: relocation error:
/tmp/local/lib/libsyncevolution.so.0: symbol SySync_srv_ConnectEngine, version VER_1.0 not
defined in file libsynthesis.so.0 with link time reference
I'm bumping the version of libsynthesis from .so.0.3.0 to .so.0.3.1
because of added features, but that won't have an effect on this
segfault.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
8:49 a.m.
On Fri, 19 Feb 2010 21:05:11 +0100, Patrick Ohly <patrick.ohly(a)intel.com> wrote:
In Moblin and a Linux desktop, proxy settings should be part of the
system, not of a particular program. In contrast to the SyncEvolution
command line, sync-ui integrates with Moblin and GNOME and thus doesn't
need separate settings for that.
Some of us do use sync-ui without gnome or moblin. I don't actually mind
configuring things from the command line, but I hope it won't get to the
point where I can't use sync-ui at all.
d
9:11 a.m.
On Fr, 2010-02-19 at 21:49 +0000, David Bremner wrote:
On Fri, 19 Feb 2010 21:05:11 +0100, Patrick Ohly
<patrick.ohly(a)intel.com> wrote:
> In Moblin and a Linux desktop, proxy settings should be part of the
> system, not of a particular program. In contrast to the SyncEvolution
> command line, sync-ui integrates with Moblin and GNOME and thus doesn't
> need separate settings for that.
Some of us do use sync-ui without gnome or moblin.
And that's what the builtin configuration options are for.
I don't actually mind
configuring things from the command line, but I hope it won't get to the
point where I can't use sync-ui at all.
Don't worry, we are careful to build the sync-ui so that it can work
with any kind of SyncEvolution config, not just the ones that can be
created with the GUI itself. However, we draw the line at adding
features that would only confuse the majority of the target users - at
least as far as we understand who those users and what they need.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9:24 p.m.
David Bremner wrote:
On Fri, 19 Feb 2010 21:05:11 +0100, Patrick Ohly
<patrick.ohly(a)intel.com> wrote:
> In Moblin and a Linux desktop, proxy settings should be part of the
> system, not of a particular program. In contrast to the SyncEvolution
> command line, sync-ui integrates with Moblin and GNOME and thus doesn't
> need separate settings for that.
Some of us do use sync-ui without gnome or moblin. I don't actually mind
configuring things from the command line, but I hope it won't get to the
point where I can't use sync-ui at all.
What Patrick said. I strongly oppose adding unnecessary configuration
settings to the UI (this includes things that are generally speaking
system settings or just uncommon syncevolution settings): every widget I
add inevitably lowers usability for the people who do not use that
widget and makes the design more difficult -- not much per widget but it
all adds up.
That said, I strive to never override things in the syncevolution config
if I can: I realise the options are there for a reason. Also, the line
for "necessary UI settings" isn't set in stone: current selection just
happens to be what we* decided on.
- Jussi
*) me, Patrick and Nick, a UX designer who is probably not on the list
but can be summoned here for discussion if need be
7 p.m.
Bommaraju, Rajyalakshmi wrote:
I am trying to run sync-ui on my ubuntu desktop. Lanches fine, I
setup
account for scheduleworld and pressed “Sync Now” button. I am getting
“Fatal database error” . What am I missing? I do have
evolution-data-server on my system.
I try to cover the common error situations in sync-ui but there are
often situations where it isn't worth the effort or it's not possible to
be more informative -- this is one of those cases. General debugging
instructions are:
* remove sync-ui from the picture, reproduce with syncevolution command
line
* look at ~/.cache/syncevolution/<datetime>/syncevolution-log.html.
Searching for "STATUS 500" may be useful in your case.
I'm open to improvement suggestions on the error message wording though:
I'm not too familiar with what exactly all the different error codes
mean... As an example, should we emphasize that this "db error" is
reported by the peer (so not a local db problem)? Are there any common
fixes we could suggest in the message?
-Jussi
10:49 p.m.
On Fr, 2010-02-19 at 08:00 +0000, Jussi Kukkonen wrote:
I'm open to improvement suggestions on the error message wording
though:
I'm not too familiar with what exactly all the different error codes
mean...
I think we are all learning about this. Let's see what the reason was in
this particular case.
As an example, should we emphasize that this "db error" is
reported by the peer (so not a local db problem)?
Distinguishing between local and remote errors would be useful,
independently of this particular error. It is a first hint to the user
who he should contact for help, or whether the problem might go away
(remote failures might get fixed by the server admins, local ones
require some action by the user).
Are there any common
fixes we could suggest in the message?
Nothing comes to my mind right now.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
7:37 a.m.
New subject: [SyncEvolution] segfault reporting in sync-ui (was: Re: Sync-UI on ubuntu desktop)
On Fr, 2010-02-19 at 11:49 +0000, Patrick Ohly wrote:
On Fr, 2010-02-19 at 08:00 +0000, Jussi Kukkonen wrote:
> I'm open to improvement suggestions on the error message wording though:
> I'm not too familiar with what exactly all the different error codes
> mean...
I think we are all learning about this. Let's see what the reason was in
this particular case.
A segfault. SyncEvolution core prepares for that by recording a bad
result for the session, which has to be overwritten later on:
synchronization process died prematurely
/** command failed / fatal DB error */
STATUS_FATAL = 500
That was introduced before we started to distinguish between local and
remote errors. The error code should have been 500 + LOCAL_STATUS_CODE
to mark it as a local problem.
> As an example, should we emphasize that this "db
error" is
> reported by the peer (so not a local db problem)?
Distinguishing between local and remote errors would be useful,
independently of this particular error. It is a first hint to the user
who he should contact for help, or whether the problem might go away
(remote failures might get fixed by the server admins, local ones
require some action by the user).
> Are there any common
> fixes we could suggest in the message?
Nothing comes to my mind right now.
In this particular case, should we introduce a special status for "died
prematurely"? Like a new SyncEvolution specific STATUS_DIED_PREMATURELY
= 22002?
There is something in syerror.h:
/** base code for linux signals (SIGXXX). SIGXXX enum value will be
added to LOCERR_SIGNAL */
LOCERR_SIGNAL = 20500
But we cannot use that because we should better not try to overwrite
status.ini after the process went bad because of a signal.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9:16 p.m.
New subject: [SyncEvolution] segfault reporting in sync-ui
Patrick Ohly wrote:
On Fr, 2010-02-19 at 11:49 +0000, Patrick Ohly wrote:
> I think we are all learning about this. Let's see what the reason was in
> this particular case.
A segfault. SyncEvolution core prepares for that by recording a bad
result for the session, which has to be overwritten later on:
synchronization process died prematurely
/** command failed / fatal DB error */
STATUS_FATAL = 500
That was introduced before we started to distinguish between local and
remote errors. The error code should have been 500 + LOCAL_STATUS_CODE
to mark it as a local problem.
Ok, this would have been shown on the UI as: "There is a problem with
the local database. Syncing again or rebooting may help." The suggestion
is there because this is what we see if EDS goes bonkers -- obviously
not very useful in this case.
In this particular case, should we introduce a special status for
"died
prematurely"? Like a new SyncEvolution specific STATUS_DIED_PREMATURELY
= 22002?
This would be what syncevolution writes in status.ini before starting to
work (so that if it does die, the status is correct)? Sounds good to me.
There is something in syerror.h:
/** base code for linux signals (SIGXXX). SIGXXX enum value will be
added to LOCERR_SIGNAL */
LOCERR_SIGNAL = 20500
But we cannot use that because we should better not try to overwrite
status.ini after the process went bad because of a signal.
I can't imagine that I'd want more details in the UI than "sync service
died prematurely": at that point one needs to look at logs and such
anyway regardless of the signal, right?
Jussi
3:48 a.m.
New subject: [SyncEvolution] segfault reporting in sync-ui
On Sa, 2010-02-20 at 10:16 +0000, Jussi Kukkonen wrote:
STATUS_DIED_PREMATURELY = 22002?
I've added this to "master", see MB #9844.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
4590
days inactive
4594
days old
syncevolution@synevolution.org
18 comments
4 participants
participants (4)
-
Bommaraju, Rajyalakshmi -
David Bremner -
Jussi Kukkonen -
Patrick Ohly