notsure.jpg

Has anyone ever found themselves thinking anything beyond the apps and perhaps the files lenses are useful? Only half /s here, I love Unity as much as the next guy (maybe even more), but perhaps my workflow is just stuck in the past as I never even touch the Dash unless I need an app not currently locked to my Launcher. The first thing I do after installing a recent release is a big apt-get –purge for all other scopes, just to better see those apps which are all I (ever) need.

Note: I’m attaching a video below demonstrating the issue. In it I’m reproducing the problem with the amd64 ISO of 15.04.

Steps to reproduce:
1. Have a (virtual) machine with a clean 10 GB hard disk and 8 GB of RAM.
2. Start the installer, select ”Erase disk and install Ubuntu”, click ”Install now”.

What happens:
A ”Do you want to return to the partitioner?” window pops up, saying ”Some of the partitions you created are too small. Please make the following partitions at least this large:

/ 3.5 GB

If you do not go back to the partitioner and increase the size of these partitions, the installation may fail.”

Selecting Continue then goes on to an installation which fails due to lack of space as promised. This is because the installer has partitioned the disk with a 8+ GB swap partition, and only what remains of the 10 GB after that allocated to /.

What I expect to happen:
I know this is a tricky corner case, but I think there are better ways to deal with it than exhibited by the installer above. Here are some alternative suggestions I came up with:

1) change the way the disk space requirement is calculated for the ”Preparing to install” view: make it require at least the minimum ”/” size + expected swap size, thus notifying the user beforehand if the requirement is not met. (As you see in the video, currently it has the green checkmark even when the installer is about to fail predictably.)

2) have the installer select a partitioning scheme where ”/” is the minimum required and allocate whatever remains for swap; warn the user that swap will be too small to do hibernation.

3) at the very least, have the ”Do you want to return to the partitioner?” window describe the situation better. It was the biggest source of confusion for me because the wording implied I had partitioned the disk (which I hadn’t done) and prompting me to ”return to the partitioner” where I hadn’t been to.

The setup for unlocking an encrypted volume during boot using (only) a keyfile (on a detachable USB drive) usually calls for a keyscript to be specified as one of the encrypted volume’s options. But with systemd, such encrypted volumes can only be unlocked during boot by typing in a passphrase.

Steps to reproduce:
1. Have a LUKS encrypted volume.
2. Have said volume specified in /etc/crypttab, with keyscript= option pointing to your script for outputting the unlocking key.
3. Boot.

What I expect to happen:
To have the volume unlocked by the script at boot time without manual intervention.

What happens instead:
Plymouth shows a prompt to enter a valid passphrase for the volume.

Workarounds:
Apparently the options for unlocking encrypted drives, including keyscript, can also be specified at the kernel command-line, without crypttab, and according to yaantc at Hacker News [1] this can be used to work around the issue. I haven’t personally tried this.

* [1] https://news.ycombinator.com/item?id=8477913

@trentrichardson I’ve just tested the branch with the change and it’s working perfectly.

Hey @trentrichardson, and thanks for the response! The best I could figure in the meantime was to initialize the prompt differently in each branch, like so:

    if (user.isSignedIn) {
        states = {
            signOut: states.signOut,
            signIn: states.signIn,
            register: states.register
        };
    } else {
        states = {
            signIn: states.signIn,
            signOut: states.signOut,
            register: states.register
        };
    }
    thePrompt = $.prompt(states);

But it’s definitely better to have true support for this in the extension itself. Excellent!

Sorry if this is obvious, but how can I open a multiple-state prompt in a specific state other than the first one in the states object? In other words, in the first statesdemo example, how can I open the prompt in state1 instead of state0?

I’m working on a login/logout/registration form with each of the three as a separate state and would like to start the prompt in either the ”log in” or ”log out” state depending on whether the user is currently logged in or not.

(I’m trying to work out the solution reading Impromptu’s source code, but figured I’d also pose this question here for others like me to find in the future.)

Aww yiss, kiitoksia!

Onko kukaan löytänyt suorien lähetysten RSS-syötettä?

Itte tykkäsin aina enemmän salaliittojaksoista, Monster of the Weekit olivat laadultaan aina vähän hit and miss. Lisäksi koin niiden ”lopussa kaikki palaa ennalleen niin että seuraavassa jaksossa ei ole enää mitään muistijälkiä tästä jaksosta” -asetelman ärsyttävän lapsellisena, se muistutti Simpsoneita (jolle saman tyylin olin valmis sallimaan, koska se oli piirretty komedia). Joitain pieniä visuaalisia viittauksia Salaiset kansiot toki myös menneitten MotW-jaksojen tapahtumiin silloin tällöin ruudulle heitti, ja tietysti sitten Toomsista tykkäsin juuri siksi, että hahmo teki comebackin myös myöhemmässä jaksossa.

Muistan sarjaa 90-luvulla katsellessani pitäneeni sellaista koko kauden tai jopa sarjan ylitse ulottuvaa juonikaarta jotenkin uutena ja ihmeellisenä ilmiönä, mutta en tiedä oliko se tosiasiassa niinkään radikaalia kuin sittenkin enemmän seurausta siitä, etten juurikaan ollut myöhäisillan tv-sarjoja ennen X-Filesia katsellut. Mutta nykypäivän poliisisarjoista (varsinkin Foxilla) on kyllä helppo nähdä, että niissä on paljon Salaisten kansioiden perintöä.