Bug 892472
Summary: | Anaconda is unable to create windows when visiting the custom partitioning screen for the second time | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Dan Mashal <dan.mashal> | ||||||||||||||
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | urgent | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 18 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, kparal, robatino, sbueno, vanmeeuwen+fedora | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | All | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2013-01-07 14:03:28 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: | |||||||||||||||||
Bug Depends On: | |||||||||||||||||
Bug Blocks: | 752661 | ||||||||||||||||
Attachments: |
|
Description
Dan Mashal
2013-01-07 08:56:35 UTC
Reproduced. The window seems like stuck. +1 blocker I have learned that sometimes you need to visit the screen more than twice, sometimes twice is enough. It might be relevant to what exactly you click, or some race condition. Attaching logs from one such attempt. Created attachment 673849 [details]
anaconda.log
Created attachment 673850 [details]
anaconda.log
Created attachment 673851 [details]
packaging.log
Created attachment 673852 [details]
program.log
Created attachment 673853 [details]
storage.log
Created attachment 673854 [details]
syslog
This is the same as bug 875291. And I am extremely pessimistic on the chances for figuring out a fix for this. *** This bug has been marked as a duplicate of bug 875291 *** |