Bug 1328720 - virt-manager coredump when remote connection by ssh without -X
Summary: virt-manager coredump when remote connection by ssh without -X
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gtk3
Version: 7.3
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Benjamin Otte
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-20 07:27 UTC by Xiaodai Wang
Modified: 2020-12-15 07:41 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:41:05 UTC
Target Upstream Version:

Attachments (Terms of Use)
virt-manager debug log (13.99 KB, text/plain)
2016-04-20 07:28 UTC, Xiaodai Wang 		no flags Details
virt-manager coredump log (68.31 KB, text/plain)
2016-04-20 07:28 UTC, Xiaodai Wang 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Xiaodai Wang 2016-04-20 07:27:34 UTC 
Description of problem:
virt-manager coredump when remote connection by ssh without -X

Version-Release number of selected component (if applicable):
virt-manager-1.3.2-1.el7.noarch

How reproducible:
100%

Steps to Reproduce:
1. Login the host by ssh without "-X".
# ssh root@$hostip

2. Startup virt-manager.

Actual results:
core dump occurs after starting virt-manager.

Expected results:
virt-manager should not core dump and "Cannot open X display" error should display.

Additional info:
Comment 1 Xiaodai Wang 2016-04-20 07:28:10 UTC 
Created attachment 1148877 [details]
virt-manager debug log
Comment 2 Xiaodai Wang 2016-04-20 07:28:39 UTC 
Created attachment 1148878 [details]
virt-manager coredump log
Comment 4 Jaroslav Suchanek 2016-04-20 10:55:54 UTC 
Well, crashed in gtk3, moving to the respective component for further analysis.
Comment 6 RHEL Program Management 2020-12-15 07:41:05 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.