Bug 849563

Summary: GTK UI seems to be broken sometimes
Product: [Fedora] Fedora Reporter: Jan Sedlák <jsedlak>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-24 13:50: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:
Description Flags
INSTALLATION SOURCE remains greyed out
software selection is broken
dialogs are displaced
installation destination dialog is too displaced
gziped logs
second gziped logs none

Description Jan Sedlák 2012-08-20 08:26:15 UTC
Created attachment 605597 [details]
INSTALLATION SOURCE remains greyed out

Description of problem:
From time to time, after I boot anaconda installer, button "INSTALLATION SOURCE" remains greyed out (see screenshot in first attachment) even when it initializes. Since then, UI seems to be broken - see screenshots in attachments.

How reproducible:
From time to time (badly reproducible)

Steps to Reproduce:
1. Have a bad luck
2. Boot TC3 installer

Actual results:
"INSTALLATION SOURCE" remains greyed out. UI is broken.

Expected results:
Working UI

Additional info:
It happens in cca. 25% of cases, mostly three to five times in a row (it happens again after reboot).

Comment 1 Jan Sedlák 2012-08-20 08:27:09 UTC
Created attachment 605598 [details]
software selection is broken

Comment 2 Jan Sedlák 2012-08-20 08:28:24 UTC
Created attachment 605599 [details]
dialogs are displaced

Comment 3 Jan Sedlák 2012-08-20 08:29:21 UTC
Created attachment 605600 [details]
installation destination dialog is too displaced

Comment 4 Jan Sedlák 2012-08-20 09:10:40 UTC
I think that it happens when "Downloading package metadata" takes too long (it's displayed under both, "installation source" and "software selection").

Comment 5 Chris Lumens 2012-08-20 15:40:04 UTC
There are several problems here all in the same bug report, which makes it difficult to track any one thing.

How long something takes is not going to be the problem, because we're waiting for threads to finish before updating the UI.  We're not just blindly waiting a certain amount of time.

Your screen shot in comment #1 is probably related to comps/yum/anaconda changes that have not all shown up in the same tree at the same time.

I don't know why your screens are shrunk down like that, but I've seen it from a few other people too.  I cannot reproduce it so I can't work on it.

Comment 6 Chris Lumens 2012-08-20 19:55:36 UTC
Yeah okay, I am seeing all these problems now too.  When the source spoke claims it's ready (but is still greyed out), can you click on a spoke and then check your X.log and see if it looks like the bottom of mine:   http://clumens.fedorapeople.org/X.log

Comment 7 Jan Sedlák 2012-08-21 10:37:30 UTC
Sorry, but no. Bottom of X.log looks normal, with:
[    24.086] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[    24.087] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[    24.087] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[    24.087] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[    24.087] (II) VMWARE(0): VMMOUSE DEVICE_ON
[    24.087] (II) VMWARE(0): vmmouse enabled
[    24.088] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse0)
[    24.088] (II) No input driver specified, ignoring this device.
[    24.088] (II) This device may have been added with another device file.

Comment 8 Chris Lumens 2012-08-21 17:28:17 UTC
When you hit this problem, can you please grab /tmp/anaconda.log and /tmp/syslog and attach them to this bug report?  I am only intermittently able to reproduce this bug, and other people I've had check are not having a lot of luck with it either.  Thanks.

Comment 9 Jan Sedlák 2012-08-22 08:40:51 UTC
I've gziped whole /tmp directory (except of tmux-0/, yum.cache/ and yum.root/). For me, it's hard to reproduce it reliably too. Best chance is to "start installation as quickly as possible" (as soon as the "Choose language" appears, click on "continue"), but you have to try it several times.

Comment 10 Jan Sedlák 2012-08-22 08:54:12 UTC
Created attachment 606176 [details]
gziped logs

Comment 11 Jan Sedlák 2012-08-22 09:23:56 UTC
I've also attached log from successful instalator startup. Only difference I see is different order of modprobe/mount at the end of program.log and additional "WARN" and "DEBUG" at the end of storage.log in unsuccessful instalator startup log.

Comment 12 Jan Sedlák 2012-08-22 09:24:21 UTC
Created attachment 606183 [details]
second gziped logs

Comment 13 Chris Lumens 2012-08-24 13:50:48 UTC

*** This bug has been marked as a duplicate of bug 849211 ***