RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 845052 - segfault in e_shell_window_peek_shell after a new message arrived
Summary: segfault in e_shell_window_peek_shell after a new message arrived
Keywords:
Status: CLOSED DUPLICATE of bug 906267
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-01 15:22 UTC by David Jaša
Modified: 2013-05-09 18:50 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-09 18:50:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
evo backtrace (42.59 KB, text/plain)
2012-08-01 15:22 UTC, David Jaša 		no flags Details
View All

Description David Jaša 2012-08-01 15:22:05 UTC 
Created attachment 601767 [details]
evo backtrace

Description of problem:
segfault in e_shell_window_peek_shell after a new message arrived. Evolution was in the background

Version-Release number of selected component (if applicable):
evolution-2.28.3-25.2.el6.x86_64

How reproducible:
didn't repeat so far

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Interesting part of the backtrace:
Thread 1 (Thread 0x7f9291f45940 (LWP 11616)):
#0  0x00000000004120f6 in e_shell_window_peek_shell (window=0x90c9110) at e-shell-window.c:1101
        __inst = 0x90c9110
        __t = 8943056
        __r = <value optimized out>
        _g_boolean_var_ = <value optimized out>
        __PRETTY_FUNCTION__ = "e_shell_window_peek_shell"
#1  0x000000000041369d in impl_ShellView_setButtonIcon (_servant=<value optimized out>, id=0x9123810 "mail", iconName=0x7f92853daa25 "mail-unread", ev=<value optimized out>) at e-shell-view.c:83
        esw = <value optimized out>
        shell = <value optimized out>
        cis = {component_name = 0x77e760 "", icon_name = 0xaa8f110 "P\251y"}
#2  0x00000035acc08728 in GNOME_Evolution_ShellView_setButtonIcon (_obj=<value optimized out>, component=0x9123810 "mail", iconName=0x7f92853daa25 "mail-unread", ev=<value optimized out>) at Evolution-stubs.c:42
        _args = {0x7fff11287448, 0x7fff11287440}
#3  0x00000035acc08ad4 in e_component_view_set_button_icon (ecv=<value optimized out>, iconName=<value optimized out>) at e-component-view.c:146
        ev = {_id = 0x0, _major = 0, _any = {_type = 0x0, _value = 0x0, _release = 0 '\000'}}
#4  0x00007f92851415ea in real_flush_updates (o=<value optimized out>, event_data=<value optimized out>, data=<value optimized out>) at mail-folder-cache.c:199
        e = 0x79a950 [EMEvent]
        t = 0xaa8f110
        component = <value optimized out>
        model = 0x77e760 [EMFolderTreeModel]
        up = 0x1599ca0
#5  0x00007f9285146c75 in do_async_event (m=0x7b6f850) at mail-mt.c:686
No locals.
#6  0x00007f9285148829 in mail_msg_idle_cb () at mail-mt.c:493
        msg = 0x7b6f850
        __PRETTY_FUNCTION__ = "mail_msg_idle_cb"
#7  0x000000363ca38f0e in g_main_dispatch (context=0x6d0d30) at gmain.c:1960
        dispatch = 0x363ca37070 <g_idle_dispatch>
        was_in_call = 0
        user_data = 0x0
        callback = 0x7f9285148770 <mail_msg_idle_cb>
        cb_funcs = 0x363cce4150
        cb_data = 0x2e83810
        current_source_link = {data = 0x53fc200, next = 0x0}
        need_destroy = <value optimized out>
        source = 0x53fc200
        current = 0x742c30
        i = <value optimized out>
Comment 1 Milan Crha 2012-08-02 06:42:23 UTC 
Thanks for a bug report. Here [1] is an upstream bug about the same, but it was never fixed, due to lack of response from a reporter. Would you mind to try to reproduce this under valgrind, please? That's basically the point where the upstream bug got stuck. Before running evolution under valgrind make sure you'll have installed debuginfo packages at least for evolution-data-server and evolution, and that they are of the same version as your binary packages. Then run evolution like this:
   $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
and wait till you get a new message (probably after the initial fetching will be done). Even if it'll not crash, then the log.txt can contain the error information.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=585104
Comment 2 RHEL Program Management 2012-12-14 07:07:16 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 Milan Crha 2013-05-09 18:50:51 UTC 
I'm marking this as a duplicate of the newer bug, because it contains a patch for this.

*** This bug has been marked as a duplicate of bug 906267 ***
Note You need to log in before you can comment on or make changes to this bug.