Version-Release number of selected component: orage-4.8.3-4.fc18 Additional info: backtrace_rating: 4 cmdline: orage crash_function: icaltimezone_load_builtin_timezone executable: /usr/bin/orage kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 icaltimezone_load_builtin_timezone at icaltimezone.c:1766 #1 icaltimezone_ensure_coverage at icaltimezone.c:462 #2 icaltimezone_get_utc_offset_of_utc_time at icaltimezone.c:969 #3 icaltimezone_convert_time at icaltimezone.c:778 #4 icaltime_convert_to_zone at icaltime.c:1081 #5 convert_to_local_timezone at ical-code.c:572 #6 ic_get_period at ical-code.c:594 #7 process_alarm_trigger at ical-code.c:2720 #8 xfical_alarm_build_list_internal_real at ical-code.c:3083 #9 xfical_alarm_build_list_internal at ical-code.c:3145 Potential duplicate: bug 862870
Created attachment 691174 [details] File: backtrace
Created attachment 691175 [details] File: cgroup
Created attachment 691176 [details] File: core_backtrace
Created attachment 691177 [details] File: dso_list
Created attachment 691178 [details] File: environ
Created attachment 691179 [details] File: limits
Created attachment 691180 [details] File: maps
Created attachment 691181 [details] File: open_fds
Created attachment 691182 [details] File: proc_pid_status
Created attachment 691183 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
sorry I haven't done anything about this... just got used to it not working have only one of seven machines giving this problem happens when just clicking the panel clock to get the calendar to open it opens and crashes but clock keeps running correctly it opens on all my other machines... on this one it is killed and crashes but I didn't think about it again till now can't even remember if this is the machine it started on now have all machines running fedora 18 now but think this may have started back on fedora 17.... just didn't remember about it. does this from terminal [al@zotac8 ~]$ orage ** Message: First Orage start. Searching default timezone. ** Message: Default timezone set to posix/US/Central. 15:13:19 ** Message: Orage **: wakeup timer init 0 Segmentation fault (core dumped) [al@zotac8 ~]$
On that same machine, if you add a new user, login as them, does it work? (that will tell us if it's a machine wide issue or one with your specific user config). Also, can you run a 'strace -f -o /tmp/trace.out orage' and attach the /tmp/trace.out?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.