Bug 537947 – Clock applet freezes on Click

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 537947 - Clock applet freezes on Click


Summary:	Clock applet freezes on Click


Status:	RESOLVED DUPLICATE of bug 515948

Product:	gnome-panel
Classification:	Other
Component:	clock
Version:	2.22.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-06-12 08:50 UTC by smol.robert
Modified:	2008-06-30 15:01 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Attachments
stack trace with debugging symbols (5.32 KB, text/plain) 2008-06-12 09:06 UTC, smol.robert	Details

Description smol.robert 2008-06-12 08:50:47 UTC

Steps to reproduce:
1. Click applet panel (sometimes)
2. 
3. 


Stack trace:
Not sure how to do stack propely, but this is from GDB.

+ Trace 200222

#0 __kernel_vsyscall
#1 pthread_cond_wait
from /lib/tls/i686/cmov/libpthread.so.0
#2 e_flag_wait
from /usr/lib/libedataserver-1.2.so.9
#3 ??
from /usr/lib/libecal-1.2.so.7
#4 e_cal_open
from /usr/lib/libecal-1.2.so.7
#5 ??
from /usr/lib/gnome-panel/libclock-applet.so
#6 ??
from /usr/lib/gnome-panel/libclock-applet.so
#7 calendar_sources_get_appointment_sources
from /usr/lib/gnome-panel/libclock-applet.so
#8 ??
from /usr/lib/gnome-panel/libclock-applet.so
#9 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#10 ??
from /usr/lib/libgobject-2.0.so.0
#11 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#12 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#13 g_object_new
from /usr/lib/libgobject-2.0.so.0
#14 calendar_client_new
from /usr/lib/gnome-panel/libclock-applet.so
#15 ??
from /usr/lib/gnome-panel/libclock-applet.so
#16 ??
from /usr/lib/gnome-panel/libclock-applet.so
#17 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#18 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#19 g_object_new
from /usr/lib/libgobject-2.0.so.0
#20 calendar_window_new
from /usr/lib/gnome-panel/libclock-applet.so
#21 ??
from /usr/lib/gnome-panel/libclock-applet.so
#22 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#23 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#24 ??
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#27 gtk_toggle_button_toggled
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libgobject-2.0.so.0
#31 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#32 ??
from /usr/lib/libgobject-2.0.so.0
#33 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#34 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#35 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgtk-x11-2.0.so.0
#37 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#38 ??
from /usr/lib/libgobject-2.0.so.0
#39 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#40 ??
from /usr/lib/libgobject-2.0.so.0
#41 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#42 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#43 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#44 ??
from /usr/lib/libgtk-x11-2.0.so.0
#45 ??
from /usr/lib/libgtk-x11-2.0.so.0
#46 ??
from /usr/lib/libgobject-2.0.so.0



Other information:
My colleague (who helped me with the stack trace) says it might be because I have evolution configured with Exchange backend and this thing is not working a lot of time. Also this happens when connectivity is not present to all sources (I also have Google Calendar enabled which is blocked via our admins).

Let me know if there is anything more I can do. I will try to install debug symbols and report back.

Comment 1 smol.robert 2008-06-12 09:06:43 UTC

Created attachment 112597 [details]
stack trace with debugging symbols

This is better stack trace with debugging symbols loaded.

Comment 2 Vincent Untz 2008-06-30 15:01:20 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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