[Bug 9961] New: Service configuration made on GUI does not disable memo defaultly
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=9961
Summary: Service configuration made on GUI does not disable
memo defaultly
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: normal
Priority: Undecided
Component: GTK UI
AssignedTo: jku(a)linux.intel.com
ReportedBy: jingke.zhang(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution(a)lists.intel.com
syncevolution-0.9.99.11
Description:
==================
I configure a scheduleworld service with correct username and password through
syncUI. I can sync with scheduleworld on GUI, but it will fail in command line:
[ERROR] memo: not found: ''
Then I checked the
.config/syncevolution/default/peer/scheduleworld/sources/memo/config.ini, the
sync= two-way. It is wrong.
Use 'syncevolution -l scheduleworld test1' to generate service configuration,
the memo is disabled by default. Please check the syncUI code.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12 years, 6 months
[Bug 9844] New: error status when syncevolution dies
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=9844
Summary: error status when syncevolution dies
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: normal
Priority: P2
Component: *Feature Request
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
When syncevolution (command line) or syncevo-dbus-server die during a sync
session (like a segfault, or kill -9), the status.ini for that session should
contain error "synchronization process died prematurely" and a suitable status
code.
As discussed on the mailing list, the previous 500 status code is unsuitable
because it is a remote error and too unspecific.
Let's use a new STATUS_DIED_PREMATURELY = 22002.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12 years, 6 months
[Bug 9636] New: [D-Bus] InfoRequest timeout leads to error 10500
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=9636
Summary: [D-Bus] InfoRequest timeout leads to error 10500
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: minor
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: jku(a)linux.intel.com
QAContact: yanshuang.zheng(a)intel.com
CC: syncevolution(a)lists.intel.com
Letting a password InfoRequest signal timeout leads to sync status 10500: there
should be a specific status for this.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12 years, 6 months
[Bug 9558] New: sync errors may be confusing on startup
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=9558
Summary: sync errors may be confusing on startup
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: NEW
Severity: minor
Priority: Undecided
Component: GTK UI
AssignedTo: jku(a)linux.intel.com
ReportedBy: jku(a)linux.intel.com
QAContact: yanshuang.zheng(a)intel.com
CC: syncevolution(a)lists.intel.com
The UI always shows the last error message (if any) for the default peer --
this includes application startup. Some error messages are probably not written
to fit this situation, giving the user the possibility to mistakenly believe
that something failed just now.
Two possible solutions:
* Add "Last sync failed: " prefix to messages that didn't just appear.
* Modify messages so that it is clear they refer to the last sync, whenever
that happened.
I'll have to review the error messages before I decide.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12 years, 6 months
[Bug 9289] New: OBEXTransportAgent: libopenobex2 vs. libopenobex3
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=9289
Summary: OBEXTransportAgent: libopenobex2 vs. libopenobex3
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: congwu.chen(a)intel.com
ReportedBy: patrick.ohly(a)intel.com
QAContact: yanshuang.zheng(a)intel.com
CC: syncevolution(a)lists.intel.com
The OBEXTransportAgent did not compile on Hardy because of
int sdp_extract_seqtype(const uint8_t *buf, uint8_t *dtdp, int *seqlen);
int sdp_extract_seqtype_safe(const uint8_t *buf, int bufsize, uint8_t *dtdp,
int *size);
sdp_record_t *sdp_extract_pdu(const uint8_t *pdata, int *scanned);
sdp_record_t *sdp_extract_pdu_safe(const uint8_t *pdata, int bufsize, int
*scanned);
Our code called sdp_extract_seqtype() and sdp_extract_pdu() as if they were the
more recent _safe variants, in other words, passed to many arguments.
It seems that libbluetooth3 changed its API in an incompatible way. Binaries
compiled on Hardy won't work on more recent Ubuntu and Debian Unstable.
Argh.
I have a patch ready that allows compilation of our code with the different
libbluetooth versions, but I don't have a solution for the binary
incompatibility. I'll compile without Bluetooth support, then for 1.0 we can
try something else, like dynamic linker tricks.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12 years, 6 months
[Bug 8048] New: command line: multiple peers per config
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=8048
Summary: command line: multiple peers per config
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Netbook
OS/Version: Moblin Linux
Status: ASSIGNED
Severity: normal
Priority: P3
Component: *Feature Request
AssignedTo: syncevolution(a)lists.intel.com
ReportedBy: patrick.ohly(a)intel.com
CC: syncevolution(a)lists.intel.com
As part of the revised configuration layout (bug #7707) empty configuration
names became a new meaning: they are a view on the peer-independent config
properties. Because the changes didn't modify the internal APIs, the command
line contues to work as before.
However, it does not take advantage of the new features yes:
- --print-config should not print peer-specific properties unless
a peer is selected
- --configure should work without selecting a peer and properly complain
about options which are invalid in such a context
- --print-sessions should find all sessions of all peers, sorted by time
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
12 years, 6 months
[Bug 2425] support suspend/resume in infrastructure
by bugzilla@moblin.org
http://bugzilla.moblin.org/show_bug.cgi?id=2425
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |INTEGRATED
--- Comment #12 from pohly <patrick.ohly(a)intel.com> 2010-03-22 06:29:37 PST ---
Improvements landed in Moblin 0.9.99.13, except for the server script and the
README.
QA, I'm not sure how you can verify this issue, short of including HTTP server
setup and client-test runs into your regular checking. I create bug #10344 so
that we remember to include it in ours. Feel free to make "CLOSED" without
verification.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12 years, 6 months