| Summary: | [Evolution][gnome-terminal] CRITICAL Error showing in terminal when run evolution | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Satyabrata Maitra <smaitra> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | dbraunwarth, lucilanga, mbarnes, mcrha, smaitra |
| Target Milestone: | --- | Keywords: | Desktop |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-07 17:05:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Satyabrata Maitra
2011-07-07 07:38:08 UTC
It is showing the following warning/error in bn_IN desktop when run evolution : [smaitra@localhost ~]$ evolution (evolution:2677): GLib-GObject-WARNING **: g_object_get_property: object class `EShellSettings' has no property named `cal-primary-calendar' (evolution:2677): GLib-GObject-WARNING **: g_object_set_property: object class `EShellSettings' has no property named `cal-primary-calendar' (evolution:2677): gtkhtml-CRITICAL **: html_object_is_text: assertion `object != NULL' failed (evolution:2677): gtkhtml-CRITICAL **: html_object_is_text: assertion `object != NULL' failed Thanks for a bug report. (In reply to comment #0) > ** (evolution:31277): CRITICAL **: categories_icon_theme_hack: assertion > `filename != NULL && *filename != '\0'' failed I can reproduce this when running git master of evolution in a mailer component like this: $ LANG=ml_IN evolution The warning seems to me like a bogus one, and can be removed silently. I didn't find an upstream bug report for this, though. (In reply to comment #1) > (evolution:2677): GLib-GObject-WARNING **: g_object_get_property: object class > `EShellSettings' has no property named `cal-primary-calendar' > > (evolution:2677): GLib-GObject-WARNING **: g_object_set_property: object class > `EShellSettings' has no property named `cal-primary-calendar' > > (evolution:2677): gtkhtml-CRITICAL **: html_object_is_text: assertion `object > != NULL' failed > > (evolution:2677): gtkhtml-CRITICAL **: html_object_is_text: assertion `object > != NULL' failed I do not see these when running evolution with bn_IN. The first two were there with 2.32.x, if I recall correctly, but the 3.0.x may not suffer of this. It may depend what component you are opening evolution in, and if it's in a mailer component, then also what message is selected for a preview. Could you check this, please? I got exactly the same message when I wanted to start gnome out of terminal. (evolution:2117): GLib-GObject-WARNING **: g_object_get_property: object class `EShellSettings' has no property named `cal-primary-calendar' (evolution:2117): GLib-GObject-WARNING **: g_object_set_property: object class `EShellSettings' has no property named `cal-primary-calendar' Segmentation fault (core dumped) But this only appears if I'm logged in as root. As user it's just the following message: Segmentation fault (core dumped) I'm not able to start evolution out of gnome 3 shell. I'm working on F17 x86_64 Could you install debug info packages for evolution and evolution-data-server and run evolution under gdb with a command like this: $ gdb evolution --ex r --ex "t a a bt" which will stop on the SEGV and print backtrace of the operation (you can quit gdb with "q" (quotes for clarity only) command) And then attach here the backtrace, please, thus it'll be clear where the crash happened? Also make sure you'll not expose any private information, like passwords or anything, though I guess you run evolution for the first time? This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |