After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 322864 - e_cal_new_system_calendar doesn't work at all
e_cal_new_system_calendar doesn't work at all
Status: RESOLVED FIXED
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.6.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks: 327516
 
 
Reported: 2005-11-30 17:00 UTC by Chris Lord
Modified: 2013-09-14 16:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
Patch (610 bytes, patch)
2005-11-30 17:03 UTC, Ross Burton 		accepted-commit_now Details | Review

Description Chris Lord 2005-11-30 17:00:08 UTC 
Version details: This also occurs in garnome 2.13.2
Distribution/Version: Ubuntu breezy

When using an ECal as returned from e_cal_new_system_calendar, the initial
objects-added signal will be received, as will signals generated by the client,
but signals generated by other applications (such as Evolution) on the system
calendar will not be received and changes will not be propogated correctly, in
either direction.

This is due to 'uri = g_build_filename ("file://", g_get_home_dir (),
".evolution", "calendar", "local", "system", NULL);' returning a uri that starts
with 'file:/' instead of 'file:///'
Comment 1 Ross Burton 2005-11-30 17:03:35 UTC 
Created attachment 55437 [details] [review]
Patch

Attaching an (untested, bad me) patch to fix this.  The problem is that
g_build_filename() will collapse multiple path separators into one as they are
meaningless in path names, but are not in URIs.
Comment 2 Poornima 2005-12-01 04:41:07 UTC 
Confirming this bug as 'Ross' also has observed this problem.
After 'Harish/Chen' reviewes this patch and checked in state of the bug can be
changed to 'Fixed'.
Comment 3 Ross Burton 2006-03-20 17:39:06 UTC 
Annoying that this didn't get into 2.6.  Any chance of it getting into the stable series?
Comment 4 Veerapuram Varadhan 2006-03-20 18:37:31 UTC 
Patch looks good to commit.  Please commit to HEAD as well as STABLE branch.
Comment 5 Ross Burton 2006-03-20 18:55:26 UTC 
Hm, I'm a fool: Tor had caught this earlier.
Comment 6 Veerapuram Varadhan 2006-03-20 19:02:35 UTC 
Hmm.. I guess, me too.  (Didn't check the actual sources)