Bug 1305521 - evolution deadlocks on start under g_type_class_ref()
Summary: evolution deadlocks on start under g_type_class_ref()
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glib2
Version: 7.2
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Colin Walters
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-08 13:48 UTC by Jiri Koten
Modified: 2020-12-15 07:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:39:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
backtrace (25.20 KB, text/plain)
2016-02-08 13:48 UTC, Jiri Koten
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 674885 0 None None None 2017-11-13 10:33:21 UTC

Description Jiri Koten 2016-02-08 13:48:26 UTC
Created attachment 1122177 [details]
backtrace

Description of problem:
Sometimes when I start evolution, there is a deadlock and the window even won't show up. I have to kill the process (SIGKILL) and start evolution again.

Version-Release number of selected component (if applicable):
evolution-3.12.11-15.el7
glib2-2.42.2-5.el7

How reproducible:
random, cannot reproduce on purpose

Steps to Reproduce:
1. Start evolution


Actual results:
Evolution won't start, if I start it again I got error that another instance is already running.

Expected results:
No deadlock.

Additional info:

Comment 1 Milan Crha 2017-11-13 10:33:22 UTC
This might be a variant of a long standing upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=674885

Comment 3 RHEL Program Management 2020-12-15 07:39:59 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


Note You need to log in before you can comment on or make changes to this bug.