

So you will also need to create /usr/sbin/update-grub with the following contents:
#!/bin/sh
set -e
exec grub-mkconfig -o /boot/grub2/grub.cfg
and set it executable (chmod 0755 /usr/sbin/update-grub) - Mar 20 2012
cd /boot/grub
ln -s ../grub2/grub.cfg grub.cfg
cd /usr/sbin
ln -s grub2-mkconfig grub-mkconfig
The first time you will still be prompted about wrong permissions, but after entering your password it will work. - Mar 20 2012

Plasma 4 Extensions by Emdek 145 comments

Plasma 4 Extensions by Emdek 145 comments
- Cut text (as reported above) -> fixed by adding
m_comboBox->setFixedHeight(30);
in
RunCommandApplet::init()
- I cannot resize it whatever I try (panel settings opened or closed, objects locked or unlocked). The resize cursor appears, but nothing happens. Since by default it takes all the space on the panel, I have put
setPreferredWidth(200);
and it seems to work.
I am under KDE 4.8.0 amd64
Thanks again for this great applet - Feb 01 2012

deKorator Themes by kbios 4 comments
I have seen your work, that's very good, Linux is all about choice.
Alberto - Mar 26 2011
First of all, I think setting grub.cfg to 0400 is useless anyway, since
1) one can simply read the password directly from the scripts in grub.d
2) if you have direct access to the machine, you can easily get the password with a bunch of techniques, it won't be a 400 to stop you (and crypting the disk will be useless in this case, since /boot cannot be crypted).
Second, that's why I added support for sha512 crypted passwords: anyone considering security so important would never use cleartext ones.
Fixperm is designed to avoid to annoy the user with UAC-style messsages, and since you probably won't be running grub-mkconfig manually everyday (probably just when installing a new kernel) I think it does its job.
That said, since kde it's all about giving the user the power to judge and decide, I'm likely going to add an option to disable it in version 1.4 (1.3 is in string freeze now).
Alberto - Mar 26 2011
/usr/share/kde4/apps/kcmgrub2/kcmgrub2.py
/usr/share/kde4/apps/kcmgrub2/kcmgrub2.ui
/usr/share/kde4/services/kcmgrub2.desktop
/usr/lib/kde4/libexec/kcmgrub2helper
/etc/dbus-1/system.d/org.kde.kcontrol.kcmgrub2.conf
/usr/share/dbus-1/system-services/org.kde.kcontrol.kcmgrub2.service
/usr/share/polkit-1/actions/org.kde.kcontrol.kcmgrub2.policy
You might also try reloading dbus. - Feb 22 2011
You're right - not everyone knows what Grub2 is, and I surely agree that from a distribution point of view bootloader configuration would sound better (every distribution has only one bootloader, after all). My concern, though, is from a kde point of view: there is already, for example, a module for Grub Legacy, and renaming mine "bootloader configuration" would probably sound like saying "this is official" or something like that.
However, I don't want to impose my view in any way, so I would like to hear other opinions about this and then decide in time for 1.1 (this Thursday). - Jan 31 2011