Various problmes on a new installation

To activate the volume controls on the keyboard, I had to open
~/.config/openbox/trisquel-mini-rc.xml
look for
  </keyboard>

and add the following above that line:
    <keybind key="XF86AudioMute">
      <action name="Execute">
        <command>~/.local/share/volume.sh toggle</command>
      </action>
    </keybind>
    <keybind key="XF86AudioRaiseVolume">
      <action name="Execute">
        <command>~/.local/share/volume.sh up 5%</command>
      </action>
    </keybind>
    <keybind key="XF86AudioLowerVolume">
      <action name="Execute">
        <command>~/.local/share/volume.sh down 5%</command>
      </action>
    </keybind>

then, create a file named ~/.local/share/volume.sh:
touch ~/.local/share/volume.sh
chmod +x ~/.local/share/volume.sh

open the file and put the following:
#!/bin/bash

# Check that amixer exists or exit
[[ -z `which amixer` ]] && exit 1

case "$1" in
[uU] | [uU][pP])
echo "Volume up by $2";
amixer set Master "$2"+;
;;
[dD] | [dD][oO][wW][nN])
echo "Volume up by $2";
amixer set Master "$2"-;
;;
[mM] | [mM][uU][tT][eE])
echo "Muting";
amixer set Master mute;
;;
[uU][nN] | [uU][nN][mM][uU][tT][eE])
echo "Unmuting all";
for i in {Master,Headphone,PCM,Speaker}; do
amixer set "$i" unmute;
done;
;;
[tT] | [tT][oO][gG][gG][lL][eE])
echo "Toggling all according to Master";
# Get the status of the Master control
M=$(amixer get Master | grep 'dB.*\[o' | awk '{print $NF}' | tr -d '[]');
for i in {Master,Headphone,PCM,Speaker}; do
# If the master is on, mute it (set on)
if [[ $M == "on" ]]; then
amixer set "$i" mute;
# If the master is off, unmute it (set off)
elif [[ $M == "off" ]]; then
amixer set "$i" unmute;
fi;
done;
;;
esac

then run openbox --reconfigure

and I would like to see these changes in the next release of Trisquel!_* please.

Hi Matsetes,

Try installing gnome-tweak-tool

# apt-get install gnome-tweak-tool

That will allow you to modify Gnome 3's desktop settings including desktop icons.

For the tackpad I'm not sure but you may want to check the Ubuntu Forums and see if someone had a similar problem for the same laptop.

Did you try installing any of these packages already?

gpointing-device-settings - configuration tool for pointing devices
gsynaptics - configuration tool for pointing devices (transitional package)
tpconfig - touchpad device configuration utility
xserver-xorg-input-synaptics - Synaptics TouchPad driver for X.Org server
xserver-xorg-input-synaptics-dev - Synaptics TouchPad driver for X.Org server (d

>I wonder why with gconf-editor this did not run... I hear they've moved some settings away from gconf. Quite a lot ot stuff changes between versions. It's a blessing and a curse.

>And for the automatic change of brightness?

The laptop mode tools could be the answer if you can change brightness in software. Let's see:

What's the output (if any) of ls /sys/class/backlight/

(blue means it's a folder)

In the intel_backlight folder there is a file named brightness. cat its value and then change the brightness and cat again. Does this number change? Try changing the number.

sudo sh -c "echo X > /path/to/file" where X is some number

Does the brightness change when you change the number?

Congrats! So, now you should install the laptop-mode-tools package as suggested by GustavoCM and configure it.

man laptop-mode.conf

Read the manual page, there's a section about brightness. I've never used it but it would seem to be able to control brightness on AC and battery.

man laptop-mode.conf

I would expect them to mean

BATT_BRIGHTNESS_COMMAND whenever you're on battery
LM_AC_BRIGHTNESS_COMMAND on ac and laptop mode
NOLM_AC_BRIGHTNESS_COMMAND on ac and no laptop mode

the value is the number that controls the brightness

BRIGHTNESS_OUTPUT is /sys/class/backlight/intel_backlight/brightness

So, the brightness will still change but you can control to what it changes. On my laptop I cannot change brightness in software at all. The hardware remembers 2 values for brightness, one for ac and one for battery... You might want to check if there is some setting in BIOS, probably not.

And if you really want to go overboard, you could write a silly little script that would copy the current value of brightness somewhere every minute or so and then would set the new brightness to that whenever there is ac/battery change. Of course any brightness changes within the last minute would be lost. There wouldn't happen to be such a file already, like previous_brightness in the folder? :)

Or then you could try to see if you can catch the change when it happens by putting a very early and a very late script to power.d to see if they see different values, then you wouldn't need such a silly polling script and wouldn't have such a bad 1 minute retention. Donät expect this to work though but could be worth trying.