egork - Slashdot User

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 file in your autostart directory called xscreensaver.desktop that contains the following five lines:

[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 /usr/bin/ (or possibly /usr/kde/3.5/bin/ or /usr/lib/kde4/libexec/) with these two lines:

#!/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.

Journal Journal: Use Logitech DiNovo Edge dongle as a generic Bluetooth

Journal by egork on Sunday March 22, 2009 @02:48PM

link

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!

Journal Journal: show ssl in the address bar

Journal by egork on Saturday March 14, 2009 @10:48AM

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/

Journal Journal: remap caps lock to toggle (switch) keyboard layout

Journal by egork on Wednesday November 19, 2008 @11:26PM

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.

Journal Journal: make iPod ejectable

Journal by egork on Monday May 26, 2008 @02:05AM

mount iPod and then say:
sudo chown egork /dev/sdc2
sudo chmod u+s `which eject`

Journal Journal: "Linux compartible" initiative, can community help vendors? 1

Journal by egork on Thursday May 22, 2008 @12:19PM

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?