Known bugs and fixes for Easy Peasy 1.1

From EasyPeasy Wiki

Jump to: navigation, search

Contents

Mute and Volume Up/Down keys don't work properly

Solution: change how eeepc-config processes them.

  1. sudo gedit /etc/default/eeepc-config
  2. Comment out the volume stuff by editting lines 50-52 from: 
EEEPC_HOTKEY_MUTE_TOGGLE="acpi_fakekey $KEY_MUTE"
EEEPC_HOTKEY_VOLUME_DOWN="acpi_fakekey $KEY_VOLUMEDOWN"
EEEPC_HOTKEY_VOLUME_UP="acpi_fakekey $KEY_VOLUMEUP"

to 

#EEEPC_HOTKEY_MUTE_TOGGLE="acpi_fakekey $KEY_MUTE"
#EEEPC_HOTKEY_VOLUME_DOWN="acpi_fakekey $KEY_VOLUMEDOWN"
#EEEPC_HOTKEY_VOLUME_UP="acpi_fakekey $KEY_VOLUMEUP"
  1. sudo /etc/init.d/eeepc-config restart

Skype audio doesn't work

Solution: change Skype hardware options

Open Skype, go to options, Sound Devices. Change all settings to HDA Intel (hw:intel,0). Untick "allow Skype to manage mixer levels".

Audio levels too low, and/or muting results in crackling noises

Solution for 901: Tweak the audio settings

Method:

  1. Go to Preferences > Sound.

In order, make the boxes say this: 

Autodetect
Autodetect
Autodetect
HDA Intel ALC269 Analog (ALSA)
Playback: ALSA PCM on front 0 (ALC269 Analog) via DMA (PulseAudio Mixer)
Make sure "Master" in the box below is highlighted.

Right-click the volume icon on the Panel, select Open Volume Control In Device, select HDA Intel (ALSA Mixer)

Make sure the sliders for PCM and LineOut are at maximum.

In Device, select Playback: ALSA PCM on front 0 (ALC269 Analog) via DMA (PulseAudio Mixer)

The Master slider should also be at maximum.

From my experiments, top volume should now be very loud, and the volume keys and mute should all work (providing the earlier fix above was applied) and mute doesn't crackle, and everything is lovely.

Fn + F2 doesn't enable wireless

Solution: Since it seems rfkill doesn't do it's job, work around it. Save the following to a file - say eeepc-wifi-toggle.patch: 

34a35
> WLAN_PROC="/sys/class/rfkill/rfkill0/state"
41,43c42,44
< if isKernelLaterThan "2.6.27"; then
< 	exit 0;
< fi
---
> #if isKernelLaterThan "2.6.27"; then
> #	exit 0;
> #fi

and run: 

patch /etc/acpi/eeepc-wifi-toggle.sh < eeepc-wifi-toggle.patch

This will use the rfkill-state file. And run the script with that. Instead of exiting because of the newer kernel.

Network manager prompts for keyring at login

This fix will clear your default application keyring password:

(don't use this fix if you want your wireless passwords and other application passwords secured)

  1. Install seahorse to manage your keyrings: sudo apt-get install seahorse
  2. Clear the password of the default keyring used by applications:
    1. start seahorse (not as root)
    2. Edit -> Preferences
    3. In the 'Password and encryption Settings' popup window, Look below and see which 'Location for application passwords' / 'Default Keyring' is selected.
    4. In the 'Password Keyrings' section, select this 'Default Keyring'
    5. click the 'Change Unlock Password' button. In the 'Old password' field enter your login password, in the second 'Password' field just press enter.
    6. Accept the warning pop-up about this keyring being insecure.
    7. Press Change button and close seahorse
  3. Reboot to check if network manager connects without asking your password.


More information on this subject can be found here: Automatically Unlocking the Default Gnome-Keyring : PAM Keyring


The following hack will not clear your default application keyring password, but it may not keep your wirless passwords secured either. You may get asked for a keyring for some other application later, but it's likely you'd rather keep your guests and users away from those things anyway. It should however keep the rest of your keyring stuff secure. Simply check the option "Available to all users" in the Network Connections Manager.

  1. Right-click the wireless applet in the task bar
  2. Select Edit Connections...
  3. Edit your wireless connection
  4. Check "Available to all users"
  5. You may want to show and re-enter your network passwords. I did, but I'm not sure it was necessary.

Source: : Ubuntu Forums Post

Retrieved from "http://wiki.geteasypeasy.com/Known_bugs_and_fixes_for_Easy_Peasy_1.1"