Bug#616644: xdm: strange behaviour after logging out: not reading kbd or mouse

2011-03-06 Thread enno.vet

Package: xdm
Version: 1:1.1.10-3
Severity: important

Using xdm as session manager, after logging out from windowmanager (e16) 
session user has again xdm login screen.  Strangely any input typed on kbd only 
gets echoed onscreen after moving the mouse.  This "echo delay" includes the 
enter key as well as the VT switch keys (C+A+F[1-6]{1}).
Also a password containing some unusual chars (such as #@" and the like) is not 
recognised correctly then, so cannot login.

Alternatively (about every other time) the kbd input is echoed immediately (as 
normal) and recognised well, but the mouse is as dead as a doornail, and is not 
resurrected on entering windowmanager session.  Strangely though a mouse tap 
seems to be noticed -- and reacted to -- only after having typed a key on the 
kbd.  Pointer movement is nil, however.

This strange behaviour can be "re-set" to normal by switching to a VT and then 
back to VT7.

Note: This only happens after coming back to login screen after logging out 
from  windowmanager session.  On first login there's no problem at all (apart 
from the spaces echoed by the password field, s. bug #575486).

Not sure if this comes from xdm proper or some associated xlib.
Just noticed: same behaviour is also shown by xdm 1:1.1.8-5.

As noted before, my kernel is a custom kernel out of debian linux-source-2.6.30 
which I have been using since its compilation without any of these X-related 
problems.  Findings with std debian 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 
2011 i686 GNU/Linux are exactly the same.

Hardware: dell inspiron 1300 (laptop) with synaptics touchpad.

Brgds, e.

Excerpt from .xsession-errors:
=
Xsession: X session started for enno at Sat Mar  5 17:12:04 CET 2011
non-network local connections being added to access control list
vol set to 22, 22
igain set to 0, 0
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
  after 11892 requests (11628 known processed) with 0 events remaining.
aumix: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
  after 131 requests (113 known processed) with 0 events remaining.
X connection to :0.0 broken (explicit kill or server shutdown).
=

Excerpt from /var/log/xdm.log:
=
Sat Mar  5 17:11:37 2011 xdm info (pid 2545): sourcing /etc/X11/xdm/Xsetup
Sat Mar  5 17:12:04 2011 xdm info (pid 2545): sourcing /etc/X11/xdm/Xstartup
Sat Mar  5 17:12:04 2011 xdm info (pid 2564): executing session 
/etc/X11/xdm/Xsession
Sat Mar  5 17:13:49 2011 xdm info (pid 2545): sourcing /etc/X11/xdm/Xreset
Sat Mar  5 17:13:49 2011 xdm info (pid 1823): Starting X server on :0
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:  Type "ONE_LEVEL" has 1 levels, but  has 2 symbols
>   Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
[config/hal] couldn't initialise context: (null) ((null))
:31:2: error: invalid preprocessing directive #xlogin
:32:2: error: invalid preprocessing directive #xlogin
:33:2: error: invalid preprocessing directive #xlogin
:34:2: error: invalid preprocessing directive #xlogin
:35:2: error: invalid preprocessing directive #xlogin
:36:2: error: invalid preprocessing directive #xlogin
:37:2: error: invalid preprocessing directive #xlogin
:38:2: error: invalid preprocessing directive #xlogin
=

Excerpt from /var/log/Xorg.0.log:
=
(II) evaluating device (Keyboard)
(II) evaluating device (Mouse)
(**) Keyboard: xkb_rules: "xorg"
(**) Option "xkb_model" "evdev"
(**) Keyboard: xkb_model: "evdev"
(**) Keyboard: xkb_layout: "de"
(--) Mouse auto-dev sets device to /dev/input/event6
(**) Option "Device" "/dev/input/event6"
(--) Mouse touchpad found
[config/hal] couldn't initialise context: (null) ((null))
(II) Keyboard: Device reopened after 1 attempts.
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(II) intel(0): xf86UnbindGARTMemory: unbind key 0
(II) intel(0): xf86UnbindGARTMemory: unbind key 1
(II) intel(0): xf86UnbindGARTMemory: unbind key 3
(II) intel(0): xf86UnbindGARTMemory: unbind key 4
(II) Open ACPI successful (/var/run/acpid.socket)
(II) AIGLX: Resuming AIGLX clients after VT switch
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x0080 (pgoffset 2048)
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x0100 (pgoffset 4096)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x0200 (pgoffset 8192)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x0380 (pgoffset 14336)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x

Re: xdm strange behaviour

2004-04-06 Thread Branden Robinson
On Thu, Feb 26, 2004 at 02:18:50PM +0100, [EMAIL PROTECTED] wrote:
> Hi @all
> 
>   I have noticed a strange behaviour of your 4.3.0-2 version of
> xdm:
> 
> tcp0  0 0.0.0.0:49775   0.0.0.0:* LISTEN 
> 7319/xdm

Thanks for your report.

We expect this to be fixed in 4.3.0-8.

-- 
G. Branden Robinson|I have a truly elegant proof of the
Debian GNU/Linux   |above, but it is too long to fit
[EMAIL PROTECTED] |into this .signature file.
http://people.debian.org/~branden/ |


signature.asc
Description: Digital signature


Re: xdm strange behaviour

2004-03-22 Thread ROBERTOJIMENOCA
[EMAIL PROTECTED] wrote:
> On , ROBERTOJIMENOCA wrote:
> > [EMAIL PROTECTED] wrote:
> > > I have noticed a strange behaviour of your 4.3.0-2 version of xdm:
> > > 
> > > tcp0  0 0.0.0.0:49775   0.0.0.0:*   LISTEN  
> > > 7319/xdm
> > > 
> > > As far as I suspect (after reading man xdm) I suspect that the xdm
> > > chooser was activated but I do not think that I did it as I did not
> > > change my config...
> > > 
> > > This behaviour occurred on three machines, two were downgraded, the last
> > > remains in this state
> > > 
> > > Do you see anything which is not correct in here? Have I made a mistake
> > > or is this really a bug?
> > > 
> > > Hope I did not waste your time
> > 
> > I also have this port open:
> > tcp0  0 0.0.0.0:33016   0.0.0.0:*   LISTEN  
> >2179/xdm
> > 
> > Did you found why this port is open?
> 
> I believe it's the xdm chooser port but I do not know why this sould be
> happening as I did not enable it...
> 
> My "solution" was to downgrade to testing, which does not expose this
> behaviour

This port seems not to be the xdm chooser.
There's a bug or a Trojan in that binary (or source). 
If you don't know a good solution (downgrading is only a workaround)
I'll fill a bug report.




Re: xdm strange behaviour

2004-03-20 Thread ROBERTOJIMENOCA
[EMAIL PROTECTED] wrote:
> I have noticed a strange behaviour of your 4.3.0-2 version of xdm:
> 
> tcp0  0 0.0.0.0:49775   0.0.0.0:*   LISTEN  
> 7319/xdm
> 
> As far as I suspect (after reading man xdm) I suspect that the xdm
> chooser was activated but I do not think that I did it as I did not
> change my config...
> 
> This behaviour occurred on three machines, two were downgraded, the last
> remains in this state
> 
> Do you see anything which is not correct in here? Have I made a mistake
> or is this really a bug?
> 
> Hope I did not waste your time

I also have this port open:
tcp0  0 0.0.0.0:33016   0.0.0.0:*   LISTEN 
2179/xdm

Did you found why this port is open?




xdm strange behaviour

2004-02-26 Thread harald
Hi @all

I have noticed a strange behaviour of your 4.3.0-2 version of
xdm:

tcp0  0 0.0.0.0:49775   0.0.0.0:*   LISTEN 
7319/xdm

As far as I suspect (after reading man xdm) I suspect that the xdm
chooser was activated but I do not think that I did it as I did not
change my config...

/etc/X11/xdm/Xaccess:
has all lines commented out

/etc/X11/xdm/Xresources:
Chooser*geometry:   700x500+300+200
Chooser*allowShellResize:   false
Chooser*viewport.forceBars: true
Chooser*label.font: *-new century schoolbook-bold-i-normal-*-240-*
Chooser*label.label:XDMCP Host Menu from CLIENTHOST
Chooser*list.font:  -*-*-medium-r-normal-*-*-230-*-*-c-*-iso8859-1
Chooser*Command.font:   *-new century schoolbook-bold-r-normal-*-180-*

/etc/X11/xdm/Xservers:
:0 local /usr/X11R6/bin/X vt7 -dpi 100 -nolisten tcp

/etc/X11/xdm/xdm-config:
DisplayManager.requestPort: 0

Only strange thing in logfile:
Wed Feb 25 15:34:34 2004 xdm error (pid 20035): can't execute 
"/usr/X11R6/lib/X11/xdm/Xsetup" (err 2)

This behaviour occured on three machines, two were downgraded, the last
remains in this state

Do you see anything which is not correct in here? Have I made a mistake
or is this really a bug?

Hope I did not waste your time

Sincerely 
Harald Jenny

-- 
Lord, grant me the serenity to accept the things I cannot
change, the courage to change the things I can, and the
wisdom to hide the bodies of the people I had to kill because
they pissed me off.