Processed: Re: Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-07-26 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 290625 xserver-xorg-core
Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) 
no keyboard on 1st startup under KDM, competing with getty on VC2
Bug reassigned from package `xserver-xfree86' to `xserver-xorg-core'.

> retitle 290625 xserver-xorg-core: race condition when attaching to a VT
Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) 
no keyboard on 1st startup under KDM, competing with getty on VC2
Changed Bug title to `xserver-xorg-core: race condition when attaching to a VT' 
from `xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no 
keyboard on 1st startup under KDM, competing with getty on VC2'.

> severity 290625 minor
Bug#290625: xserver-xorg-core: race condition when attaching to a VT
Severity set to `minor' from `normal'

> kthxbye
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-07-26 Thread Julien Cristau
reassign 290625 xserver-xorg-core
retitle 290625 xserver-xorg-core: race condition when attaching to a VT
severity 290625 minor
kthxbye

On Thu, Jul 26, 2007 at 14:10:01 +0300, Vassilii Khachaturov wrote:

> The bug only manifests itself on a particular upgrade path, described in
> the bug thread messages (which I believe have all the needed reproduction
> information). If you set up a fresh system, it definitely
> doesn't happen. It could very well be that upgrading from an oldstable
> system+XFree86 to the today's stable or testing could still trigger it,
> but as I said I don't have the hardware to reproduce it. Note that it
> relies on a not-very-sane decision in (not fully) updating a manually
> touched kdmrc as I elaborated on the bug thread in my Feb 4
> message. If you ask me, this downgrades the importance of the bug
> considerably, but, as you see in the reply from Michel Daenzer the same
> day, it's still an X bug. My guess would be that the bug is still there,
> but one has to retest the fishy upgrade path to see.
> 
OK, thanks for following up!

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-07-26 Thread Vassilii Khachaturov
> > I am sorry, all the Debian systems around here at the university that I
> > have access to have already been upgraded to the up-to-date xorg/etch,
> > so I don't have an opportunity to retest it.
>
> Hi Vassilii,
>
> do you mean that the problem doesn't happen with the Xorg X server?
> If so, I think this bug can be closed.  In any case, it's always better
> to explicitly say when you start X which vt you want it to use.

The bug only manifests itself on a particular upgrade path, described in
the bug thread messages (which I believe have all the needed reproduction
information). If you set up a fresh system, it definitely
doesn't happen. It could very well be that upgrading from an oldstable
system+XFree86 to the today's stable or testing could still trigger it,
but as I said I don't have the hardware to reproduce it. Note that it
relies on a not-very-sane decision in (not fully) updating a manually
touched kdmrc as I elaborated on the bug thread in my Feb 4
message. If you ask me, this downgrades the importance of the bug
considerably, but, as you see in the reply from Michel Daenzer the same
day, it's still an X bug. My guess would be that the bug is still there,
but one has to retest the fishy upgrade path to see.

HTH,
Vassilii



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-07-24 Thread Julien Cristau
On Sun, Mar 11, 2007 at 11:57:33 +0200, Vassilii Khachaturov wrote:

> > You mentioned that you reproduced this bug a couple month ago. But, were
> > you using Xorg/Etch at this point? If not, could you try?
> 
> Hi Brice,
> 
> I am sorry, all the Debian systems around here at the university that I
> have access to have already been upgraded to the up-to-date xorg/etch,
> so I don't have an opportunity to retest it.

Hi Vassilii,

do you mean that the problem doesn't happen with the Xorg X server?
If so, I think this bug can be closed.  In any case, it's always better
to explicitly say when you start X which vt you want it to use.

Cheers,
Julien


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-03-11 Thread Vassilii Khachaturov
> You mentioned that you reproduced this bug a couple month ago. But, were
> you using Xorg/Etch at this point? If not, could you try?

Hi Brice,

I am sorry, all the Debian systems around here at the university that I
have access to have already been upgraded to the up-to-date xorg/etch,
so I don't have an opportunity to retest it. However, if you have a spare
Sarge machine, and install KDM there, just do a sarge->etch upgrade on it
while (mistakenly) not allowing the ServerVTs=... line to be merged into
the resulting kdmrc (as per the history of the bug). If, after that, the
bug doesn't manifest itself (check across 1 reboot as well), then you
probably should report the fact on the bug thread and happily close it.
(The bug is pretty deterministic).

HTH,

Vassilii



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-01-17 Thread Vassilii Khachaturov
> Hi Vassilii,
>
> About 2 years ago, you reported a bug to the Debian BTS regarding
> keyboard not working in X under KDM, apparently related with gett on
> VC2. Did you reproduce this problem recently? If not, I will close this
> bug in the next weeks.

I have seen the problem later, as late as 4 months ago. The bug is pretty
esoteric as it requires particular problem in the course of the kdmrc etc
files updates merge on the part of user, and only across some specific
version numbers leap. Nevertheless, I don't believe someone actually
committed a patch to have it fixed.

V



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#290625: xserver-xfree86: sarge upgrade (4.3.0.dfsg.1-8 -> 4.3.0.dfsg.1-10) no keyboard on 1st startup under KDM, competing with getty on VC2

2007-01-16 Thread Brice Goglin
Hi Vassilii,

About 2 years ago, you reported a bug to the Debian BTS regarding
keyboard not working in X under KDM, apparently related with gett on
VC2. Did you reproduce this problem recently? If not, I will close this
bug in the next weeks.

Thanks,
Brice



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]