[Hardy] Google calendar in evolution freezes Gnome Panel

Bug #214573 reported by komputes
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Confirmed
Medium
Ubuntu Desktop Bugs

Bug Description

Although I am not able to reproduce this with consistency, I thought it would be good to report it. When I click on the calendar, it shows as selected (shadowed/shaded) but ends up freezing the entire gnome-panel, not making anything clickable. The only solution I have found is to log out and log back in.
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1)
Package: gnome-panel 1:2.30.2-0ubuntu0.2
PackageArchitecture: i386
ProcEnviron:
 LANGUAGE=en_US:en_CA:en
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Tags: lucid
Uname: Linux 2.6.32-25-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Francisco Isgleas (isgleas) wrote :

I'm confirming this. gnome-panel suddenly froze, and if I run it on a terminal it launches gnome-panel, then starts/stops for about 5 times, then freezes again nor dissapears (not the same behavior all the time).

When called from console I get:
****
(gnome-panel:10379): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -25 and height 24

(gnome-panel:10379): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion `instance != NULL && instance->g_class != NULL' failed

(gnome-panel:10379): Gtk-CRITICAL **: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed

(gnome-panel:10379): Gtk-CRITICAL **: gtk_widget_size_request: assertion `GTK_IS_WIDGET (widget)' failed
****

Attaching gdb's log.

My timezone is America/Mexico_City (-5:00)
My locales are set to es_MX
My charset is UTF-8
Ubuntu 8.04 (dev) on an i386

Revision history for this message
Francisco Isgleas (isgleas) wrote :

I launch gnome-panel and, while the 'flicking', I managed to delete the clock applet from the upper panel, when done, the panel stopped flicking and now it seems to work ok.

I thought it was the clock applet because I think I saw some error referring to the timezoning.

I put back clock applet on the panel, to keep aware of it. I don't know, it may be something related to language-support{,-es} or language-pack-gnome{-es,-es-base} packages, as long as I can recall, there where some updates on those packages and I think there's strong relation because the localization.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

Changed in gnome-panel:
status: Confirmed → Invalid
Revision history for this message
Francisco Isgleas (isgleas) wrote :

I don't know how is this related to Bug #174088, but it may be.

Revision history for this message
komputes (komputes) wrote :

Bug #174088 is in Gutsy, this one is in Hardy (MAY BE CAUSE BY SOMETHING COMPLETELY DIFFERENT) please make sure developers know this befor 8.04 LTS rolls out. The packages affected are gnome-panel and perhaps evolution (which is where it grabs the calendar from when the user clicks on the time to get the date/calendar). Pedro, please mark this bug as valid and have it expedited or include the number of the bug you are referring.

Quote: "This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find."

Revision history for this message
Eric Drechsel (ericdrex) wrote :

Francisco: I don't think the behavior you are describing is related to this bug.

komputes: The temp solution is to killall gnome-panel from a gnome-terminal instance (accessed by alt-tab) or VT 1 (accessed by ctrl-alt+F1).

Pedro: the description of #213944 indicates a crash at startup, which isn't the behavior reported here. Clicking the clock applet causes gnome-panel to become unresponsive, but not SIGSEGV. I don't think this is a duplicate, although Andrew Melo has reported this bug in the comments of #213944 and #174088. I am experiencing this on Hardy with the default panel config.

Revision history for this message
Eric Drechsel (ericdrex) wrote :

Solved by PRGUY85 in http://ubuntuforums.org/showthread.php?p=4993857

Evolution > Delete google calendar (it doesn't work anyway)

Revision history for this message
Eric Drechsel (ericdrex) wrote :

can't find source package for gdata evolution calendar plugin

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
Revision history for this message
komputes (komputes) wrote :

This hasn't been an issue for me since Hardy was in Beta stage, I think Eric may be experiencing a different issue with google calendar inside evolution.

Revision history for this message
Eric Drechsel (ericdrex) wrote :

komputes: perhaps. I was experiencing the same behavior you describe, and removing the "google sources" plugin in evolution fixed it. I'm not sure how to reproduce, but the "google sources" plugin is pretty broken and should be fixed or removed.

Revision history for this message
Nathaniel Smith (njs) wrote :

I can confirm this bug -- it bit me today on up-to-date hardy, and seems very likely to be an issue with evolution's Google calendar support. My timeline:
  * Used hardy for months, no problems
  * Added a google calendar to evolution (Using New -> Calendar -> Type: Google). Discovered that it didn't work (it seemed to add the calendar, but never showed any events). Poked and prodded it for a bit; gave up.
  * Continued to use hardy for a few weeks, no problems
  * A few hours ago, discovered that clicking on the clock applet in the panel caused the background to go "depressed" and then the entire panel to freeze. This is perfectly consistent -- restarting the panel, rebooting, etc. all cause the panel to start working again, but it freezes as soon as I click on the clock.
  * I opened evolution and discovered that it had, somehow, in the last day or so, decided to actually start loading the google calendar.
  * I deleted the google calendar from evolution, and restarted the panel; now it works fine.

So the timing makes it look like some issue with that calendar -- when the calendar appeared, my panel stopped working, and removing the calendar fixed the panel.

Further details: I have other webcal calendars in evolution (New -> Calendar -> Type: "On the web"), also pulled from google, as it happens, but not using the Google "calendar type" and not requiring authentication. So it may be something specific to the special Google support plugin.

Since the "Type: Google" option didn't work, I also tried adding the same calendar as a generic webcal feed. It prompted for authentication etc., but never loaded events, and still hasn't. Possibly if it ever starts loading events it will freeze my panel too. So it may be something specific to authenticating to google over webcal, I dunno.

The google calendar in question is in a Google Apps For Your Domain account.

Changed in gnome-panel:
status: Invalid → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug is a duplicate

Changed in evolution:
status: New → Invalid
Revision history for this message
schmeii (schmeii) wrote :

I am unsetting bug #204775 as a duplicate because the fix for that bug doesn't fix this issue and I found no other duplicates of this bug.

Changed in gnome-panel (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
komputes (komputes) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
komputes (komputes) wrote : GConfNonDefault.txt

apport information

Revision history for this message
komputes (komputes) wrote :

Please ignore the latest apport uploads.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.