Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37307 - [evolution] freeze on new mail

Attached to Project: Arch Linux
Opened by Alexandre (agamemnon) - Saturday, 12 October 2013, 09:47 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 16 November 2014, 18:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

Hi!

I have a problem with Evolution 3.10.
When I try to open a new mail, evolution starts to use 100% cpu and freeze. Kill the processus is the only way to close Evolution.
It acts the same way with reply and forward and I can't write any mail.

Additional info:
* package version(s)
* config and/or log files etc.

System up-to-date without testing packages. Gnome 3.10.

When I start Evolution with terminal, it shows many errors:

** (evolution:2687): CRITICAL **: categories_icon_theme_hack: assertion 'filename != NULL && *filename != '\0'' failed

** (evolution:2687): WARNING **: The set_id method on WebKitDOMHTMLElement is deprecated. Use the one in WebKitDOMElement instead.

Steps to reproduce:

Open Evolution and try to write a new mail.
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 16 November 2014, 18:37 GMT
Reason for closing:  Works for me
Comment by Enoon Emanon (deraffe) - Tuesday, 29 October 2013, 22:40 GMT
I see the same behavior on my system. Somehow I managed to write an email after killing evolution several times earlier, but not today.

Additional info: Apart from taking up as many CPU cycles as it can get, its memory consumption also skyrockets (which leaves me with killing the process as the only viable option before my system gets unresponsive). In addition, dconf-service shows heightened activity.

I couldn't get anything sensible out of a strace run I did, apart from lots of UDP socket errors (ENOAGAIN), which are apparently business as usual.
Comment by kodiak (kodiak) - Monday, 17 February 2014, 22:31 GMT
Yepp, same experiences here with 3.10.4 on 32 bit.
Comment by mattia (nTia89) - Sunday, 16 November 2014, 14:33 GMT
I can't reproduce the bug
because we are talking about an old version of evolution I think we can close the bug

Loading...