I must admit it's quite embarrasing, but now it works... I changed XSESSION to "kde-3.4" and now it works, not only kde but also enlightenment.... I can't realize why it has made it to work, but the fact it's the only thing I've touched...
Thanks everybody On 6/6/05, Juan Ignacio Sánchez Lara <[EMAIL PROTECTED]> wrote: > > Several questions: > > > > Are you selecting a specific WM from the drop-down menu, or are you just > > using "Default"? I am not certain that Entrance has/uses a "Default" > > setting, wherever it may come from. You'd think from /etc/rc.conf, but > > heck, GDM doesn't use that to set its default (it asks you, so it has > > its own config for this somewhere), so maybe Entrance doesn't either > > (although it never asked me about setting anything as default). > > > > Do you have any other WMs installed and listed, and have you tried > > logging into them instead? Do any of them work, and which ones do not? > I've tried not only default but enlightenment and kde (the WMs I > have). None worked. I've checked that the database entries correspond > with /etc/X11/Session files. > > > > > If Enlightenment itself is the one that doesn't work, did you previously > > have e16 installed? I did, and even though e17 very kindly moved the > > previous enlightenment.desktop item in /etc/X11/Sessions to e16.desktop, > > neither the e16 entry appeared in the list, nor did choosing > > Enlightenment start e17. > e17 is the first Enlightenment release I install. > > > > > This turned out to be because the exec line in the Enlightenment.desktop > > entry was still pointing to /usr/bin/enlightenment, whereas the binary > > for e17 is named something like enlightenment-0.17 (to distinguish it > > from the e16 binary). So I changed the exec line in the script, and then > > it was fine. > > > > However I uninstalled both e16 and e17 (I may reinstall e16, which I > > liked much better), and switched to fvwm anyway. But e17 sure is pretty, > > can't argue with that. > > > > Hope this helps, > > > > Holly > > Thanks for the reply, anyway... > > > > > > > Here's my rc.conf (someone asked for it): > > # /etc/rc.conf: Global startup script configuration settings > # $Header: /home/cvsroot/gentoo-src/rc-scripts/etc/rc.conf,v 1.22 > 2003/10/21 06:09:42 vapier Exp $ > > # Use KEYMAP to specify the default console keymap. There is a complete tree > # of keymaps in /usr/share/keymaps to choose from. This setting is used by > the > # /etc/init.d/keymaps script. > > KEYMAP="es" > > # Should we first load the 'windowkeys' console keymap? Most x86 users will > # say "yes" here. Note that non-x86 users should leave it as "no". > > SET_WINDOWKEYS="yes" > > # The maps to load for extended keyboards. Most users will leave this as is. > > EXTENDED_KEYMAPS= > #EXTENDED_KEYMAPS="backspace keypad" > > # CONSOLEFONT specifies the default font that you'd like Linux to use on the > # console. You can find a good selection of fonts in /usr/share/consolefonts; > # you shouldn't specify the trailing ".psf.gz", just the font name below. > # To use the default console font, comment out the CONSOLEFONT setting below. > # This setting is used by the /etc/init.d/consolefont script (NOTE: if you do > # not want to use it, run "rc-update del consolefont" as root). > > #CONSOLEFONT="default8x16" > CONSOLEFONT="lat9w-16" > > # CONSOLETRANSALTION is the charset map file to use. Leave commented to use > # the default one. Have a look in /usr/share/consoletrans for a selection of > # map files you can use. > > #CONSOLETRANSLATION="8859-1_to_uni" > CONSOLETRANSLATION="8859-15_to_uni" > > # Set CLOCK to "UTC" if your system clock is set to UTC (also known as > # Greenwich Mean Time). If your clock is set to the local time, then set > CLOCK > # to "local". This setting is used by the /etc/init.d/clock script. > > CLOCK="local" > > # Set EDITOR to your preferred editor. > > #EDITOR="/bin/nano" > EDITOR="/usr/bin/vim" > #EDITOR="/usr/bin/emacs" > > # Set PROTOCOLS to the protocols that you plan to use. Gentoo Linux will only > # enable module auto-loading for these protocols, eliminating annoying module > # not found errors. > # > # NOTE: Do NOT uncomment the next lines, but add them to 'PROTOCOLS=...' > line!! > # > # Num Protocol > # 1: Unix > # 2: IPv4 > # 3: Amateur Radio AX.25 > # 4: IPX > # 5: DDP / appletalk > # 6: Amateur Radio NET/ROM > # 9: X.25 > # 10: IPv6 > # 11: ROSE / Amateur Radio X.25 PLP > # 19: Acorn Econet > > # Most users want this: > PROTOCOLS="1 2" > > #For IPv6 support: > #PROTOCOLS="1 2 10" > > # What display manager do you use ? [ xdm | gdm | kdm | entrance ] > DISPLAYMANAGER="kdm" > #DISPLAYMANAGER="entrance" > > # XSESSION is a new variable to control what window manager to start > # default with X if run with xdm, startx or xinit. The default behavior > # is to look in /etc/X11/Sessions/ and run the script in matching the > # value that XSESSION is set to. The support scripts is smart enouth to > # look in all bin directories if it cant find a match in /etc/X11/Sessions/, > # so setting it to "enligtenment" can also work. This is basically used > # as a way for the system admin to configure a default system wide WM, > # allthough it will work if the user export XSESSION in his .bash_profile, > etc. > # > # NOTE: 1) this behaviour is overridden when a ~/.xinitrc exists, and startx > # is called. > # 2) even if a ~/.xsession exist, if XSESSION can be resolved, it will > # be executed rather than ~/.xsession, else KDM breaks ... > # > # Defaults depending on what you install currently include: > # > # Gnome - will start gnome-session > # kde-<version> - will start startkde (ex: kde-3.0.2) > # Xsession - will start a terminal and a few other nice apps > > XSESSION="kde-3.3.2" > > > > > > > > > > > > > -- > > gentoo-user@gentoo.org mailing list > > > > > > > -- > Juan Ignacio Sánchez Lara > Ingeniero Técnico en Informática de Sistemas > -- Juan Ignacio Sánchez Lara Ingeniero Técnico en Informática de Sistemas -- gentoo-user@gentoo.org mailing list
