Bug 1004477 - White Screen of Death after "I accept my fate."
Summary: White Screen of Death after "I accept my fate."
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: David Shea
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-04 17:46 UTC by Martin
Modified: 2015-09-08 01:31 UTC (History)
9 users (show)

Fixed In Version: 1.12.2-1.fc23
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-07 16:35:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
console 1 (36.26 KB, image/png)
2013-09-04 17:46 UTC, Martin
no flags Details
console 3 (68.45 KB, image/png)
2013-09-04 17:47 UTC, Martin
no flags Details
console 4 (79.49 KB, image/png)
2013-09-04 17:48 UTC, Martin
no flags Details
console 4 without OOM kill (86.57 KB, image/png)
2013-09-05 16:24 UTC, Martin
no flags Details

Description Martin 2013-09-04 17:46:25 UTC
Created attachment 793760 [details]
console 1

Description of problem:
When I click on "I accept my fate.", I got white screen instead of hub.

Version-Release number of selected component (if applicable):
anaconda 20.9-1
20130903 nightly build

How reproducible:
always

Steps to Reproduce:
1. Boot 20130903 nightly build from PXE
2. click on "Continue"
3. click on "I accept my fate."

Actual results:
White Screen of Death

Expected results:
main hub

Additional info:
17:26:46,819 INFO anaconda: /sbin/anaconda 20.9-1
17:26:47,234 INFO anaconda: 1048576 kB (1024 MB) are available
17:26:47,234 INFO anaconda: check_memory(): total:1024, needed:512, graphical:512
17:26:47,280 INFO anaconda: anaconda called with cmdline = ['/sbin/anaconda']
17:26:47,281 INFO anaconda: Default encoding = utf-8
17:26:47,787 INFO anaconda: Display mode = g
17:26:47,789 INFO anaconda: 1048576 kB (1024 MB) are available
17:26:47,789 INFO anaconda: check_memory(): total:1024, needed:512, graphical:512
17:26:48,959 DEBUG anaconda: X server has signalled a successful start.
17:26:48,968 INFO anaconda: Starting window manager, pid 914.
17:26:49,068 INFO anaconda: Started spice-vdagent.
17:26:52,039 WARN anaconda: module import of __init__ failed: <type 'exceptions.AttributeError'>
17:26:52,042 WARN anaconda: module import of __init__ failed: <type 'exceptions.AttributeError'>
17:26:52,043 INFO anaconda: using only installclass _Fedora
17:26:53,304 INFO anaconda: bootloader GRUB2 on X86 platform
17:26:53,306 INFO anaconda: bootloader GRUB2 on X86 platform
17:26:53,446 DEBUG anaconda: network: devices found ['eth0']
17:26:53,639 DEBUG anaconda: updating hostname dhcp131-64.brq.redhat.com
17:26:53,663 INFO anaconda: Running Thread: AnaStorageThread (140137121163008)
17:26:53,665 INFO anaconda: Running Thread: AnaTimeInitThread (140137112770304)
17:26:53,685 INFO anaconda: Running Thread: AnaWaitForConnectingNMThread (140137104377600)
17:26:53,695 INFO anaconda: Running Thread: AnaPayloadThread (140137095984896)
17:26:53,746 INFO anaconda: got 2 NTP servers from DHCP
17:26:53,819 INFO anaconda: Thread Done: AnaWaitForConnectingNMThread (140137104377600)
17:26:53,863 INFO anaconda: Running Thread: AnaGeolocationRefreshThread (140137104377600)
17:26:53,864 INFO anaconda: Starting geolocation lookup
17:26:53,869 INFO anaconda: Geolocation provider: Fedora GeoIP
17:26:55,073 INFO anaconda: Geolocation lookup finished in 1.2 seconds
17:26:55,106 INFO anaconda: territory: US
time zone: America/New_York (from GeoIP)
17:26:55,107 INFO anaconda: Thread Done: AnaGeolocationRefreshThread (140137104377600)
17:26:56,953 INFO anaconda: Thread Done: AnaStorageThread (140137121163008)
17:26:57,009 INFO anaconda: Thread Done: AnaTimeInitThread (140137112770304)
17:26:58,031 INFO anaconda: Thread Done: AnaPayloadThread (140137095984896)
17:27:14,360 WARN anaconda: /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/utils.py:103: Warning: gsignal.c:3346: value location for 'gboolean' passed as NULL
  AnacondaWidgets.lb_destroy(lightbox)
 
