| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
| |
Using libnm-glib from a separate thread results in a hang, probably
because libnm-glib has to do some "loops magic" for its internal use
of DBus.
Signed-off-by: Vratislav Podzimek <vpodzime@redhat.com>
|
| |
|
|
| |
"b" means bits, which is definitely not what we want to display.
|
| |
|
|
|
|
|
|
| |
With the addition of Cinnamon and MATE and some others, there's now entirely
too much stuff in the environment window to fit without scrolling. Plus, I
guess smaller screens always needed to scroll. Without a scroll bar, GTK
puts this window in a really bizarre place. See the screenshot attached to
the bug.
|
| | |
|
| |
|
|
|
|
| |
Catch some common errors that are not practical to prevent via the
UI and show an error message instead of attempting to carry out the
request.
|
| | |
|
| |
|
|
|
|
| |
/boot can be on btrfs, lvm, or md. This should be handled in the ui.
Related: rhbz#864131
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Resolves: rhbz#862667
Resolves: rhbz#960994
|
| |
|
|
|
|
|
|
| |
BTRFS and RAID are not always in the device type combo, so we
can't count on using direct index access to the combo.
Resolves: rhbz#862667
Resolves: rhbz#860994
|
| | |
|
| |
|
|
|
|
|
|
| |
reIPL used to be ran via dispatch, and would trigger either a reboot or
a shut down. Now we'll run it as part of the s390 bootloader install.
The message warning users to reipl themselves is somewhat lost here,
something for another day perhaps. This at least gets the system
working right.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This keeps the ugly hack going, but it keeps us from crashing on the
s390 case where anaconda gets launched twice (once to prompt for ssh,
once inside tmux to do the actual install).
|
| |
|
|
|
|
| |
If anaconda is launched /inside/ tmux, the TMUX variable will be
present. This is the anaconda we want to attach to, so don't prompt for
ssh here.
|
| |
|
|
|
|
|
|
|
| |
When installing on s390x, we just want to run pure anaconda on the tty.
This will either detect s390x and print out ssh details for the user to
ssh in to continue the install (and get tmux), or if a kickstart was
provided and the RUNKS option was used it will just blast through the
kickstart in cmdline mode. Tmux doesn't work in x3270, the terminal for
s390x, so we have to avoid using it.
|
| |
|
|
|
| |
This is useful as the install user's shell, rather than having anaconda
direct as that shell.
|
| |
|
|
|
|
|
|
|
| |
Break out the setup of ARM-OMAP systems, as they need to have a vfat partition
at the start of the disk in order for the SOC to load the initial boot code.
This also sets the weight for the '/' partition to ensure it is the last
partition on the image.
Signed-off-by: Brian C. Lane <bcl@brianlane.com>
|
| |
|
|
|
|
| |
This likely hits every single kickstart install. Because we run execute
over and over again, we're eventually going to hit a situation where
storage just breaks.
|
| | |
|
| |
|
|
|
|
| |
Now that we're storing full languages in the store again (thanks to the
mangling crud from earlier), that's what needs to get expanded when we are
comparing the language setting from the command line or kickstart.
|
| |
|
|
|
|
|
| |
This doesn't fix the redraw-related size problem. I think that might just
be an artifact of not using a compositing manager. This merely attempts to
fix it so we don't display a spoke entirely smashed up in the upper left
corner of the screen.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
First, don't always put a cancel button on. That looks weird on the storage
spoke where we don't mention cancel. Second, change the order such that the
Quit or Cancel button comes left-most and is positioned secondarily.
|
| |
|
|
|
| |
Otherwise, the resize dialog is going to be referencing devices that are hidden
in the devicetree, which makes them basically not exist.
|
| |
|
|
| |
Otherwise, the resize dialog is going to be passed incorrect references.
|
| |
|
|
| |
users.Users() no longer takes an argument, so don't try to pass one.
|
| |
|
|
|
|
| |
Give up on getting cute with payload data to set required or not, just
always make the user visit it. Also don't default the kickstart data to
locked, that can confuse the UI
|
| |
|
|
|
|
|
| |
* log when threads are started and are finished
* log progress messages
* log all the running threads and their stack frame when USR2 is
received.
|
| |
|
|
| |
It needs to be more clear that deleting filesystems is also an option.
|
| | |
|
| |
|
|
|
| |
Otherwise, you'll end up in a situation where packages the previous and
current environment share will not get installed.
|
| |
|
|
|
| |
When the custom checkbox is selected, we need to make sure the software spoke
is ready when deciding whether the Modify button is sensitive or not.
|
| | |
|
| |
|
|
|
|
| |
Activating the checkbutton effectively sets the default behavior
of applying encryption to all new block devices, even in the
custom spoke.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This allows us to get/check/set passphrase and then call populate
to continue populating the devicetree to pick up devices descended
from the newly decrypted device.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Our forced packages should be marked for installation after all removals
have taken place.
|
