(Note: I forgot who made these originally a long time ago; if these are your images, please send me a note and I'll be happy to attribute them to you!)

regsvr32 %system-root%appatch\slayerui.dll

HKEY_LOCAL_MACHINE\Software\Network Associated\TVD\Virusscan Enterprise\CurrentVersion

Entferne die Zeichen vom UIP Sting Key und trage im UIPMode Dword Key eine 0 (Null) ein.

...und schon is' alles offen ;-)

El siguiente, es un extracto de la información sobre que contendrá GNOME 2.22 cuya fuente es la nota de lanzamiento en su versión en español.

Novedades para los usuarios

El proyecto GNOME se centra en los usuarios y la usabilidad, y continúa en GNOME 2.22 con cientos de arreglos y mejoras pedidas por los usuarios. Pero este impresionante número de mejoras hacen imposible listar cada cambio que se ha realizado pero esperamos resaltar algunas de las características orientadas al usuario más excitantes de este lanzamiento de GNOME.
El programa Cheese.

GNOME 2.22 cuenta con una nueva aplicación Cheese. Cheese permite tomar fotos y hacer vídeos usando la cámara web del equipo usando diferentes efectos: como malva, negro/blanco, psicodélico y distorsión.Fotos y vídeos que puede compartir con sus amigos y guardar en F-Spot o definirlos como la foto de su cuenta de usuario.

Composición de ventanas

GNOME 2.22 introduce la composición de ventanas en plataformas que sean capaces de proporcionarla. Siguiendo con la política de GNOME de «mantenerlo simple», las características tienen una baja prioridad. Los cambios más notables son las sombras arrojadas sobre las ventanas, Previsualizaciones vivas al cambiar de ventanas con Alt+Tab y efectos de transparencias.

No todo hardware gráfico es capaz de soportar la composición, así que ésta característica está desactivada de forma predeterminada y aún no se muestra en las preferencias. Si sabe que su hardware gráfico es capaz de soportar la composición, puede ejecutar el siguiente comando: gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true desde el dialogo ejecutar, o establecer la clave en el Editor de configuración. Para desactivar la composición, establezca la clave a false.

Mejores Sistemas de archivos de red

GNOME 2.22 presenta GVFS una nueva capa de sistemas de archivos virtuales para GTK+. GVFS está diseñada para superar las deficiencias de la versión precedente del sistema GNOME-VFS. Las mejoras sobre GNOME-VFS incluyen recordar las credenciales de entrada durante toda la sesión y ser más resistente a los fallos. Muchas de las aplicaciones de GNOME ya están usando GVFS incluyendo todas las aplicaciones del núcleo.

Con el cambio a GVFS, GNOME usará la especificación de Freedesktop.org sobre la Papelera, que define el almacenamiento de archivos eliminados.

También hay disponibles algunos protocolos nuevos. cdda:// mostrará todas las pistas de audio en un CD, disponibles como archivos WAV. gphoto2:// le proporcionará acceso a cualquier cámara digital conectada.

Ahora el Gestor de archivos de GNOME ahora es mas inteligente sobre los soportes y le mostrará una barra de información con las posibles acciones cuando introduzca un soporte extraíble o examine una carpeta en una unidad extraíble.

Hay disponible información técnica acerca de GVFS en la GVFS y GIO, bajo Novedades para los desarrolladores.

DVD, TV digital y más

El Reproductor de películas de GNOME ahora ofrece soporte mejorado para la reproducción de DVD así como soporta para televisión digital (DVB). En 2.22 también se aprecia una selección de nuevos complementos, incluyendo soporte para MythTV, Youtube y búsqueda usando Tracker. También se pueden compartir listas de reproducción y seleccionar los subtítulos para los archivos.

GNOME 2.22 incorpora la capacidad de previsualizar y reproducir contenido Flash y video usando el decodificador de Flash libre y abierto swfdec.

Reloj internacional

No hay necesidad de hacer más cálculos mentales para saber a qué hora comienza su teleconferencia en Buenos Aires. GNOME 2.22 ahora tiene internacionalización integrada en su reloj. Puede añadir multiples ubicaciones de todo el mundo para ver la hora local y el clima.

Reloj internacional.

Evolución continua

Evolution mejora cualitativamente gracias al soporte de Google Calendars y de la personalización de las etiquetas de mensajes para los correos electrónicos.

Evolution mostrando un calendario de Google.

Se ha trabajado también en mejorar la velocidad del filtro de SPAM y hacer los diálogos de error menos s en su sesion de escritorio usando la barra de estado en lugar de mensajes emergentes.

Escritorios remotos

En GNOME 2.22 el Visor de escritorios remotos es nuevo. Esta aplicación complementa al soporte existente de servidor de escritorio remoto en GNOME. Puede descubrir máquinas en la red local y marcar sus favoritas.

Visor de escritorios remotos interactuando con el escritorio actual.

Los usuarios que deseen más control sobre el servidor de escritorio remoto apreciarán la inclusión de una solapa Avanzada en el diálogo de propiedades.

Ajustes de teclado simplificados

Las preferencias de la distribución del teclado y la accesibilidad se han unido en un sólo dialogo, metiendo todos los ajustes del teclado que necesita en un sólo sitio. Las Combinaciones de teclas del escritorio se mantienen separadas.

El nuevo diálogo de Preferencias del teclado.

Pero eso no es todo...

GNOME 2.22 también cuenta con muchas correcciones de errores e implementación de mejoras requeridas por los usuarios desarrolladas en los últimos seis meses, incluyendo:

The Fix

The error message was this: "could not load font 'fixed'"

It was a fatal error and it gave up. X just wouldn't start! I checked out my font aliases and everything and it was all clear. I tried installing a BUNCH of packages, but that didn't help, either. So I just got rid of them all again. Then, I uninstalled and reinstalled font-misc-misc. Then I ran the command fc-cache -fv. Then startx. And guess what? It just works.

The End

Ya know, since this was such a short post, I was tempted to leave off my now-obligatory "The End."

Today, in our Linux Page (in Spanish) we have posted a review about the new version (4.2.5) of Damn Small Linux. Damn Small Linux is one of our favourite distribution due to its capability to run on very old PC as 386/486/Pentium with very few hardware resources. This version has updated some features as Monkey Webserver 0.9.2 and is incredibly stable (as the previous ones, I must say). According to distrowatch.com, in the last 12 months Damn Small Linux has been the 10th most downloaded (and consequently used) Linux version also because, with no costs, many people are converting old Windows based machines to new up-to-date computers. Anyway, Damn Small Linux is based on Knoppix but is smaller and contains many improvements. Last but not least, I would like to focus your attention on the five different subversions available:

I was doing a few random searches with aptitude this evening a stumbled upon WindowMaker again and just couldn't resist the temptation to play around with it again. So I aptitude installed it, edited ~/.xinitrc and fired it up with a startx.

The initial nostalgia shock was almost too much. Here was a window manager that I had stared at almost 24/7 for at least 2-3 years. I grabbed the Extras tarball so that I could get it to exactly the way I used to have it running.

For a while I was contemplating going back to WindowMaker. Sadly, I don't think that will happen. Over the years I've just grown too accustomed to fluxbox (which is another great window manager, btw). I've handcrafted my fluxbox menu and I've built up keybindings for all the things I need. I launch rxvt with ALT+T, irssi with ALT+i etc. In short, I hardly ever have to grab for the mouse. Setting all that up in WindowMaker again feels like too much work.

But it sure was fun. And WindowMaker feels so snappy, it's amazing. Fluxbox feels old and slow by comparison. If you have some real old hardware with limited RAM and a video card from a previous era, give Window Maker a try. It will not disapoint you. And using WindowMaker for a while did inspire me to make a few changes to my fluxbox set-up.

First of all, my favorite WindowManager theme was Night, which comes on the Extras tarball. I especially liked the wallpaper because it is dark and simple. It also has a calming effect on me. I also decided to get a few dockapps again. Seems the dockapps warehouse is gone, but there are some other sites. Also Debian packages some of them. I was able to get some of the ones I used to run in the WindowMaker dock.

Screenshot follows:

Fluxbox with a few dockapps. Style is mussel. One rxvt window, busy scrotting this screenshot. Here's a closer look at the slit:

The following dockapps are running here, all available in Debian:

• wmmoonclock: shows the moon phase
• wmcalclock: date and time
• wmnd: monitors network interfaces
• wmtop: top three processes
• wmfire: shows CPU load

I would have liked to have wmscope there as well. It does exist in Debian, but when I launched it, CPU usage show right up. Also, it didn't really seem to work right. A little bit of quick research revealed that it doesn't seem to work with ALSA, only OSS, which of course was *the* sound system for Linux back in those days.

I also used to have a dockapp for mail notification (I think it was wmymail or something like that). Now that I'm on a bunch of mailing lists and recieving new mails almost constantly I'm not sure if a biff for the slit makes all that much sense.

Well, it was fun and my "new" fluxbox look will serve as a reminder of WindowMaker, the totally great window manager that I wish I had the patience to get used to again..

I'm not sure if these instructions apply to Gnome or KDE. Most likely, Japanese and Chinese are not user-friendly enough for Gnome, and KDE offers you a GUI tool to configure your input methods that is so complex you need a triple-degree in nuclear physics to figure it out. The following should work on a normal X window manager, which is the preferred way of using Linux for normal people.

Install SCIM and related packages

The best thing to do first is aptitude search scim. You will at least need scim itself. For Japanese I use anthy, and for Chinese I use scim-chinese and scim-chewing. I also have a few other packages, like scim-gtk2-immodule and scim-qtimm (you might need to grab that one from the Sid repos) installed.

Adapt the following to your own requirements. Note that there are several other input methods available with SCIM as well, such as Korean. Unfortunately, I don't know Korean (yet) so it is not something I currently need.

aptitude install scim scim-anthy scim-chinese scim-chewing scim-gtk2-immodule scim-qtimm

Get fonts

You can do aptitude search ttf | grep Japanese to find Japanese fonts. A similar search will give you Chinese. You might also be able to find some others floating around at various places on the 'Net.

Aptitude install the ones you want. You can, and probably should do a bunch of fine-tuning as well, such as organizing your fonts, so that the best fonts get selected. I normally only do such things once I get annoyed enough. That hasn't happened quite yet.

Edit .zshenv

The way it *should* be done, all according to the people who really know, is to set environment variables in /etc/X11/xinit/xinput.d/*. But I'm a non-conformist, and moreover far to lazy to change something that works for me. I stuck the following in ~/.zshenv:

export XMODIFIERS='@im=SCIM'
export GTK_IM_MODULE="scim"
export QT_IM_MODULE="scim"

Of course, I could have added these lines to ~/.xinitrc instead. But these are just environment variables. No harm can come from them being set in ~/.zshenv. I've never had any problems.

At least I added the following to ~/.xinitrc:

scim -d

I put this before exec startfluxbox. There is no need to append a & since the -d will daemonize scim.

Activate scim

Simplest way to do this is to exit your window manager, source ~/.zshenv and restart X.

% . ~/.zshenv
% startx

Success stories

• rxvt-unicode (some people say it doesn't work, don't know why. It works fine for me
• (g)vim, which is what really matters. I use gtk2-vim so it's a gtk2 application.
• opera, although the fonts look ugly (guess I need to play around with that a bit). Opera uses qt3.
• Iceweasel/Firefox, without the fonts looking ugly.
• Netbeans, which proves that it works with Java/Swing as well. Fonts *cough, cough* don't look too good, however..
• gjiten, which is a gtk2 application
• qt4-config. Seems to be the only thing I have available to test that it works with qt4.
• tkremind, which shows that it works with Tcl/Tk as well.

So, SCIM works with the important applications (urxvt, gvim) as well as tk, gtk2, qt3, qt4 and Java/Swing applications. It does not seem to work with fbrun, however (not that it matters at all to me, just had to test it). If everybody had stuck to motif/lesstif I wouldn't have had to test so many applications.

I love fvwm. It really is amazing in many ways. But, it's very easy to end up spending all your time playing around with fvwm manager itself and not getting any time left over for other things. That's what eventually drove me away. In short, fvwm turns into an addiction.

I used Window Maker almost exclusively for a few years. I found it an enjoyable window manager. However, gradually I began using blackbox (which I didn't particularly like at first) more and more. And when fluxbox arrived I began using it and never really looked back.

If I were asked, I would probably not call fluxbox my favorite window manager. Fvwm or possibly Enlightenment would probably fill that spot. But, in half a day, you will have done all the configuration you will ever need to do with fluxbox, and then it just stays out of your way and lets you get on with what you have to do.

I have used the same style (mussel, can't remember where I found it), for at least a few years now. Don't see any reason to change it. I have hand-crafted my menu to contain only the applications I want there. I have keybindings to launch all the important applications (rxvt, mutt, irssi, etc). All in all, my configuration is such that I have to use the mouse relatively little, which makes me happy.

I tried using openbox for a while, but the fact that it uses XML for its configuration files really put me off.

Of course I have also played around a bit with a few of the desktop environments. The only one that seems interesting to me is GNUStep. KDE is, er.. a mess (sorry, but that is my personal opinion), and Gnome is sort of neat in a way but brain-dead (again, personal opinion) at the same time and way too clunky for me to use regularly. I guess Xfce is kind of neat as well, but I've never really taken the time to get to know it well.

Since I spend about 95% of my computer time using a terminal and a text editor (vim), desktop environments really aren't my thing. I rarely use a graphical file manager. If I ever do need one, Rox filer does everything I could ever need.

So, since I use it almost every day, and it rarely annoys me, I've got to give thanks to all the people behind fluxbox.

My ~/.fluxbox/keys file contained the follwing lines, which worked well in the applications that I happen to use most of the time (rxvt-unicode, vim):

Mod4 G :Exec setxkbmap -layout gh -variant ga
Mod4 S :Exec setxkbmap -layout se -variant nodeadkeys
Mod4 U :Exec setxkbmap -layout us


I noticed one thing. If I changed the keymap before launching Opera, the browser would use that keymap. So if, at the time of starting Opera, I was using a Swedish keymap, then I would be able to enter Swedish keys in Opera. But changing the keymap while Opera was running had no effect.

The fix for the problem was simple, after a bit of Googling. I modified ~/.xinitrc to look as follows:

setxkbmap -option grp:switch,grp:shift_toggle,grp_led:scroll us,se,gh -variant ',,ga'
exec startfluxbox


Now the few Qt and Gtk applications that I use behave well! I can switch between US, Swedish and Ga keyboards in all X applications.

Moral: if somethings doesn't work as you like, don't get frustrated, get searching. Somebody has had the problem before, fixed it and documented it.

One other difference - and I'm guessing it's a key difference - this time I unplugged the VGA cable to my external monitor before starting the update process. I did not reconnect my external monitor until after Gutsy Gibbon was fully booted and running.

I followed Mike O'Conner's advice which he left in a comment here earlier. For convenience, here's the link to Intel's instruction - which Mike had reported on.

So:

While still on the laptop screen (and the external still unconnected) I typed:

xrandr -q

and got:

Screen 0: minimum 320 x 200, current 1280 x 800, maximum 1280 x 800
default connected 1280x800+0+0 0mm x 0mm
1280x800 60.0*
1280x768 60.0
1024x768 60.0
848x480 60.0
800x600 60.0
720x576 60.0
etc...

Notice - no information about any other moniter. xrandr thinks the only monitor is called "default".

I then reconnected the second monitor and restarted X (ctrl+alt+backspace).

After the reboot, I immediately saw my second desktop - all correctly positioned with the correct resolution. But typing xrandr -q at the prompt on the laptop screen still gave me exactly the same information.

I then typed xrandr -q at a prompt on the external monitor's instance of X and got a different set of data - this time, with no information about the first monitor's configurations. The bad thing - xrandr is reporting that the external monitor is also known as "default". This will keep me from following the intell instructions - since it seems that xrandr needs to distinguish the two (common sense) but the X Window's way seems to be to have completly independent instances running simultaneously.

The only kink in that logic that I can see is that, even though X Windows doesn't allow me to drag windows or applications from one monitor to the next - I can drag icons from one to the other. ...interesting. that has to be a clue - - but I'm not sure to what.

the up side:

The up side is that I really don't care right now. I've finally gotten to upgrade to Gutsy and my monitors are working.

dream config:

It's silly that I should have to even suggest this to the Ubuntu team - but I want to be able to drag running application from one monitor to the other.

mouthing off:

This notion of having X Windows running multiple instances doesn't seem to support that - and I'm wondering if that means that the errors and troubles that so many Ubuntu users have been having with setting up a dual head configuration could be due to a bad design that simply needs to be scrapped and redesigned.

thanks for all who've commented and offered suggestions, links, and assistance!

The solution is XLiveCD: http://xlivecd.indiana.edu/

This is a CD that just makes your Windows PC into a X-Windows client (Correct terminology would be Server... ;) ). With this you can just start a ssh session into your remote Unix/Linux box, and from there just run any graphical application that you need. The application will display along your other Windows applications.

By the way if you have Nero Image or something similar, you even don't need to burn a CD...

Also as a bonus the CD has a complete CYGWin set of commands, and so you also get tail, grep, uniq...

Needless to say, that was needless.

Sometime later I was able to do the same thing with popular freeware software. The key software here is Cygwin ( http://cygwin.com ), which most folks should know as a "Linux-like environment for Windows" (their words). The install is clunky, but whaddaya want for nuttin'? I liked it because it was free and the Cygwin modules I needed did not need admin rights for PC install (as admin rights are disabled to the masses per our company's security policy). You need to make sure that you explicitly download the X11 module with all the defaults.

Although not needed, I'd recommend using the telnet/ssh client of your choice. I like PuTTY ( http://www.chiark.greenend.org.uk/~sgtatham/putty/ ). Again, it's great because it's free and the install ... well, there is no install. You download one file, an .exe. and you put it somewhere. Preferably where you can remember it. It's not needed because you can work within the ssh client that comes with Cygwin, but PuTTY's client is more feature rich (with luxuries like copying/pasting without a lot of pain).

To start an X Server on your machine, you need to open up a Cygwin shell (the install should create a shortcut to open a shell), cd /usr/X11R6/bin, and execute startx. This will start the X server. For sanity, I usually create a small batch script in my Cygwin $HOME to do the above.

From this point forward, the steps to implement and test are harder to cast in stone, since we start to hit variables that will differ from shop to shop (X11 forwarding, firewalls, OS builds, etc). I can only discuss what works for me. Take it as supplemental knowledge, and google cygwin xwindows putty for some other shop's setup instructions. Henceforth, my use of second person pronouns and will be replaced by first person and nominative possessive pronouns.

Once X Server is up, an XWindows console comes up. I execute "xhost myremote.machine.com" to allow XWindows connections from my remote machine to my local machine.

I PuTTY (via ssh) into my remote machine, and set a DISPLAY environment variable to my IP address appeneded with ":0.0", which I believe is the main display address for the X server locally (in case of multiple desktop displays, I guess). I make sure I have my PATH environment variable pointing to the XWindows libraries (for me: /usr/openwin/bin).

The moment of truth: Enter xclock. If a little clock widget displays on my machine, then I set it up correctly.

Hope some of this is of help. Enjoy!

Learning to be patient,
Walt Silva

I went into a console using "control-alt-F4":

and I set the display for applications using

declare -x DISPLAY=":0"

so that X applications would go onto the X screen, which can be returned to by control-alt-F7. Then I started Inkscape on the console:

as can be seen here:

It worked OK because when Inkscape froze the X window system, I was able to go back into the console and look at what was happening.

#!/usr/bin/perl
use warnings;
use strict;
my $files = join (" ", @ARGV);
if ($files eq "") {
    die "No files specified.\n";
}
if (!fork) {
    exec ("wmctrl -a emacs");
} else {
    exec ("/usr/bin/emacsclient --no-wait $files --alternate-editor /usr/bin/emacs");
}

If Emacs is not running, it starts it. If Emacs is running, it uses the emacsclient program to start a new client process. You also need the following in a file called ".emacs" in your home directory:

; Start the server which responds to "emacsclient":

( server-start )

The other thing this does is to raise the X window containing Emacs. It's necessary because the usual way of raising the frame, adding

;; make the server raise the Emacs window
(setq server-raise-frame t)

to your .emacs file, doesn't work with Ubuntu's default window manager. You need to have the "wmctrl" package installed. On Ubuntu, use

sudo apt-get install wmctrl

to install this.

What will you do when you leave your X Window desktop on a Linux box?
obviously, lock it to protect your precious data. But this is not a full protection yet, why? because one can still press <Ctrl> + <Alt> + BackSpace key to kill your entire session. If you have any unsaved documents they all are gone.

The Solution

Open /etc/X11/xorg.conf file in your favorite text editor and look for
Section "ServerFlags" line. If one already exists add the following line between start and end of that section.

    Option "DontZap"      "true"

If the section does not exists at all, append the following lines to your xorg.conf file

Section "ServerFlags"
    Option "DontZap"      "true"
EndSection

Note

You can also add the following option to disable switching to full text mode (VT).

    Option "DontVTSwitch" "true"

BE WARNED! this will disable both killing your X session forcefully and switching to text mode. If some application got hung and your X session is not responding you will have to restart your machine.

http://www.apsivam.in/tips/linux/secure_your_x_window_system

I was never able to make that work in my computer, and I ended up getting used to the clumsy "AltRight+," key combination that produces it.

Just today, Paulo sent me the recipe to get it working :-). You just have to go into the /etc/gtk-2.0 and edit the file gtk.immodules. In that file you are going to find a line like this:

"cedilla" "Cedilla" "gtk+" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa"

In the last string there, append ':en' into it, making it look like:

"cedilla" "Cedilla" "gtk+" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en"

Save the file, restart X, and you're good.

via http://jaortega.wordpress.com/2007/04/11/erlang-now/

and now for something completely different:

g( . )( . )gle is watching you...

Pode-se inclusive rodar um servidor X-Windows, e rodar programas gráficos do Linux aqui, exportar display, pacote completo :-).

No entanto, o X não é instalado por default pelo Cygwin, você precisa selecionar alguns pacotes, na categoria X11. Eu recomendo (pelo menos) o seguinte conjunto:

• X-start-menu-icons
• X-startup-scripts
• cygwin-x-doc
• xorg-x11-man-pages
• xorg-x11-xwin
• xterm
• xwinwm

Ao escolher esses pacotes vários outros serão automaticamente escolhidos também para satisfazer dependências. Clique em Next e instale.

Para fazer o servidor X rodar automaticamente ao dar login no seu Janelows, faça o seguinte:

1. Abra o diretório
   "C:\Documents and Settings\<seu usuário>\Start Menu\Programs\Startup"
2. Crie um novo Atalho (exatamente como está escrito abaixo):
   Target: C:\cygwin\bin\run.exe -p /usr/X11R6/bin X -multiwindow -clipboard
   Start in: C:\cygwin\bin

Para testar, já mande executar na hora, verifique que o ícone do X aparece na barra do Windoze. Para ter certeza, dê um logoff e um logon e verifique que o servidor X e iniciado ao você entrar na sessão.