It was my third day after I’ve switched to Fedora. After all the initial installation/configuration and KDE 3.2 upgrade, I decided to enable the multiple sessions support, because that’s one of the core features, needed to replace one Windows XP installation I’m shame about!
However, first I visited the FedoraNews site (recommended by Yovko), and I found there an article about how to get the Start New Session option to work under KDE 3.2. I did all what was mentioned in that article and… hmmm… it won’t show (the Start New Session menu item).
I red the article again. At the bottom the guy was talking that he’s not sure if this hack would work on display manager, different than KDM.
I briefly checked mine – it was gdm (logically, this is the default display manager for Fedora). So, I had another task to finish – how to change the default display manager.
After consulting with Yovko again, he suggested taking a look at the /etc/X11/prefdm. It was a script, which was calling /etc/sysconfig/desktop script, and expecting the $DISPLAYMANAGER variable to be set correctly.
First I made the wrong assumption and I onyl changed the $DESKTOP variable to “KDE”. Nope – nothing happen. After that I added the following line:
DISPLAYMANAGER=”KDE”
And all went fine.
I still have my DESKTOP variable set to “KDE”, and I’m not sure if it will work if you leave it to be “GNOME”. You are free to try it as you want.
So, I had my installation working in two easy steps: applying the patch and adding the DISPLAYMANAGER line.
If you decide to follow my advice here, please have in mind that:

1. I do not give any guarantee that this article is usable at all. You take any risk for doing any kind of damage to your computer
2. I assume that you always make backups of all the files, which you have to modify. When I speak “changind”, “adding” or whatever else, I always presume you did backup of the file you modify, in case that something goes wrong
3. Any of the mentioned steps require restart of the currently running display manager. The best is to do all the steps in runlevel 3! After each step you have to do “init 3” and after that “init 5” as root, in order changes to get applied.

I wish you success!

Yesterday one of my friends, Georgi Chorbadzhiyski has paid attention to my new blog RSS feeds, and has informed me that they suck. Especially the cyrillic support there.
Because WordPress is initially lacks cyrillic support (see my article about how I did it working with help of the community), it seems I either forgot, either there it was initially missing, to tune up the RSS feeds.
So, I had to dig the sources. And I digged out the following problem: WordPress RSS feeds output no encoding tag. So the browsers assume what they want, and mine was assuming UTF-8. I had to add the encoding tag to the WordPress RSS source.
If you have the same problem, this is your solution (it’s divided on two):

1. Modify wp-rss.php, located in your main blog dir. Put the following text:

    encoding="windows-1251"

   immediately after the following text:

   <?xml version="1.0"

   Please note that between the text above and the encoding word you must put one space.

2. Modify wp-rss2.php, located in your main blog dir. Put the following text:

    encoding="windows-1251"

   immediately after the following text:

   <?xml version="1.0"

   Please note that between the text above and the encoding word you must put one space.

3. Modify wp-commentsrss2.php, located in your main blog dir. Put the following text:

    encoding="windows-1251"

   immediately after the following text:

   <?xml version="1.0"

   Please note that between the text above and the encoding word you must put one space.

After the modifications your RSS output should be in windows-1251 encoding, which should solve the cyrillic troubles you may have.