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 317484 - gnome Clock applet in top panel crash
gnome Clock applet in top panel crash
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Calendar
1.8.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 397211 (view as bug list)
Depends on:
Blocks: 327516
 
 
Reported: 2005-09-29 03:42 UTC by John Chendra
Modified: 2013-09-10 13:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description John Chendra 2005-09-29 03:42:44 UTC
Distribution: Fedora Core release 4 (Stentz)
Package: gnome-panel
Severity: major
Version: GNOME2.10.0 2.10.x
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome Clock applet in top panel crash
Bugzilla-Product: gnome-panel
Bugzilla-Component: clock applet
Bugzilla-Version: 2.10.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
When I click the clock applet to see the date/calendar, the program
crashes.

Steps to reproduce the crash:
1. click on the clock applet in the top panel of gnome
2.
3.

Expected Results:
a pop-up window of the calendar

How often does this happen?
everytime

Additional Information:
none,
sorry, this is my first bug report



Debugging Information:

Backtrace was generated from '/usr/libexec/clock-applet'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209153856 (LWP 8009)]
[New Thread -1211352144 (LWP 2269)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00920402 in ?? ()

Thread 1 (Thread -1209153856 (LWP 8009))

  • #0 ??
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 e_cal_set_default_timezone
    from /usr/lib/libecal-1.2.so.2
  • #5 calendar_client_get_type
  • #6 calendar_event_free
  • #7 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_object_thaw_notify
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #12 calendar_client_new
  • #13 main



--
http://john.chendra.net




------- Bug moved to this database by unknown@gnome.bugs 2005-09-29 03:42 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was jchendra@gmail.com.

Comment 1 Brent Smith (smitten) 2005-09-29 05:34:24 UTC
looks like a unique stack trace.  Marking as NEW.
Comment 2 Vincent Untz 2005-10-01 08:45:09 UTC
Looks like a bug in e-d-s
Comment 3 Chakravarthi 2005-10-22 09:08:07 UTC
Can the reporter please get back to us with the timezone information 
being used in his/her evolution ?

This bug is similar to 
http://bugzilla.gnome.org/show_bug.cgi?id=318104

The reporter may also want look at the last few comments of the above bug.

Comment 4 John Chendra 2005-10-22 15:08:03 UTC
My Timezone is Asia/Makassar (GMT +8)

I cannot tell if my problem is the same as 318104, since I don't have the same
Timezone and I didn't try to change the timezone.

I'll try some of the case on 318104 as soon as I get to the troubled machine
(which is at my office, and today is Saturday here :)
Comment 5 John Chendra 2005-10-25 03:46:40 UTC
Okay, I've tried to open up evolution and here's the result:
Evolution crashes everytime I click to open up Calendars and Tasks

I probably should add that I'm using NTP. I've changed my Timezone to
Asia/Singapore and later on Asia/Hongkong. I restart Evolution (even the
machine) but it seems that the problem still exists, the clock applet still
crash and so is Calendars and Tasks.

So, I guess it is not the same case. If I'm not mistaken, this problem doesn't
exist at first or few days after I install FC4, because I remember clicking it
once, quite a long time ago. Maybe there's a conflict or something with some
software I installed later. I'll try to do a fresh install and recheck it.
Comment 6 Chakravarthi 2005-10-25 10:12:14 UTC
thanx .. will look into it soon
Comment 7 Chakravarthi 2005-10-27 10:26:49 UTC
i see that in recent evolution, Makassar's timezone information is missing.

If you have chenged the timezone (system's) using NTP.. that doesn't effect
evolution in setting its own timezone. anyway a patch will be soon updated here 
to fix this problem. thanx again.
Comment 8 Brent Smith (smitten) 2005-12-30 00:50:58 UTC
any updates on this?
Comment 9 André Klapper 2006-05-30 17:19:22 UTC
reassigning chakravarthi's bugs to avoid rotting.
Comment 10 André Klapper 2006-06-15 14:38:43 UTC
Evolution 2.7.3:

"Asia/Makassar" can be chosen as evolution's timezone, but it is not included in http://cvs.gnome.org/viewcvs/libical/zoneinfo/Asia/ - it has been removed, see http://cvs.gnome.org/viewcvs/libical/zoneinfo/Asia/Makassar.ics , perhaps we should re-add it to CVS.
chen, comments?


changing my evolution time zone to "Asia/Makassar" immediately crashes the gnome-panel and Evolution here:

Backtrace was generated from '/opt/gnome/libexec/evolution-2.8'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1236429136 (LWP 1646)]
[New Thread -1487930464 (LWP 25264)]
[New Thread -1454396512 (LWP 1873)]
[New Thread -1437611104 (LWP 1871)]
[New Thread -1446003808 (LWP 1870)]
[New Thread -1429218400 (LWP 1868)]
[New Thread -1412432992 (LWP 1867)]
[New Thread -1420825696 (LWP 1866)]
[New Thread -1876448352 (LWP 1864)]
[New Thread -1868055648 (LWP 1862)]
[New Thread -1884841056 (LWP 1859)]
[New Thread -1893233760 (LWP 1858)]
[New Thread -1410020448 (LWP 1648)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1236429136 (LWP 1646))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 812
  • #3 segv_redirect
    at main.c line 425
  • #4 <signal handler called>
  • #5 giop_send_buffer_append_string
    at giop-send-buffer.c line 515
  • #6 ORBit_marshal_value
    at corba-any.c line 208
  • #7 orbit_small_marshal
    at orbit-small.c line 353
  • #8 ORBit_small_invoke_stub
    at orbit-small.c line 645
  • #9 ORBit_small_invoke_stub_n
    at orbit-small.c line 575
  • #10 ORBit_c_stub_invoke
    at poa.c line 2643
  • #11 GNOME_Evolution_Calendar_Cal_setDefaultTimezone
    at Evolution-DataServer-Calendar-stubs.c line 140
  • #12 e_cal_set_default_timezone
    at e-cal.c line 5061
  • #13 e_cal_model_set_timezone
    at e-cal-model.c line 1076
  • #14 e_calendar_view_set_timezone
    at e-calendar-view.c line 492
  • #15 set_timezone
    at e-cal-list-view-config.c line 153
  • #16 timezone_changed_cb
    at e-cal-list-view-config.c line 164
  • #17 notify_listeners_callback
    at gconf-client.c line 2384
  • #18 notify_listener_list
    at gconf-listeners.c line 589
  • #19 ltable_notify
    at gconf-listeners.c line 655
  • #20 gconf_listeners_notify
    at gconf-listeners.c line 184
  • #21 notify_one_entry
    at gconf-client.c line 2409
  • #22 gconf_client_flush_notifies
    at gconf-client.c line 2449
  • #23 notify_idle_callback
    at gconf-client.c line 2343
  • #24 g_idle_dispatch
    at gmain.c line 3924
  • #25 g_main_dispatch
    at gmain.c line 2043
  • #26 IA__g_main_context_dispatch
    at gmain.c line 2594
  • #27 g_main_context_iterate
    at gmain.c line 2675
  • #28 IA__g_main_loop_run
    at gmain.c line 2879
  • #29 bonobo_main
    at bonobo-main.c line 311
  • #30 main
    at main.c line 614
  • #0 __kernel_vsyscall

Comment 11 palfrey 2007-01-16 22:50:03 UTC
*** Bug 397211 has been marked as a duplicate of this bug. ***
Comment 12 Kjartan Maraas 2007-01-17 00:25:23 UTC
Chen? Ping!?
Comment 13 Matthew Barnes 2008-03-11 00:58:54 UTC
Bumping version to a stable release.
Comment 14 Suman Manjunath 2008-08-06 04:59:54 UTC
Last trace is from evo 2.7.3

Could you please check if this is still an issue with the latest stable release (2.22.x)? 

Evolution now uses system timezone information. So, missing timezone ICS files should no longer be an issue. 
Comment 15 Akhil Laddha 2008-10-31 12:48:15 UTC

Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for with
current version 2.24.1 Thanks!