Bug 1619811

Summary: Frustrating GTK-Warnings in VNC installs
Product: Red Hat Enterprise Linux 7 Reporter: Ken Green <Ken.Green>
Component: gtk3Assignee: Benjamin Otte <otte>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: vponcova
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-15 07:41:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
set of the files from under /tmp on the install target system, these are from a KVM based VM. none

Description Ken Green 2018-08-21 19:22:05 UTC
Created attachment 1477668 [details]
set of the files from under /tmp on the install target system, these are from a KVM based VM.

Description of problem:

When installing RHEL7.4 or RHEL7.5 using VNC and a serial console you get a whole load of GTK-Warnings after being told to "Please manually connect your vnc client to ..."

 


Version-Release number of selected component (if applicable):
The problem occurs with both RHEL7.4 & 7.5, it works OK 7.3

The output is

18:51:53 Starting VNC...
18:51:55 The VNC server is now running.
18:51:55

You chose to execute vnc with a password.


18:51:55 Please manually connect your vnc client to bl12.r214.example.com:1 (192.168.72.12:1) to begin the install.
18:51:55 Attempting to start vncconfig

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

There seems to be a couple of second delay between the message about "Attempting to start vncconfig" and the Gtk-WARNINGs.


These tests were performed on an HPE ProLiant bl460c Gen8 blade and also on a virtual machine running under KVM. 

Both the ProLiant and the VM were PXE booted (they are legacy BIOS based). 
The entry in the pxelinux config file was

label rh75
  kernel rhel75x86_64/vmlinuz
  append initrd=rhel75x86_64/initrd.img  inst.repo=ftp://bl24/rhel75x86_64 console=ttyS0,115200 inst.vnc inst.vncpassword=install




How reproducible:
All the time,


Steps to Reproduce:
1. PXE boot the intended system
2. Boot using the options
label rh75
  kernel rhel75x86_64/vmlinuz
  append initrd=rhel75x86_64/initrd.img  inst.repo=ftp://bl24/rhel75x86_64 console=ttyS0,115200 inst.vnc inst.vncpassword=install


3. Sit back and wait, if there are any spare NICs in the system you'll have to wait through the annoying 60s DHCP timeout for each of them.

4. Eventually on the console you'll get Gtk warning above.


Actual results:
18:51:53 Starting VNC...
18:51:55 The VNC server is now running.
18:51:55

You chose to execute vnc with a password.


18:51:55 Please manually connect your vnc client to bl12.r214.example.com:1 (192.168.72.12:1) to begin the install.
18:51:55 Attempting to start vncconfig

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(anaconda:1811): Gtk-WARNING **: Allocating size to pyanaconda+ui+gui+MainWindow 0x2e80270 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?



Expected results:
(this was taken from repeating the same test using RHEL7.3)

Starting installer, one moment...
anaconda 21.48.22.93-1 for Red Hat Enterprise Linux 7.3 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * when reporting a bug add logs from /tmp as separate text/plain attachments
19:08:28 Starting VNC...
19:08:29 The VNC server is now running.
19:08:29

You chose to execute vnc with a password.


19:08:29 Please manually connect your vnc client to bl12.r214.example.com:1 (192.168.72.12:1) to begin the install.
19:08:29 Attempting to start vncconfig




Additional info:
I've attached a set of the files from under /tmp on the install target system, these are from a KVM based VM.

Comment 2 Vendula Poncova 2018-08-22 07:20:36 UTC
This is an issue in the GTK library: https://gitlab.gnome.org/GNOME/gtk/issues/658

Comment 5 RHEL Program Management 2021-02-15 07:41:48 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.