Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
While starting virt-viewer gnome-shell goes down into oops screen.
Version-Release number of selected component (if applicable):
gnome-shell-3.14.4-50.el7.x86_64
virt-viewer-2.0-10.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1.start virt-viewer
Actual results:
GS crash
Expected results:
no crash
Additional info:
no abrt crash, no backtrace in gdb, just SIGABRT caught. Reproduced on two independent boxes
Created attachment 1178915[details]
gnome-shlle gdb out
Program received signal SIGABRT, Aborted.
0x00007f5686ada1d7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);
Comment 7Ray Strode [halfline]
2016-07-12 16:58:49 UTC
Just to clarify a bit, the issue is caused by this commit:
Author: Florian Müllner <fmuellner>
Date: Wed Jul 6 19:56:47 2016 +0200
app: Add a construct-only app-info property
This will allow us to create a ShellApp from JS code, for instance
for .desktop files that aren't known to the AppSystem.
So that means the app-info property will get set unconditionally at instance creation time, even if app-info isn't explicitly set in the property list.
That commit changes _shell_app_new () to set "app-info" explicitly, but _shell_app_new_for_window() doesn't set "app-info" explicitly so the property will get set to NULL at creation time.
If i'm reading the code right, this will cause two things to happen:
1) app->info getting set to g_object_ref (NULL)
2) shell_app_get_name (app) will get called with app->info NULL and window_backed_app_get_window() will assert because app->running_state fails.
The patch in bug 674799 should address the second problem. The first problem probably causes noise in the log so it should probably get fixed too.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2258.html