public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: (EE) XKB: No components provided for device Virtual  core keyboard
Date: Sun, 21 Mar 2010 20:11:32 +0000	[thread overview]
Message-ID: <201003212011.45803.michaelkintzios@gmail.com> (raw)
In-Reply-To: <ho5jc1$hml$1@dough.gmane.org>

[-- Attachment #1: Type: Text/Plain, Size: 2036 bytes --]

On Sunday 21 March 2010 17:04:28 walt wrote:
> On 03/21/2010 05:33 AM, Leandro Boscariol wrote:
> > Well, I`ve got this:
> >
> > /etc/conf.d/xdm
> > ...
> > DISPLAYMANAGER="kdm"
> > ...
> >
> > /etc/rc.conf
> > ...
> > # Gnome - will start gnome-session
> > # kde-<version> - will start startkde (look in /etc/X11/Sessions/)
> > # Xfce4 - will start a XFCE4 session
> > # Xsession - will start a terminal and a few other nice apps
> > XSESSION="kde-4"
> >
> > Then I remembered about /etc/X11/Sessions and switched it for KDE-4, but
> > still...
> >
> > Also tried commenting the line XSESSION, and nothing again.
> >
> > But, I`m thinking about this note in /etc/rc.conf:
> >
> > # NOTE:  1) this behaviour is overridden when a ~/.xinitrc exists, and
> > startx #           is called.
> >
> > This is the command called when I use startx, right? If so, how can I
> > make xdm use it as well? Or the problem is somewhere else here?
> 
> In the old days, xdm used your ~/.xsession instead of ~/.xinitrc.  I see
>  that /etc/X11/Sessions/Xsession still reads ~/.xsession, but I don't use
>  kde so I don't know what /etc/X11/Sessions/KDE-4 (or kde?) does when you
>  run it.
> 
> Whatever is in that file must do something different than just run
>  startkde, so take a look at it.

/etc/X11/Sessions/KDE-4 just runs:  

exec "/usr/bin/startkde"

and /usr/bin/startkde does not seem to look into either .xinitrc, or 
.xsession, both of which are optional files for personal settings of your 
xsession and its applications.  It does however check to see if XDM is 
running and then it tries to connect to that X server.

In my machine (still on the stable baselayout) if I add XSESSION="kde-4" in 
/etc/rc.conf and DISPLAYMANAGER="kdm" in /etc/conf.d/xdm it works.

Assuming that you have not forgotten to emerge xdm ;-) you may want to try 
using the above settings and then running:

/etc/init.d/xdm --debug restart

from a console to see what errors you get.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-03-21 20:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12 19:37 [gentoo-user] (EE) XKB: No components provided for device Virtual core keyboard Leandro Boscariol
2010-03-12 22:26 ` Mick
2010-03-16 16:35   ` Leandro Boscariol
2010-03-16 21:38     ` Mick
2010-03-17 22:20       ` Leandro Boscariol
2010-03-17 23:02         ` Mick
2010-03-19 11:16           ` Leandro Boscariol
2010-03-19 23:57             ` Mick
2010-03-21 12:33               ` Leandro Boscariol
2010-03-21 17:04                 ` [gentoo-user] " walt
2010-03-21 20:11                   ` Mick [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201003212011.45803.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox