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 673474 - Events not shown in planning view in gnome-shell
Events not shown in planning view in gnome-shell
Status: RESOLVED DUPLICATE of bug 673610
Product: evolution-data-server
Classification: Platform
Component: Calendar
3.4.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-04-04 05:35 UTC by Frederic Bezies
Modified: 2012-04-18 13:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frederic Bezies 2012-04-04 05:35:27 UTC
This is in some ways related to bug #672521.

I'm using archlinux testing, with gnome 3.4.0 in it.

After a gnutls bug was fixed (the one described in bug #672521), I have problem showing events in gnome-shell.

Looks like password is not remembered.

I launched evolution using a gnome-terminal session, and I got this, while I asked evolution to sync my google calendar account every 15 minutes.

(evolution:11325): e-data-server-ui-WARNING **: Le trousseau de clés est inutilisable : pas de nom d'hôte ou d'utilisateur

Rough translation :

(evolution:11325): e-data-server-ui-WARNING **: keyring cannot be used : no host or user name.

evolution-data-server : 3.4.0
gnome-keyring : 3.4.0

and if it matters, gnome-online-accounts : 3.4.0
Comment 1 André Klapper 2012-04-04 09:39:33 UTC
So this is only about a Google calendar? 
Or does the problem also happen for local calendars?
Comment 2 Frederic Bezies 2012-04-04 09:44:45 UTC
Well, with a local calendar, nothing appears too.
Comment 3 Milan Crha 2012-04-12 09:08:40 UTC
Thanks for abug report. There is filled a gnome-shell bug report, bug #673610, though the issue with
> e-data-server-ui-WARNING **: keyring cannot be used : no host or user name.
might be unrelated to it. How was you google calendar created?
Comment 4 Frederic Bezies 2012-04-12 09:15:19 UTC
I created my google calendar from the web. And I was able to synchronize it with planning filled with gnome 3.2.1 and Evolution 3.2.1.
Comment 5 Mundi Granja 2012-04-15 08:35:44 UTC
I can confirm this bug too.
Comment 6 André Klapper 2012-04-15 09:06:42 UTC
In general, confirmations are not helpful without version information and distribution information.
Comment 7 Mundi Granja 2012-04-15 09:21:56 UTC
Sorry, I'm a newbie.

I'm running ArchLinux testing too.

evolution-data-server: 3.4.0
gnome-keyring: 3.4.0
gnutls: 3.0.18
Comment 8 robert.vallis 2012-04-16 04:57:21 UTC
Fedora 17 Beta, Gnome 3.4, gnome shell is 3.4.0, evolution 3.4.0.1 and e-d-s 3.4.0.

I tried setting up the calendar using the online accounts, and nothing would show in either evolution-calendar or gnome-shell-preview-calendar. That turned out to be  a different bug. [1] However, now that I can get google calendars synced in my evo-calendar, they still do not show up in the g-s-p-c.

I also tried setting the calendar up in Evolution rather than using online acccounts. Same story. 

Finally tried using a local calendar. Again, no joy. The g-s-p-c simpy will not show a calendar event. The same is true of tasks  by the way, but I don't really use those I was just trying to get something to show up there.


[1] https://bugzilla.gnome.org/show_bug.cgi?id=673894
Comment 9 Milan Crha 2012-04-16 07:45:37 UTC
From Robert's comment I tend to believe this belongs to gnome-shell, especially if you can see events in evolution itself. Maybe this can be marked as a duplicate of bug mentioned in comment #3.
Comment 10 Frederic Bezies 2012-04-16 09:06:15 UTC
Well, why not ? But I want to see if the patch in bug #673610 fixes the issue before marking it as a duplicate.
Comment 11 Frederic Bezies 2012-04-18 13:51:41 UTC
Well, duplicate of bug #673610, planning is displaying events in gnome shell 3.4.1.

*** This bug has been marked as a duplicate of bug 673610 ***