Red Hat Bugzilla – Bug 862870
[abrt] orage-4.8.3-1.fc17: Process /usr/bin/orage was killed by signal 11 (SIGSEGV)
Last modified: 2013-08-01 13:33:55 EDT
Description of problem:
Selected from menu on previous login.
This occurance I suspect because started automatically by desktop.
Has not worked since upgrading with yum
Version-Release number of selected component:
libreport version: 2.0.13
:Thread no. 1 (10 frames)
: #0 icaltimezone_load_builtin_timezone at icaltimezone.c
: #1 icaltimezone_ensure_coverage at icaltimezone.c
: #2 icaltimezone_get_utc_offset_of_utc_time at icaltimezone.c
: #3 icaltimezone_convert_time at icaltimezone.c
: #4 icaltime_convert_to_zone at icaltime.c
: #5 convert_to_local_timezone at ical-code.c
: #6 process_start_date at ical-code.c
: #7 get_appt_from_icalcomponent at ical-code.c
: #8 xfical_mark_calendar_from_component at ical-code.c
: #9 xfical_mark_calendar_file at ical-code.c
Created attachment 621090 [details]
Created attachment 621091 [details]
Created attachment 621092 [details]
Created attachment 621093 [details]
Created attachment 621094 [details]
Created attachment 621095 [details]
Created attachment 621096 [details]
Created attachment 621097 [details]
Created attachment 621098 [details]
So, anytime you start it it crashes this way?
Can you run it from a terminal and attach the output?
Also, if you make a new user and login as them does it work?
147 files 114M -> /usr/bin/orage
** Message: First Orage start. Searching default timezone.
** Message: Default timezone set to US/Eastern.
19:07:35 ** Message: Orage **: wakeup timer init 0
** (orage:15563): WARNING **: ic_internal_file_open: too many top level components in calendar file /mail/phil/orage/orage.ics
19:07:35 ** Message: Orage **: Build alarm list: Added 0 alarms. Processed 9 events.
19:07:35 ** Message: Orage **: Found 18 alarms of which 0 are active. (Searched 0 recurring alarms.)
Segmentation fault (core dumped)
147 files 114M ->
new user scenario to follow shortly.
calendar window appears briefly (approx 1 sec) on startup
/mail is nfs mount
New user test created via administration/users and groups from Applications Menu
8 files 124K -> /usr/bin/orage
8 files 124K -> /usr/bin/orage
19:23:49 ** Message: Orage **: wakeup timer init 0
19:23:49 ** Message: Orage **: Build alarm list: Added 0 alarms. Processed 0 events.
19:23:49 ** Message: Orage **: Found 0 alarms of which 0 are active. (Searched 0 recurring alarms.)
ok, so it's something in your data.
Can you see if you can get a backtrace on it?
That would be most helpfull. Thanks.
Manual start of orage from command line
OS Release: Fedora release 17 (Beefy Miracle)
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.
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 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.
Thank you for reporting this bug and we are sorry it could not be fixed.