[Bug 716] syncevo-dbus-server freezes when backend is bogus
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=716
murrayc <murrayc(a)murrayc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |murrayc(a)murrayc.com
--- Comment #2 from murrayc <murrayc(a)murrayc.com> 2011-06-08 11:27:17 UTC ---
The current status is that we think Syncevo-dbus-server's event handling should
run all syncs inside a forked process. This work could possibly lead to a
complete rewrite of the code.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Medium
Keywords:
Status: ASSIGNED
Who: murrayc(a)murrayc.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed: CC
--------
https://bugs.meego.com/show_bug.cgi?id=716
--
Configure bugmail: https://bugs.meego.com/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.
9 years, 7 months
[Bug 1351] SyncEvolution code cleanup
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=1351
--- Comment #2 from murrayc <murrayc(a)murrayc.com> 2011-06-08 11:25:32 UTC ---
I suspect that we should also use GDBus (part of glib) instead of libdbus (via
libgdbus), because it fixes some general threading problems vaguely hinted at
here: http://developer.gnome.org/gio/stable/ch29.html. It would also remove
that (copied) code from syncevolution, letting us depend on glib's maintenance
of that layer. Using that "standard" C high-level API for D-Bus would also make
the code more readable for the typical GTK+/GNOME developer, making it easier
to get improvements from the community.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Medium
Keywords:
Status: ASSIGNED
Who: murrayc(a)murrayc.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=1351
--
Configure bugmail: https://bugs.meego.com/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.
9 years, 7 months
[Bug 736] Detect 'device model' for phones
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=736
murrayc <murrayc(a)murrayc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |murrayc(a)murrayc.com
--- Comment #2 from murrayc <murrayc(a)murrayc.com> 2011-06-08 11:09:59 UTC ---
Here's a summary of the current plan:
SyncEvolution can adapt to the capabilities of the device that it is syncing
with. However, that currently requires the user to manually select a template.
Ideally, SyncEvolution would be able to automatically detect popular devices,
avoiding this step.
Currently, SyncEvolution only knows the the device name assigned to a Bluetooth
device. But this string is simply a default human-readable value that can be
modified by users and might not describe the manufacturer or model at all.
There are several ways to obtain more information:
* Use bluez to obtain the Bluetooth Device ID Profile via the Bluetooth Service
Discovery protocol.
We have confirmed that bluez already has support for this, via its
sdp_record_t query results, though the protcol only provides unsigned 16-bit
values, so SyncEvolution will require a mapping of these to actual vendor and
device names.
Not all mobile phones support the Bluetooth Device ID Profile, but apparently
enough do support it for it to be worth using. See BluetoothDeviceIDProfile.
* Use bluez to request the Bluetooth address and then parse if to discover the
device manufacturer.
Bluez already has functions to do this, such as ba20ui() and oui2comp() via
its own internal mapping. This will not provide a unique device ID, though it
should uniquely identify the device manufacturer. However, this might be the
manufacturer of the bluetooth adaptor rather than, for instance, the mobile
phone. This might at least be used to narrow the list of choices.
* Use SyncML's initialization stage to read the DevInf section.
However, this is currently ruled out. See #c1
We can make the device identification available to syncevo-dbus-server and to
use that to automatically select the appropriate template in the GTK+ GUI, or
to at least reduce the available choices there.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Undecided
Keywords:
Status: ASSIGNED
Who: murrayc(a)murrayc.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed: CC
--------
https://bugs.meego.com/show_bug.cgi?id=736
--
Configure bugmail: https://bugs.meego.com/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.
9 years, 7 months
[Bug 18175] New: GetConfig returns password as "-"
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=18175
Summary: GetConfig returns password as "-"
Classification: MeeGo Platform
Product: OS Middleware
Platform: ---
Version: 1.2
Platform: Common
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: gabriel.schulhof(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
ext-iekku.huttunen(a)nokia.com
Estimated Hours: 0.0
SyncEvolution 1.1.99.4+20110524+SE+2172a65
1. Create a configuration for Google Calendar, complete with credentials
2. rm -rf ${HOME}/.gnome2/keyring
3. Call GetConfig("Google", false) and dump the output
EXPECTED OUTCOME:
===================
Password is empty.
ACTUAL OUTCOME:
===================
Password is "-"
REPRODUCIBILITY:
=====================================
Always
--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: gabriel.schulhof(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=18175
--
Configure bugmail: https://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
9 years, 7 months