Journal Journal: Map Logitech V470 buttons to back and forward in Mozilla
add
pointer = 1 2 3 4 5 8 9 6 7
to
mouse has only 7 buttons, but in Xwindows and Mozilla 3.x 8 and 9 are responcible for the back and forward browser history events.
add
pointer = 1 2 3 4 5 8 9 6 7
to
mouse has only 7 buttons, but in Xwindows and Mozilla 3.x 8 and 9 are responcible for the back and forward browser history events.
as root apt-key adv --recv-keys --keyserver keyserver.ubuntu.com YOUR_KEY
I had to tweak the ~/.Xmodemap again. (is accessed by script in ~/.kde/Autorun)
Use this command to get the keycodes from the multimedia keys.
xev | grep -A2 --line-buffered '^KeyRelease' | sed -n '/keycode
/s/^.*keycode \([0-9]*\).* (.*, \(.*\)).*$/\1 \2/p'
my Xmodmap
keycode 121 = XF86AudioMute
keycode 122 = XF86AudioLowerVolume
keycode 123 = XF86AudioRaiseVolume
keycode 142 = XF86Away
keycode 163 = XF86Mail
keycode 165 = XF86AudioPrev
keycode 166 = XF86AudioStop
keycode 171 = XF86AudioNext
keycode 172 = XF86AudioPlay
keycode 217 = XF86Search
Generally to map shortcuts one can use the KDE Settings "Input Actions" and just add new Hotkeys. I have used it for all keys except for Amarok.
Also Qt has explicitly refused to accept
keycode 150 = XF86Sleep
keycode 179 = XF86Tools
that have worked before in 8.04
"Hotkey" Action command
"Decrease Volume" qdbus org.kde.kmix
"Increase Volume" qdbus org.kde.kmix
"Start Dolphin"
Amarok has its own Settings->Configure Global Shortcuts menu.
Just drop all XF86... Shortcuts from "Configure Shortcuts" and put them into "Configure Global Shortcuts"
I have also deinstalled keytouch, keytouch-editor and lineakd, klineakconfig. They basically are responsible for the same thing and may have interferred with the settings, but I am not sure.
change here
HID2HCI_ENABLED=1
to
HID2HCI_ENABLED=0
It prevents resetting the dongle in to bluetooth mode, which does not work for this dongle anyways. This is this reset that disconnects the keyboard.
http://www.diyaudio.com/wiki/index.php?page=LINUX+Audio+MAudioTransit/
use hw:1,0 to configure xine or alsa
sudo blkid
Re: ElectricSheep, can't find xv, another process running, terminated
Hi. The best solution is to remove your current version of electricsheep:
Code:
sudo apt-get remove electricsheep
And then you can use this script and run
Code:
sudo sh install-electricsheep-package.sh
This will install a new version of electric sheep from a PPA on lauchpad.
Credits to spotspot:
http://ubuntuforums.org/showthread.php?t=826554
http://community.electricsheep.org/node/271
http://ubuntuforums.org/showthread.php?t=950771&highlight=electricsheep/
http://www.jwz.org/xscreensaver/man1.html
USING KDE
KDE also has invented their own screen saver framework instead of simply using xscreensaver. To replace the KDE screen saver with xscreensaver, do the following:
1: Turn off KDE's screen saver.
Open the ``Control Center'' and select the ``Appearance & Themes / Screensaver'' page. Un-check ``Start Automatically''.
2: Find your Autostart directory.
Open the ``System Administration -> Paths'' page, and see what your ``Autostart path'' is set to: it will probably be ~/.kde/Autostart/ or something similar.
3: Make xscreensaver be an Autostart program.
Create a
[Desktop Entry]
Exec=xscreensaver
Name=XScreenSaver
Type=Application
X-KDE-StartupNotify=false
4: Make the various "lock session" buttons call xscreensaver.
Replace the file kdesktop_lock or krunner_lock in
#!/bin/sh
xscreensaver-command -lock
Make sure the file is executable (chmod a+x).
Now use xscreensaver normally, controlling it via the usual xscreensaver-demo (1) and xscreensaver-command (1) mechanisms.
Thanks to others who have posted all over the web, including this forum and others, I found out how to fix this, at least on my system.
I did it with Setpoint already installed, but I don't know if this makes a difference.
Disconnect the usb dongle.
Push and hold down the connect button. Put the dongle back in the USB slot while still holding the button for at least 5 sec or so. It will now be recognized as a bluetooth device. I don't know if it's Windows or Setpoint, but new drivers will automatically be installed. The bluetooth icon shows up on the bottom right of the screen, and it's now an option in control panel. I still don't see a bluetooth option within the Setpoint software, though, but Windows can do the rest.
The keyboard now needs to be reconnected to the bluetooth hub. Go to the bluetooth setup screen. Enable discovery in the option tab, and click "add" in the device tab, then follow the wizard. I didn't use a passkey. When connecting, there's a tiny button on the back of the keyboard to press; a green bluetooth logo will flash on the front. It took maybe less than a minute for it to be recognized.
Adding additional bluetooth devices should follow the same steps I think. I'm getting a bluetooth headset to try out. Good luck to us both!
Dazu muss man die Pseudo-URL about:config aufrufen, wovor Firefox allerdings mit einem "Hier endet möglicherweise die Gewährleistung!" warnt. Nach dem eingeforderten Versprechen, vorsichtig zu sein, führt die Eingabe von identity im Suchfeld zur Einstellung browser.identity.ssl_domain_display deren Wert man von 0 auf 1 setzt.
http://www.heise.de/security/Richtig-verschluesseln-mit-Firefox-3--/artikel/132527/
download free software with source code written in c language here http://haali.cs.msu.ru/winutils/
then just drag and drop the exe file to the startup menu and add 20 to the command line (target) in the shortcut properties.
mount iPod and then say:
sudo chown egork
sudo chmod u+s `which eject`
All the hardware I am using works with Linux. None of it comes with "Linux compatible" stamp on it. The information on compatibility has to be looked up on message boards or specialized web sites.
Why the vendors are afraid of confirming the compatibility?
I have heard that vendors do not want to confirm that their hardware works with Linux because they do not see it economical to offer Linux support line. Linux users market is still too small and the OS is too fractured. Well, if the hardware does work with Linux, why not state it and just let users know, that they may not count with customer support yet? This would be a great help for Linux users already.
I can imagine the main problem here is to legally exclude support while stating compatibility. Wouldn't it be a high time for Linux community to set up a framework legalese to lower the barriers for the vendors?
/dev/sdb1
http://picasa.google.com/linux/faq.html#19c
Change the Default Depth in xorg.conf
"Gravitation cannot be held responsible for people falling in love." -- Albert Einstein