[Bug 22152] New: GIO D-Bus clients crash the SyncEvolution server.
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=22152
Summary: GIO D-Bus clients crash the SyncEvolution server.
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ALL
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: mark.d.ryan(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
Created attachment 8641
--> https://bugs.meego.com/attachment.cgi?id=8641
Test program for crashing SyncEvolution
BUILD IMAGE:
MeeGo 1.2 Netbook 19th May
The bug is also present in the latest version of SyncEvolution (1.1.99.5)
downloaded from syncevolution.org and compiled for Ubuntu 11.04
HARDWARE MODEL:
Lenovo S10-3t
BUG DETAILED DESCRIPTIONS
===========================================================
I’m calling the SyncEvolution D-Bus APIs from C using the gio dbus functions.
Unfortunately, when I create a proxy using g_dbus_proxy_new_for_bus or
g_dbus_proxy_new_for_bus_sync using the default flags, the sync evolution
server crashes. I have noticed however, that if I use the flag
G_DBUS_PROXY_DOT_NO_LOAD_ PROPERTIES, when creating the proxy, there is no
crash. The crash can easily be reproduced with the attached test program.
EXACT STEPS LEADING TO PROBLEM:
===========================================================
1. Download the attached program, uncompress it to a directory and cd to this
directory.
2. ./configure
3. ./make
4. ./syncevotest
EXPECTED OUTCOME:
===================
The SyncEvolution daemon should not crash.
ACTUAL OUTCOME:
===================
It crashes
USER IMPACT:
===================
SyncEvolution clients written using the GIO D-Bus bindings that use the default
settings will not work. Other clients should be okay, as even if the
SyncEvolution server crashes, it will be re-launched by D-Bus as soon as it
receives a new request from another client.
REPRODUCIBILITY:
=====================================
100%
EXTRA SOFTWARE INSTALLED:
============================
Just the test program.
OTHER COMMENTS:
===================
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: mark.d.ryan(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=22152
--
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.
10 years, 9 months
[Bug 736] Detect 'device model' for phones
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=736
blixtra <blixtra(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |blixtra(a)gmail.com
--- Comment #3 from blixtra <blixtra(a)gmail.com> 2011-08-15 11:06:21 UTC ---
I've now got this working pretty well using the Bluetooth Device ID Profile
(DIP).
We detect if the bluetooth device supports the PnPInformation defined in the
Device ID Profile similar to the way SyncML functionality is detected; we check
that the UUID matches a well-defined value. Unlike SyncML, with PnPInformation
we also need to extract additional information from the record: vendor and
product id. I've added a very simple parser function to extract these values.
Once they are retrieved we look-up first the vendor and then the product. If
both are in the lookup table, then the product will be used as the fingerprint
for matching templates. If only the vendor is found, which will often be the
case until the product table gets better populated, we use that for the
fingerprint. Before, the user-modifiable device name was used for the
fingerprint. This is still used when there is no PnPInformation support. Even
when PnPInformation is supported the user-modifiable device name still needs to
be made available to the dbus interface consumer for use in a GUI, for
instance. For that reason, we now make this user-modifiable device name
available through the peerName field when calling GetConfig.
The new look-up table file is located in the src/dbus/server directory and is
installed to ${datadir}/syncevolution. I've added a new DATA_DIR cppflag that
can be overridden by setting a SYNCEVOLUTION_DATA_DIR environment variable.
Code changes were mostly confined to the Server, BluezManager and SyncConfig
classes.
To see the work pull my bluetooth-device-id branch or view it here:
https://meego.gitorious.org/meego-middleware/syncevolution/commits/blueto...
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: enhancement
Priority: Undecided
Keywords:
Status: ASSIGNED
Who: blixtra(a)gmail.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.
10 years, 9 months
[Bug 21249] New: remove RPATH /usr/lib from syncevolution.org binaries
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=21249
Summary: remove RPATH /usr/lib from syncevolution.org binaries
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
SyncEvolution 1.1.99.5a contains RPATH /usr/lib in various files. This breaks
loading libraries from other locations via LD_LIBRARY_PATH or ld.so config and
thus should be avoided.
As a workaround:
sudo perl -pi -e 's;/usr/lib(?!/);/xxx/lib;' \
/usr/lib/libsyncevolution.so.0.0.0 \
/usr/libexec/syncevo-dbus-server \
/usr/lib/syncevolution/libgdbussyncevo.so.0.0.0 \
/usr/lib/syncevolution/backends/*.so
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: patrick.ohly(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=21249
--
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.
10 years, 9 months
[Bug 22594] New: CalDAV: Google + Exchange + detached recurrences
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=22594
Summary: CalDAV: Google + Exchange + detached recurrences
Classification: MeeGo Projects
Product: SyncEvolution
Platform: ---
Version: unspecified
Platform: Common
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: patrick.ohly(a)intel.com
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE: SyncEvolution 1.1.99.5
BUG DETAILED DESCRIPTIONS
===========================================================
Evolution shows detached recurrences twice.
EXACT STEPS LEADING TO PROBLEM:
===========================================================
1. get your Google account invited to a meeting series from someone using
Exchange
2. have the organizer modify (not delete!) one recurrence
3. sync with Evolution via CalDAV
EXPECTED OUTCOME:
===================
Regular meeting show except for the one modified recurrence, which must show
the updated information.
ACTUAL OUTCOME:
===================
Evolution shows the meeting twice on the day of the modified recurrence.
USER IMPACT:
===================
Doesn't know which event is the up-to-date one.
REPRODUCIBILITY:
=====================================
100%
OTHER COMMENTS:
===================
Occurs because the detached recurrence generated this way contains a
RECURRENCE-ID in UTC. I suspect that this is legal according to the RFC and
that there is an Evolution/libical bug here.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: normal
Priority: Undecided
Keywords:
Status: NEW
Who: patrick.ohly(a)intel.com
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=22594
--
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.
10 years, 9 months
[Bug 4835] N900: fails to synchronize with some distros
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=4835
hschmitt <linux(a)hschmitt.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux(a)hschmitt.de
--- Comment #19 from hschmitt <linux(a)hschmitt.de> 2011-08-08 14:04:43 UTC ---
(In reply to comment #18)
> I have the same problem on two different machines, both with the same software
> installed: Ubuntu Linux 10.04 (Lucid) with Syncevolution 1.1.1. This means the
> same kernel, bluez software and so on. But on one machine it works, on the
> other this bug occurs.
>
> How can I help?
As I read the bug it could be due to a bug in openobex1.4 which is used in N900
PR1.3:
http://git.kernel.org/?p=bluetooth/openobex.git;a=blobdiff;f=lib/obex_obj...
Here you can find a openobex1.5 for Armel
http://talk.maemo.org/showthread.php?p=731941#post731941
The bug shows when the message is to big to transfer in one packet. So you can
test it on systems which fail with very small address books.
--------
Product: SyncEvolution
Component: SyncEvolution
MeeGo Release: unspecified
Severity: major
Priority: High
Keywords:
Status: WAITING FOR UPSTREAM
Who: linux(a)hschmitt.de
Assigned To: syncevolution-bugs(a)meego.bugs
Target Build: ---
Flags:
Changed: CC
--------
https://bugs.meego.com/show_bug.cgi?id=4835
--
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.
10 years, 9 months
[Bug 19661] MeeGo PHOTO data not synchronized to peer
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19661
jingke <jingke.zhang(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution| |FIXED
--- Comment #18 from jingke <jingke.zhang(a)intel.com> 2011-08-08 08:51:30 UTC ---
(In reply to comment #17)
> So the original problem that this issue is about was solved. Do you agree to
> mark it as verified?
>
Yes, I also agree this issue has been fixed. Thank you!
> The problem that you see is feature request #17345. I've added a comment that
> it also applies to Google.
--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: normal
Priority: Medium
Keywords: triaged
Status: RESOLVED
Who: jingke.zhang(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: Jul-29-11
Flags:
Changed: Status Resolution
--------
https://bugs.meego.com/show_bug.cgi?id=19661
--
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.
10 years, 9 months
[Bug 19661] MeeGo PHOTO data not synchronized to peer
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19661
--- Comment #17 from pohly <patrick.ohly(a)intel.com> 2011-08-08 08:02:12 UTC ---
(In reply to comment #16)
> (In reply to comment #15)
> > (In reply to comment #14)
> > > Hi Patrick,
> > > I cannot attach the syncevolution-log.html, it is so big (>3M) by loglevel=4.
> > > Our bugzilla only permit <1M attachment. I will give it in private mail.
> >
> > Please compress the log file.
> >
> > I tried to reproduce the issue, but it worked for me.
>
> Hi Patrick,
> I check the pictures I assigned to the contacts, one of them is
> /home/meego/Pictures/Animals/parrot.jpg. The picture is 976K size. How big is
> yours?
Just a small thumbnail.
> I also took a 12K picture to verify this issue, and contact with 12K is
> successfully synced to Google Contact Server.
So the original problem that this issue is about was solved. Do you agree to
mark it as verified?
The problem that you see is feature request #17345. I've added a comment that
it also applies to Google.
--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: normal
Priority: Medium
Keywords: triaged
Status: NEEDINFO
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: Jul-29-11
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=19661
--
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.
10 years, 9 months
[Bug 19661] MeeGo PHOTO data not synchronized to peer
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19661
--- Comment #16 from jingke <jingke.zhang(a)intel.com> 2011-08-08 01:17:21 UTC ---
(In reply to comment #15)
> (In reply to comment #14)
> > Hi Patrick,
> > I cannot attach the syncevolution-log.html, it is so big (>3M) by loglevel=4.
> > Our bugzilla only permit <1M attachment. I will give it in private mail.
>
> Please compress the log file.
>
> I tried to reproduce the issue, but it worked for me.
Hi Patrick,
I check the pictures I assigned to the contacts, one of them is
/home/meego/Pictures/Animals/parrot.jpg. The picture is 976K size. How big is
yours?
I also took a 12K picture to verify this issue, and contact with 12K is
successfully synced to Google Contact Server.
What's your info? :)
--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: normal
Priority: Medium
Keywords: triaged
Status: NEEDINFO
Who: jingke.zhang(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: Jul-29-11
Flags:
Changed:
--------
https://bugs.meego.com/show_bug.cgi?id=19661
--
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.
10 years, 9 months
[Bug 19661] MeeGo PHOTO data not synchronized to peer
by bugzilla＠meego.com
https://bugs.meego.com/show_bug.cgi?id=19661
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
--- Comment #15 from pohly <patrick.ohly(a)intel.com> 2011-08-05 07:07:42 UTC ---
(In reply to comment #14)
> Hi Patrick,
> I cannot attach the syncevolution-log.html, it is so big (>3M) by loglevel=4.
> Our bugzilla only permit <1M attachment. I will give it in private mail.
Please compress the log file.
I tried to reproduce the issue, but it worked for me.
--------
Product: OS Middleware
Component: SyncEvolution
MeeGo Release: 1.2
Severity: normal
Priority: Medium
Keywords: triaged
Status: NEEDINFO
Who: patrick.ohly(a)intel.com
Assigned To: patrick.ohly(a)intel.com
Target Build: Jul-29-11
Flags:
Changed: Status
--------
https://bugs.meego.com/show_bug.cgi?id=19661
--
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.
10 years, 9 months