From: Florian Kulzer on
On Mon, Feb 08, 2010 at 20:32:44 -0500, Stephen Powell wrote:

[...]

> I was able to reproduce the symptoms that you describe above when I first
> arrived home. I verified that the X server was running on vt 7, then
> did a logout. The login screen started on vt 8. From then on, no matter
> what I did to stop and restart the server, it ended up on vt 8. There
> were some pending updates; so I applied updates, shutdown, and rebooted.
> But now I can no longer (at least for now) reproduce the problem.
> No matter how I shutdown and restart the server, it ends up on vt 7,
> which is of course the desired behavior.
>
> Does that mean it's fixed? Maybe. Then again, maybe not. I found
> the following bug report:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=348033

I think the present problem, which I can still reproduce on my Sid system,
is not related to #348033.

I find that VT7 often cannot be deallocated after X shuts down, which
explains why X has to use VT8 if started up again:

# deallocvt 7
VT_DISALLOCATE: Device or resource busy
deallocvt: could not deallocate console 7

Killing console-kit-daemon makes VT7 available again for me in this
situation, and X starts normally after that. I have not bothered to
investigate this issue any further.

--
Regards, |
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
From: Stephen Powell on
On Sat, 13 Feb 2010 07:15:20 -0500 (EST), Florian Kulzer wrote:
> I think the present problem, which I can still reproduce on my Sid system,
> is not related to #348033.
>
> I find that VT7 often cannot be deallocated after X shuts down, which
> explains why X has to use VT8 if started up again:
>
> # deallocvt 7
> VT_DISALLOCATE: Device or resource busy
> deallocvt: could not deallocate console 7
>
> Killing console-kit-daemon makes VT7 available again for me in this
> situation, and X starts normally after that. I have not bothered to
> investigate this issue any further.

Well, Florian, after today's upgrade I am now where you are with Sid.
The X server is on vt7, I logout of the GNOME desktop, and X restarts
on vt8. I switch to a text console, issue "deallocvt 7", and it fails.
I kill console-kit-daemon, then "deallocvt 7" is successful. Another
logout from the GNOME desktop and the X server starts up on vt7.
(console-kit-daemon restarts as soon as I switch back to the X console).


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/740985477.12719101266278663236.JavaMail.root(a)md01.wow.synacor.com
From: Florian Kulzer on
On Mon, Feb 15, 2010 at 19:04:23 -0500, Stephen Powell wrote:
> On Sat, 13 Feb 2010 07:15:20 -0500 (EST), Florian Kulzer wrote:

[...]

> > I find that VT7 often cannot be deallocated after X shuts down, which
> > explains why X has to use VT8 if started up again:
> >
> > # deallocvt 7
> > VT_DISALLOCATE: Device or resource busy
> > deallocvt: could not deallocate console 7
> >
> > Killing console-kit-daemon makes VT7 available again for me in this
> > situation, and X starts normally after that. I have not bothered to
> > investigate this issue any further.
>
> Well, Florian, after today's upgrade I am now where you are with Sid.
> The X server is on vt7, I logout of the GNOME desktop, and X restarts
> on vt8. I switch to a text console, issue "deallocvt 7", and it fails.
> I kill console-kit-daemon, then "deallocvt 7" is successful. Another
> logout from the GNOME desktop and the X server starts up on vt7.
> (console-kit-daemon restarts as soon as I switch back to the X console).

I came across a long-standing issue with the daemon running in 64
threads, maybe the present annoyance is related. The report gives me the
impression that some kludges are currently used for the daemon's
interaction with the VTs:

https://bugs.freedesktop.org/show_bug.cgi?id=17720

--
Regards, |
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100219210001.GA4947(a)isar.localhost