17:27:16,398 DEBUG anaconda: network standalone spoke (init): completed: True
17:27:17,988 INFO anaconda: Running Thread: AnaDateTimeThread (140137095984896)
17:27:18,104 INFO anaconda: fs space: 0 B  needed: 3 GB
17:27:19,207 INFO anaconda: Thread Done: AnaDateTimeThread (140137095984896)
17:27:20,136 WARN anaconda: /usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/__init__.py:254: Warning: g_object_disconnect: invalid signal spec "button-release-event"
  self.window.clear_info()
 
17:27:20,189 INFO anaconda: fs space: 0 B  needed: 3 GB
17:27:21,005 INFO anaconda: fs space: 0 B  needed: 3 GB
17:27:22,048 INFO anaconda: Running Thread: AnaSourceWatcher (140137121163008)
17:27:22,102 INFO anaconda: fs space: 0 B  needed: 3 GB
17:27:22,223 INFO anaconda: Running Thread: AnaSoftwareWatcher (140137104377600)
17:27:22,263 DEBUG anaconda: Setting up repos: []
17:27:22,375 INFO anaconda: Thread Done: AnaSourceWatcher (140137121163008)
17:27:22,603 INFO anaconda: Running Thread: AnaStorageWatcher (140137121163008)
17:27:22,636 INFO anaconda: Thread Done: AnaStorageWatcher (140137121163008)

Comment 1 Martin 2013-09-04 17:47:13 UTC
Created attachment 793761 [details]
console 3

Comment 2 Martin 2013-09-04 17:48:06 UTC
Created attachment 793763 [details]
console 4

I can reproduce it also with 20130831, but not with TC2 image.

Comment 3 David Shea 2013-09-04 18:21:36 UTC
Based on the console 4 screenshot, the VM ran out of memory and the kernel killed anaconda. Does this occur in a VM with more memory available?

Comment 4 Martin 2013-09-05 16:15:38 UTC
I use 1 GB RAM, which is default for Fedora 19 in virt-manager.
But I can't reproduce this bug with TC4 images, nor 20130904 nighly build. Have you tried to fix it or is this heisenbug?

Comment 5 Martin 2013-09-05 16:24:16 UTC
Created attachment 794354 [details]
console 4 without OOM kill

It's definitively a heisenbug. I can reproduce it with 20130903 nightly build on both i686 and x86_64, but with TC4 or 20130904 only on i686.

I have console 4 screenshot after WSoD, but without OOM kill.

Comment 6 Leslie Satenstein 2015-08-11 20:59:48 UTC
This is back for Fedora 23 

Fedora-Workstation-netinst-x86_64-23_Alpha_TC2.iso

This problem has to be reopened. This is how to cause it to occur

After accepting the warning message, if the continue happens to be clicked before the above message is cleared from the screen (because it may take a few seconds to disappear), the text is gone from the white rectangle.

When this happens, clicking on Continue is ineffective, clicking on the white rectangle locks up anaconda with only the system reset button on the computer as the only recourse.

This problem can be demonstrated with

Fedora-Workstation-netinst-x86_64-23_Alpha_TC2.iso

Comment 7 David Shea 2015-08-17 14:24:39 UTC
Thank you for the explanation, I'm able to reproduce this.

Comment 8 Leslie Satenstein 2015-08-18 21:12:20 UTC
David

You have my email address. Can you advise me when you would like me to stress test this aspect of anaconda?

Regards

Comment 9 Fedora Update System 2015-09-03 19:33:47 UTC
python-blivet-1.12.2-1.fc23 anaconda-23.19.2-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-15030

Comment 10 Fedora Update System 2015-09-04 07:33:18 UTC
anaconda-23.19.2-1.fc23, python-blivet-1.12.2-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update anaconda python-blivet'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15030

Comment 11 Fedora Update System 2015-09-07 16:35:26 UTC
anaconda-23.19.2-1.fc23, python-blivet-1.12.2-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 12 Leslie Satenstein 2015-09-08 01:31:35 UTC
Thank you David and Martin.


Note You need to log in before you can comment on or make changes to this bug.