Bug 998866

Created attachment 788394 [details]
Evolution backtrace

Thanks for a bug report, but I'm not sure of the screen shot, it shows htop or such, with no reference to evolution, only many chrome processes. The attached backtraces show all processes idle, not waiting for anything "in progress". Do I miss anything?

I want show that evolution (first string in htop) consume 100% of CPU core.

Oh, the first line, I didn't look at it as it had other color from the rest of the screen shot. Anyway, as I wrote above, all the processes are idle  in evolution backtrace, which might also mean that you were lucky and got the backtrace in a "pause" minute. The thing is, do you have any steps how to reproduce this, please? Specifically, your console logs show that there is loaded some libreoffice4 plugin, which is not shown for me (I guess it's a web browser plugin, which is loaded by WebKit).

$ evolution
No bp log location saved, using default.
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:002] Using Gtk2 toolkit
No bp log location saved, using default.
[000:379] No bp log location saved, using default.
[000:379] Browser XEmbed support present: 1
[000:379] Browser toolkit is Gtk2.
[000:379] Using Gtk2 toolkit
[000:000] No bp log location saved, using default.
Created new window in existing browser session.

(evolution:1790): dconf-WARNING **: failed to commit changes to dconf: Timeout was reached

(evolution:1790): dconf-WARNING **: failed to commit changes to dconf: Timeout was reached

(evolution:1790): Gtk-WARNING **: Refusing to add non-unique action 'open-with-env' to action group 'openwith'

(evolution:1790): Gtk-WARNING **: Refusing to add non-unique action 'open-with-env' to action group 'openwith'

(evolution:1790): dconf-WARNING **: failed to commit changes to dconf: Timeout was reached

(evolution:1790): dconf-WARNING **: failed to commit changes to dconf: Timeout was reached

(evolution:1790): dconf-WARNING **: failed to commit changes to dconf: Timeout was reached

** (evolution:1790): WARNING **: Timeout was reached

(evolution:1790): evolution-mail-WARNING **: Failed to request http://atmst.net/o~AVGUST~d6d085644083f7869868bdfbe005bf28.gif (code 4)

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x984bc60 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x984bc60 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x984bc60 is mapped but visible=0 child_visible=1 parent GtkBox 0xa32ddd0 mapped=1

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x984bc60 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x984bc60 is mapped but visible=0 child_visible=1 parent GtkBox 0xa32ddd0 mapped=1

(evolution:1790): evolution-mail-WARNING **: Failed to request http://www.jobool.com/index.php?mailid=83&option=com%5Facymailing&subid=815613&ctrl=stats (code 4)

(evolution:1790): evolution-mail-WARNING **: Failed to request http://www.jobool.com/index.php?mailid=83&option=com%5Facymailing&subid=815613&ctrl=stats (code 4)

(evolution:1790): evolution-mail-WARNING **: Failed to request http://www.jobool.com/index.php?mailid=83&option=com%5Facymailing&subid=815613&ctrl=stats (code 4)

** (evolution:1790): CRITICAL **: e_mail_part_list_ref_part: assertion `E_IS_MAIL_PART_LIST (part_list)' failed

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8e20 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8e20 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8e20 is mapped but visible=0 child_visible=1 parent GtkBox 0xab75738 mapped=1

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8e20 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8e20 is mapped but visible=0 child_visible=1 parent GtkBox 0xab75738 mapped=1

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8800 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8800 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8800 is mapped but visible=0 child_visible=1 parent GtkBox 0xa3edad0 mapped=1

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8800 is mapped but not visible

(evolution:1790): Gtk-WARNING **: EAttachmentBar 0x97d8800 is mapped but visible=0 child_visible=1 parent GtkBox 0xa3edad0 mapped=1
^C^C
^C

I mean, I nothing unusual to do for it

(In reply to Mikhail from comment #5)
> $ evolution
> No bp log location saved, using default.
> [000:000] Browser XEmbed support present: 1
> [000:000] Browser toolkit is Gtk2.
> [000:002] Using Gtk2 toolkit

There might be something installed, something what breaks evolution for you. I bet for some 3rd party browser plugin, but I have no proof for it, neither idea what it can be. By the way, gtk2 is probably wrong, evolution uses gtk3.

*** Bug 1000932 has been marked as a duplicate of this bug. ***

Which browser??? On both systems at work and home I use Google Chrome. But at home I don't see this message in console.

That's the thing, some browser plugins can be shared between all browsers. These are stored either at
   /usr/lib64/mozilla/plugins
or at
   /usr/lib/mozilla/plugins
If you move away (do not delete) files from there, and run evolution, then the messages should go away too. I would try, as a test, to run without any plugins, whether it'll help to stabilize your machine (I think of the bug #995177 too).

Did you manage to play with the mozilla plugins directory, especially did it help with this and the bug #995177, please?

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.