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 1431618 - anaconda aborts (Pane is dead) with GLib-GObject:ERROR:gsignal.c:693:handler_unref_R: assertion failed: (hlist->tail_after == handler)
Summary: anaconda aborts (Pane is dead) with GLib-GObject:ERROR:gsignal.c:693:handler_...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1432436
TreeView+ depends on / blocked
 
Reported: 2017-03-13 12:41 UTC by Radek Vykydal
Modified: 2021-01-15 07:32 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1432436 (view as bug list)
Environment:
Last Closed: 2021-01-15 07:32:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
backtrace from core dump (783.87 KB, text/plain)
2017-03-13 12:41 UTC, Radek Vykydal 		no flags Details
program.log (16.64 KB, text/plain)
2017-03-13 12:43 UTC, Radek Vykydal 		no flags Details
anaconda.log (14.63 KB, text/plain)
2017-03-13 12:44 UTC, Radek Vykydal 		no flags Details
syslog (229.39 KB, text/plain)
2017-03-13 12:45 UTC, Radek Vykydal 		no flags Details
View All

Description Radek Vykydal 2017-03-13 12:41:52 UTC 
Created attachment 1262431 [details]
backtrace from core dump

Happens during 7.4 devel phase, eg with RHEL-7.4-20170310.n.0 compose.

When running anaconda kickstarts tests which run 4 installations in virtual machines in parallel on kvm hypervisor we are sometimes [1] hitting this crash:

GLib-GObject:ERROR:gsignal.c:693:handler_unref_R: assertion failed: (hlist->tail_after == handler)

Seems to be hit by this installer function in widgets/src/BaseWindow.c [2]:

void anaconda_base_window_clear_info(AnacondaBaseWindow *win) {
    if (!win->priv->info_shown)
        return;

    gtk_widget_hide(win->priv->info_bar);
->    gtk_widget_destroy(win->priv->info_bar);
    gtk_widget_destroy(win->priv->event_box);
    win->priv->info_shown = FALSE;
}


I am attaching backtrace.

NOTE: Some time ago we have been hitting also
GLib:ERROR:gmain.c:3141:g_main_dispatch: assertion failed: (source->context == context) 
in some installation instances but I've not been able to hit it last few weeks.

[1] It can be hit about every second (almost every) kickstart test batch running 11 tests (kickstart installations). The tests are scheduled so that 4 tests are run in parallel on the hypervisor.

[2] The code has been reworked on master:
https://github.com/rhinstaller/anaconda/commit/5b4513c104ff7fc3d04c469abcc997320f8827ef
Maybe it would fix the issue but there seems to be a wider context of the change.
Comment 2 Radek Vykydal 2017-03-13 12:43:47 UTC 
Created attachment 1262432 [details]
program.log
Comment 3 Radek Vykydal 2017-03-13 12:44:45 UTC 
Created attachment 1262433 [details]
anaconda.log
Comment 4 Radek Vykydal 2017-03-13 12:45:13 UTC 
Created attachment 1262434 [details]
syslog
Comment 5 Radek Vykydal 2017-03-13 12:47:37 UTC 
(In reply to Radek Vykydal from comment #0)

> [2] The code has been reworked on master:
> https://github.com/rhinstaller/anaconda/commit/
> 5b4513c104ff7fc3d04c469abcc997320f8827ef
> Maybe it would fix the issue but there seems to be a wider context of the
> change.

David, you've been working on this stuff in Anaconda, do you have any hint?
Comment 6 David Shea 2017-03-13 14:44:17 UTC 
The change in 5b4513c1 was just to add the animation, not to address any particular bug. Based on the backtrace, it looks like either info_bar is being destroyed more than once, or there is a bug in gtk in the handling of the signal list.
Comment 7 Radek Vykydal 2017-03-14 12:54:14 UTC 
I can't see anything wrong on installer side.
Kalev (or someone from Gtk/Glib team), could you please check the backtrace in the description (Thread1) if it looks fine for you?
Are there any known issues or hints for debugging or pitfalls regarding the failing assert would point to?
Thank you.
Comment 8 Kalev Lember 2017-03-15 09:39:50 UTC 
Not sure what's going on, but maybe running anaconda under valgrind would reveal something? Adding mclasen to CC in case he has ideas.

Also, we have new glib2 and gtk3 coming to 7.4 (https://errata.devel.redhat.com/advisory/27092), would be interesting to know if this changes anything with this crash.
Comment 9 Radek Vykydal 2017-03-30 09:40:20 UTC 
Unlike the bug 1432436, I haven't hit the issue after the glib2 and gtk3 rebase so far.
Comment 11 RHEL Program Management 2021-01-15 07:32:47 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.