Re: What controls X?
On Sat, Jun 18, 2011 at 11:41 AM, Camaleón <firstname.lastname@example.org> wrote:
> On Sat, 18 Jun 2011 08:18:50 -0400, Tom H wrote:
>> On Sat, Jun 18, 2011 at 7:25 AM, Camaleón <email@example.com> wrote:
>>>> Examing the system, I found in /etc/X11/xinit/xserverrc
>>>> exec /usr/bin/X -nolisten tcp "$@"
>>>> where "$@" I suppose is the console-number.
>>> Mmm, I dunno what holds that variable "$@" but it has to be documented
>>> somewhere ("man startx" or "man xserver") :-?
>> $@ is a bash positional parameter not an X-specific variable.
> Mmm, good but, what exactly holds?
It holds vt7.
As I said later in my earlier reply, I gave up on finding out its source...
>>>> But where does it get from?
>>> I've always thought that X server sets the first available vt for the x
>>> window system so I wonder why X server cannot dispose of vt7 to
>>> allocate the kdm/gdm session.
>> I tried to look for its source some time ago and gave up quickly. I'm
>> not running GNOME so this is from memory: the parent process of "exec
>> /usr/bin/X ..." calls a variable of the form "/org/gnome/<something>". I
>> thought that it might be a gconf key that might hold the VT but I didn't
>> find it.
> I've made some findings. By reading this bug report:
> I followed the suggested steps and edited "/etc/gdm3/daemon.conf" (this is
> a wheezey system):
> Restarted and seems it worked:
> test@debian:~$ grep -i vt /var/log/Xorg.0.log
> [ 37.345] (++) using VT number 9
> So at least we have found where we can set this under GNOME.
"FirstVT" used to be an upstream variable but its was dropped in the
upgrade from 2.20 to 2.24 and the Debian maintainer seems to be
applying a patch in order to perpetuate it in Debian.
Anyway, I don't think that this a solution to the OP's problem, unless
I'm misremembering it. No matter what is set as FirstVT, you can end
up at a higher number after logging out and logging back in because
console-kit-daemon would've kept that VT allocated.