| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
Adds logic to treat a partitioned disk with no partitions as empty
if storage.config.initializeDisks is True.
Removes some logic that doesn't belong related to clearing of
non-existent devices.
Consolidates logic for determining whether a disk is "empty"
into a nested function.
|
|
|
|
|
|
| |
It is important not to base device type on the position of the
currently selected item in the deviceTypeCombo since its contents
vary.
|
| |
|
| |
|
|
|
|
| |
There is a filesystem type combo for this purpose.
|
|
|
|
|
| |
This also expands the set of exceptions handled when testing the
passphrase, which catches the case of an empty passphrase.
|
|
|
|
|
| |
We don't prompt for passphrases for encrypted devices, so this can
only improve the quality of our device clearing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This change was introduced in commit c308c8978e2d27 that is a port
from rhel6-branch where we use anaconda.id.bootloader instead of
storage.bootloader.
|
| |
|
|
|
|
| |
We had everything except the function to display the error. Oops.
|
|
|
|
|
|
| |
Referencing baseRepo there can take an awful long time, which happens as part
of building the first hub. This means there's a long time where the betanag
screen is sitting in front of the user completely unresponsive.
|
| |
|
|
|
|
|
| |
Previous patches to this file were trying to be too clever. Instead, just
uppercase the return value and call it good enough.
|
|
|
|
| |
This reverts commit 03af0cbf7fdbaba1b5d53cfad0d77902c5f829a4.
|
|
|
|
| |
This reverts commit 21a9c715ead09d84306ed1a4dd711f947596f4c5.
|
|
|
|
|
| |
This removes a thin little grey border you could see if you looked close
enough.
|
| |
|
|
|
|
|
|
|
|
|
| |
move doesn't work because /run/ is a shared filesystem. So do as
systemd suggests, mark the filesystem as private. We don't know of any
reason in anaconda for the filesystem to be shared anyway.
This hack can go away if/when the kernel ever allows moving mounts
within a shared filesystem.
|
|
|
|
|
|
| |
This reverts commit 799d526f3b8a0586c5c716ae1adf9af79883d9de.
With the new threading code in place, this is no longer needed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Marks all methods containing mostly gtk calls as gtk_thread_wait
or gtk_thread_nowait
- Uses gtk_call_once instead of GLib.idle_add to make sure the
method is called only once (returns False)
- Removes some code from the threading locks, because it wasn´t
touching Gtk at all
This change was discussed in the mailinglist here:
https://www.redhat.com/archives/anaconda-devel-list/2012-October/msg00030.html
The main point was:
According to the Gtk team, the gdk_threads_enter/leave pair should
not be used at all (and they have apparently discouraged usage of
it since early releases of Gtk2). Moreover in the current Gdk docs
(http://developer.gnome.org/gdk3/stable/gdk3-Threads.html)
those functions are now marked as deprecated.
The preferred way (and now the only way) is to use g_idle_add
(GLib.idle_add) with a callback method to schedule GUI changes.
The callback method will then get called by the Gtk main loop so
no locking is needed (and GLib.idle_add performs none). But that
is also the reason why everything Gtk related must be done from
the mainloop thread either directly or via idle_add.
|
|
|
|
| |
exception handler be called by Gtk only once
|
| |
|
|
|
|
|
|
| |
When replacing the last layout in the list, user may mark the same
layout (among the others) for adding. In such cases we shouldn't
remove the layout from the list and just leave it where it was.
|
|
|
|
|
| |
Since we add actions to main loop, not releasing lock may lead
to deadlock.
|
|
|
|
|
|
|
|
|
|
|
| |
If we want tboot to keep getting used, we need to configure
new-kernel-pkg to tell grubby to do that. When grubby finds a multiboot
stanza as the default template, it won't use the multiboot parts of the
template unless specifically configured to. This patch adds a
configuration option to tell grubby that we always want to use the tboot
multiboot kernel by default when we add a new kernel.
Signed-off-by: Peter Jones <pjones@redhat.com>
|
| |
|
|
|
|
| |
Resolves: rhbz#747278
|
|
|
|
| |
Related: rhbz#838736
|
| |
|
|
|
|
|
| |
There's no need for these to be editable, and setting this off also helps a
little with the packing.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
You've already bought into doing something destructive, so why not have the
chance to really tear things up? Also, make the cancel button the default
action.
|
|
|
|
|
| |
Most of this patch is just un-indenting stuff. The rest is replacing references
to currentPage with references to selector._root. Same data, really.
|
|
|
|
|
|
|
|
|
| |
First, it simply does not work right now. Secondly, it's not at all obvious
in the UI how you would go about doing this. Click on the expander and then
hit remove? Yes, but then the expander collapses and you still have a
mountpoint displayed on the right. Which thing are you deleting then?
We need a way to do this, but I don't think this code is it.
|
| |
|
|
|
|
|
|
| |
It's possible to end up in a situation where the root is "None Linux None for
None" which just looks silly. This happens in my testing if you kill an
install after it's made partitions, but before fedora-release gets installed.
|
| |
|
|
|
|
|
|
|
|
| |
Without this change we were automatically selecting the first
environment from the list, and adding it to the existing package data.
This means no matter what you had in %packages you also got the GNOME
environment. Obviously this is wrong, so we don't autoselect if we're
doing an automated install and have package data.
|
|
|
|
|
|
| |
This brings it up to feature parity with the gui spoke, mostly. Still
don't have a way to completely disable the password here, but that's a
good thing for now.
|