Multiple everything - using VMWare, VirtualBox and Multisystem usb drives
Recently there was an post on Hacker News about collective nouns for birds in English. I run loads of virtual machines on my computer and I wonder what they should be called - 'a herd of virtual machines'? I have the mediocre Windows 7 Home Premium, and I wonder if that should be called a 'A badling of windows' after the phrase 'A badling of ducks'.
The big change for me in my computing evironment recently has been using virtual machines all the time instead of setting up my computers with multiple boot options. For work I use a 27 inch Macintosh with 8 GB of memory, running Windows 7 Home Premium and Kubuntu 11.04 under VMWare as guests under Mac OS X as the host. We have moved from scarcity in computer resources for programmers to a world where even the most under powered netbook can handle most of the things I need to do.
I spent most of last weekend preparing my HP 2133 netbook for use at the forthcoming Desktop Summit. I wanted to get it working well in advance as I had a lot of trouble with my netbook at the recent Qt Contributors Summit. At that conference I couldn't even get WiFi working for the first day or two, and it was only because I happened to bump into the awesome Paul Sladen from Canonical that I managed to get it working to a reliable standard at all.
Talking to Paul he didn't think he was any kind of power user (he works for Canonical as a UI designer), and that his suggestions to me about how to sort out my machine should be obvious. I'm not sure about what exactly I'm good at, but I think it is only programming and I am not a very good systems administrator (or a UI designer for that matter). But if I have a lot of trouble doing obvious things with my Linux portable I think you can assume anyone at all normal with be having even more trouble.
I found out about the Multisystem project, and managed to create a USB stick with Kubuntu 11.04, Ubuntu 11.04, OpenSUSE 11.4, Mandriva 2010, Mandriva 2011 RC2, Fedora 15, Debian Squeeze 6.0.1. Then I tried running each of these distributions in turn and trying to install them onto my HP 2133.
My Great White Hope was SUSE because that was the distribution that my HP 2133 originally came with. I never got it running when I first tried to boot my new HP 2133 because I got a 'grub error 18' or similar, after i got it home and tried to boot it - that would have put off 99% of potential Linux users straight away. The install of OpenSUSE 11.4 started and then after a while it died. Oh dear.
Next up was Fedora 15, and I got as far as the initial screen after being warning that my machine wasn't powerful enough to run Gnome 3. I started the 'install to hard disk' tool, and it died after a minute or two. Not enough memory, some other problem? I've no idea.
I was beginning to run out of ideas and then I thought of Mandriva and tried to install Mandriva 2010. That went well until I tried to boot and the Mandriva grub 1.0 install clashed with the grub 2.0 install of Kubuntu that I had on the second partition in my netbook. The naming scheme for partitions has changed between grub 1.0 and grub 2.0 and it isn't a good idea to combine them.
Large parts of my weekend were beginning to disappear even though it should be simple for an expert user to set up a netbook. Then I found out that Mandriva 2011 uses grub 2.0 and installing that worked great.
Back to bird collective nouns - I clearly had a 'flight of Mandrivas' here. I like the changes that Mandriva have made to the KDE UI. They have their own custom Plasma panel. It is black and doesn't look horrible like the default grey Plasma panel does. It doesn't have multiple virtual desktops by default. I thought I should just try the default UI at the Desktop Summit and see how I got on with it.
I wonder what has gone wrong with KDE Usuability considering we have a usuability expert on the KDE eV board. I find trivial usuabiltiy problems with KDE really annoying. For instance, if I set up KDE Wallet why do I have to give it a different password once I have logged in? Why doesn't it trust me?
If I try and make my laptop suspend while it is still connected to the mains power by shutting the lid, why doesn't it just suspend? I have to disconnect the power cable and then shut the lid again. Then plug the mains cable back in to ensure the laptop doesn't run out of power. Why do I get a completely useless notification about 'your laptop has had its power removed'? Of course I know that because I just removed the power cord to get round the problem of the laptop not suspending properly.
When my laptop wakes up it asks me for a password before it unlocks the screen. Why does it lock my screen by default? I don't know. I used to work on real time trading systems at a bank, and there was certainly a policy there of using screen lockers. But banks must be about 1% of KDE's users and so I have no idea why locking the screen is something a non-expert user should be confronted with. I haven't worked out how to disable screen locking even though it is a complete pain in the arse.
I have no idea why the KDE menus still have underlines in them to allow you to navigate without a mouse. That made sense when mice were rare things in the early eighties and power users without mice could navigate through Windows 1.0, but now about 1% of people use that option why are the other 99% being exposed to such an ugly UI.
I'm looking forward to the Berlin Conference and I hope we can make it an opportuntity to sort out KDE's 1980s and 1990's UI problems like I've just described. Clearly Plasma Active is in advance of everything else in my opinion, but the normal widget based normal KDE UI isn't. I still think we can do better than Mac OS X Lion and I look forward to hearing the opinions of KDE UI experts at the conference.
Some valid questions.
Some valid questions. I have probably at least some ideas...
if I set up KDE Wallet why do I have to give it a different password once I have logged in?
Guess noone did implement pam-support / single-sign-on in KWallet yet. You can just leave the password empty and press all those ugly warnings away to earn a similar result (except your passwords are not protected any longer against harddisc-thefts / multiuser-spies).
If I try and make my laptop suspend while it is still connected to the mains power by shutting the lid, why doesn't it just suspend?
Here it does but that's probably distributor-dependent?
Why do I get a completely useless notification about 'your laptop has had its power removed'?
At least there is a trend away from those modal message-box's. But yes, the notification-flood is annoying too.
I haven't worked out how to disable screen locking even though it is a complete pain in the arse.
Open Systemsettings (now named "Personal Settings"), choose "Power Management" and there it says "Lock screen on resume" which is enabled per default but can be disabled.
I have no idea why the KDE menus still have underlines in them to allow you to navigate without a mouse.
Isn't that style-specific? If yes, then a patch for oxygen would be an idea maybe? At least I don't see a reason too why it's enabled per default.
Re: Some valid questions.
I have been using Kubuntu on my laptop and maybe the 'suspend when mains powered' behaviour is specific to that distribution. Or I thought maybe it is something to do with the bios on my HP 2133 - I don't know enough about how it all works.
My next laptop will probably be an Apple Air, and I will run Linux under Mac OS X via Vmware or Virtual Box, and that way it will have the standard Apple suspend behaviour. It will also be able connect to WiFi without needing to go through KWallet. And I won't have to mess with b43-fwcutter or build Broadcom wl drivers that crash the system like I do with my HP 2133.
I will take a note of where I can disable screen locking. I thought I had looked under 'power settings' already. Although I don't really see why locking the screen has much to do with power settings. I would associate screen locking with security features and include it with things like whether or not you want a kdm user/password dialog to login or not. Or maybe in with screen saver options, but power management doesn't seem right.
I'm not sure if the menu underlines can be fixed entirely with a style change if you wanted the Microsoft behaviour, which is to only show them when you hold the alt key down. I have no particular objection to that behaviour, but for me it would be fine if I could just turn them off altogether. I think it needs to be fixed in the Qt libs themselves, but it doesn't appear to bother anyone much but me.
Re: Some valid questions.
I tried closing the lib of my laptop with Mandriva and all went well, the laptop just went to sleep as you would want.
Things didn't go so well when I opened the laptop lid. I got all manner of useless random notification messages telling me that I had just opened the lid of my laptop. It prompted me for a screen lock password and then went to sleep again, combined with some more notification message mayhem. I looked at the 'Configure Notifications - System Settings' dialog and it does appear to be possible to configure the mains cable plugged in off/on notifications to be more user friendly - ie remove that pointless stuff altogether.
Who can I talk to me at the Berlin Desktop Summit about making the decision to make screen locking the default option in KDE, along with putting it in the wrong place in the system settings?
I'm not sure if the menu
I'm not sure if the menu underlines can be fixed entirely with a style change if you wanted the Microsoft behaviour, which is to only show them when you hold the alt key down.
I think some styles do it already like that. iirc the Sculpture QStyle does exactly that.