| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This was introduced by 576349d2, which fixed a similar deadlock but accidentally
introduced this one. Tweak that patch just a little to make sure the
gdk_threaded only gets applied when needed.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This uses the main loop to mark the button as insensitive until software
selection is ready, then the user can press the button and go to that spoke.
I'd also like to add a spinner to the button, but that appears to be beyond
glade for the moment.
|
| |
|
| |
|
| |
|
|
|
|
| |
This is to make way for the boot device picking option.
|
|
|
|
|
|
|
|
| |
packagesSeen is a value, that should not be changed in spokes. Using
it as a condition for the completed property results in no way of
completing software spoke in kickstart installation without %packages
section. Without %packages section in kickstart, SoftwareSpoke's
completed method should use the same code as in manual installations.
|
|
|
|
| |
Not just when we have old devices set up as mounts.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This avoids a confusing situation where you return to the hub and get an
error dialog you can only exit anaconda from. Also, put errors from
doAutoPartition into self.errors on the storage spoke so they are viewable
by clicking on the info bar.
|
|
|
|
|
|
|
| |
The idea here is that the dialog says you can make enough space to install by
resizing or deleting, but only ever mentions how much space is available if you
do resizing. That seems weird to me, so I've added another row that shows how
much space is in all the selected disks.
|
| |
|
|
|
|
|
| |
With the resize dialog, we have UI for everything now and can send the user
through a path that'll allow them to make space.
|
| |
|
|
|
|
|
|
|
|
|
| |
This allows shrinking and deleting of individual partitions in order to make
enough room to do an installation. All shrinking and deleting happens as
scheduled actions which will be executed later, therefore eliminating the need
for progress and error reporting in this dialog.
It's not hooked up quite yet.
|
|
|
|
|
|
| |
Without this whole GUI hangs in case this dialog is run to choose
replacement for the last layout in the list of added layouts (minus
button clicked).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This gets used if text mode is requested or if X startup fails. We
don't (yet) prompt the user for advanced VNC configuration such as port
number or to connect to an existing system.
|
|
|
|
|
| |
cmdline means no prompting, so if we have spokes that are incomplete,
raise the error.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add/set mountpoint:
- new device
- add selector to new install page
- new filesystem on old device
- add selector to new install page
- remove selector(s) from old install root page(s)
- old filesystem on old device
- add selector to new install page
- leave selector(s) in old install root page(s)
Remove mountpoint from new install page:
- new device
- destroy the device (cancel its scheduled creation)
- remove the selector from the new install page
- new filesystem on old device
- reset the device to its initial state
- remove the selector from the new install page
- add the selector(s) back to any old install page(s)
- old filesystem on old device
- reset the device to its initial state (mountpoint)
- remove the selector from the new install page
- leave the selector(s) in any old install page(s)
Remove mountpoint from old install page:
- destroy the device
- remove selector(s) from any old or new install page(s)
Other changes:
- Remove remove_from_root method.
- We don't want to modify the Root instances. We won't be showing
devices that are no longer present, so there should be no harm
in leaving the Roots intact.
- Remove _update_ui_for_removals since it's only called from one method.
- Protect more signal handlers from running during refresh.
- Use constants for flipping pages in the partitionsNotebook.
|
| |
|
| |
|
|
|
|
| |
This allows users to assign mountpoints to existing devices.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Especially the year set in HW clock (and thus as system date) may
be out of our range of years, that can be selected in the combobox.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This follows the same design as GUI. If the install is automated, and
all the spokes are complete, proceed into the installation phase.
However if there are incomplete spokes, let the user finish those
spokes. As soon as all spokes are complete jump straight to the install
phase.
Note that any new spoke that has a background process that could make it
not be "ready" immediately is going to have to be accounted for here,
which is ugly. Perhaps a object attribute that is a list of potential
threads to join would work?
|
|
|
|
|
|
| |
We were just eating all errors, which is not correct. This will accept
errors that might be fixable, but lets other errors bubble up and end
the install. It also manipulates the ready status correctly.
|
|
|
|
|
| |
This brings things more in-line with the GUI spoke. Also it imports the
thread stuff only once rather than multiple times.
|
|
|
|
|
|
|
| |
This is necessary for doing installs via kickstart where we've got the
data even though we haven't gone through the spoke.
Also handle the case where the account could be locked.
|
| |
|
|
|
|
|
| |
We need this to quit when handling errors, since doing a sys.exit() from a
thread only kills the thread and not the main program.
|