Bug 1167658 - custom partitioning: after you press Done for the first time, Reset All stops working
Summary: custom partitioning: after you press Done for the first time, Reset All stops...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedFreezeException
: 1162880 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-25 09:16 UTC by Kamil Páral
Modified: 2017-12-12 10:13 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 10:13:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
video - cancel confirmation (720.46 KB, application/ogg)
2014-11-25 09:17 UTC, Kamil Páral
no flags Details
video - see warning (920.02 KB, application/ogg)
2014-11-25 09:17 UTC, Kamil Páral
no flags Details
video - re-enter screen (1005.35 KB, application/ogg)
2014-11-25 09:18 UTC, Kamil Páral
no flags Details
anaconda.log (24.20 KB, text/plain)
2014-11-25 09:18 UTC, Kamil Páral
no flags Details
program.log (25.63 KB, text/plain)
2014-11-25 09:18 UTC, Kamil Páral
no flags Details
storage.log (127.51 KB, text/plain)
2014-11-25 09:18 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2014-11-25 09:16:15 UTC
Description of problem:
In custom partitioning, Reset All button claims to reset the view to a current on-disk partition layout. But it works only initially. After you press Done for the first time, it no longer works. Tested on these use cases:

* Hit Done, but cancel the "Summary of changes" dialog
* Hit Done, and see a warning bottom bar pop up (e.g. missing swap)
* Hit Done, confirm changes, and then go back to custom partitioning screen

In all these cases, "Reset All" no longer works. See attached videos.

I tested on a disk with some existing partitions and also on an empty disk. Happens always.

Version-Release number of selected component (if applicable):
anaconda 21.48.16-1
F21 TC3 Server DVD x86_64

How reproducible:
always

Steps to Reproduce:
1. enter custom part
2. make some changes
3. hit Done
4. whatever happens, make sure you go back to custom part (read warnings, cancel confirmations, enter the dialog again, whatever)
5. try Reset All

Actual results:
Reset All doesn't work after you hit Done

Expected results:
Reset All works always

Additional info:
I'm appending logs from the last attempt - confirming changes and entering custom part screen again.

Comment 1 Kamil Páral 2014-11-25 09:17:34 UTC
Created attachment 961074 [details]
video - cancel confirmation

Comment 2 Kamil Páral 2014-11-25 09:17:57 UTC
Created attachment 961075 [details]
video - see warning

Comment 3 Kamil Páral 2014-11-25 09:18:26 UTC
Created attachment 961077 [details]
video - re-enter screen

Comment 4 Kamil Páral 2014-11-25 09:18:53 UTC
Created attachment 961078 [details]
anaconda.log

Comment 5 Kamil Páral 2014-11-25 09:18:55 UTC
Created attachment 961079 [details]
program.log

Comment 6 Kamil Páral 2014-11-25 09:18:58 UTC
Created attachment 961080 [details]
storage.log

Comment 7 Kamil Páral 2014-11-25 09:21:57 UTC
Proposing as a freeze exception. We could also consider it a blocker, if people judge it too serious and we find a matching criterion.

Comment 8 Scott Suehle 2014-11-26 20:12:04 UTC
Discussed at today's blocker review meeting [1]. Accepted as a punt. More information is needed to decide FE status. A proposed fix to look at would be really helpful.

[1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-11-12/

Comment 9 Mike Ruckman 2014-12-01 16:39:30 UTC
Discussed in 2014-12-01 blocker review meeting. Rejected as a FE: this is obviously a bit annoying, but it's too late for speculative FEs now, anaconda team doesn't have a clear fix for it, and it is workaroundable.

Comment 10 David Shea 2015-04-24 15:18:13 UTC
*** Bug 1162880 has been marked as a duplicate of this bug. ***

Comment 11 Fedora End Of Life 2015-11-04 12:31:35 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Kamil Páral 2015-11-04 14:19:44 UTC
Same issue on F23.

Comment 13 Fedora End Of Life 2016-11-24 11:18:46 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 14 Kamil Páral 2016-11-24 12:01:39 UTC
Sure, still broken.

Comment 15 Fedora End Of Life 2017-11-16 19:06:23 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 16 Fedora End Of Life 2017-12-12 10:13:24 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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