Bug#528994: Info received (Bug#528994: Info received (Bug#528994: Acknowledgement (xserver-xorg-core: Corrupt mouse motion events send pointer to top-left of screen)))

2009-05-20 Thread sand
Diagnosis and patch available at 
.

This Debian bug should be reassigned to the xserver-xorg-input-evdev
package for tracking the upstream fix.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#528994: Info received (Bug#528994: Acknowledgement (xserver-xorg-core: Corrupt mouse motion events send pointer to top-left of screen))

2009-05-20 Thread sand
I have managed to work my way back up the failure chain, to the point
where GDB can stop the server before the mouse moves.  The failure is
associated with a motion event of {0,0} and is_absolute of 1.

(gdb) bt
#0  xf86PostMotionEventP (device=0x84a6308, is_absolute=1, first_valuator=0, 
num_valuators=2, valuators=0xbfc6af7c)
at ../../../../hw/xfree86/common/xf86Xinput.c:741
#1  0xb7a6a263 in ?? () from /usr/lib/xorg/modules/input//evdev_drv.so
#2  0x084a6308 in ?? ()
#3  0x0001 in ?? ()
#4  0x in ?? ()
(gdb) p *valuat...@num_valuators
$77 = {0, 0}

That would definitely send the pointer to {0,0}.  Unfortunately, I'm
using a mouse.  And, of course, the absolute motion event didn't show
up in my original traces because I never bothered to put a trace on
that call, because it was absolute motion.  Back to debugging evdev.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#528994: Acknowledgement (xserver-xorg-core: Corrupt mouse motion events send pointer to top-left of screen)

2009-05-18 Thread sand
Assuming that this xorg.conf option works properly

Option  "AccelerationScheme""none"

I don't think it's an acceleration bug.  I grabbed the debugging
symbols package and attached to Xorg, and I was seeing the
pDev->last.valuators array getting zeroed out in GetPointerEvents,
(getevents.c) somewhere around this block of code:

events = updateFromMaster(events, pDev, &num_events);

if (flags & POINTER_ABSOLUTE)
{
if (flags & POINTER_SCREEN) /* valuators are in screen coords */
{

valuators[0] = rescaleValuatorAxis(valuators[0], NULL,
   pDev->valuator->axes + 0,
   scr->width);
valuators[1] = rescaleValuatorAxis(valuators[1], NULL,
   pDev->valuator->axes + 1,
   scr->height);
}

moveAbsolute(pDev, &x, &y, first_valuator, num_valuators, valuators);
} else {
if (flags & POINTER_ACCELERATE)
accelPointer(pDev, first_valuator, num_valuators, valuators, ms);
moveRelative(pDev, &x, &y, first_valuator, num_valuators, valuators);
}

That causes the code to add the deltas to 0,0 to get the next absolute
position.

It's hard to pinpoint exactly where this is happening, because of the
code optimization, but the "updateFromMaster" call now seems like the
next place to look.



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#445100: xserver-xorg: Ctl-Alt-Fx has stopped working after a fresh install

2007-11-04 Thread sand
> > Can you try with xserver-xorg-video-ati 1:6.7.194-1 current in
> > experimental?
> 
> You nailed that one, Brice. The problem goes away with
> xserver-xorg-video-ati/experimental 1:6.7.194-1.

Is this a problem with xserver-xorg-video-ati, or with that driver's
interaction with xserver-xorg?

I'm using the experimental xserver-xorg-video-radeonhd package
(0.0.1+git20071006) on top of unstable and I can switch from the X
virtual terminal to the console virtual terminals and back again, but
the console virtual terminals don't send any video signal at all---my
monitor's status LED goes amber.  I'm wondering whether I need to
report this as an actual bug, or whether the next
xserver-xorg-video-radeonhd package build will pick up a fix
automatically.

Thanks,

Derek



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



Bug#219311: xdm: Default install missing referenced config files

2003-11-12 Thread sand
Branden Robinson writes:
> > "Xsetup" and "Xreset" are referenced in the config file, but they no
> > longer exist on disk.  This causes "xdm" to bomb out on startup.
> 
> I suspect your xdm daemon is in fact exiting for another reason.  Are
> there any error messages in /var/log/xdm.log?

The log file was showing this:

[[...blah blah blah...]]
  GetModeLine - scrn: 0 clock: 135000
  GetModeLine - hdsp: 1280 hbeg: 1296 hend: 1440 httl: 1688
vdsp: 1024 vbeg: 1025 vend: 1028 vttl: 1066 flags: 5
  SetGrabKeysState - enabled
[[...I exit out of XDM to restart it after an update...]]
  Thu Nov  6 07:06:09 2003 xdm error (pid 14156): can't execute 
"/usr/X11R6/lib/X11/xdm/Xreset" (err 2)
  (EE) [GLX]: Failed to add GLX extension (NVIDIA XFree86 driver not found)
  Thu Nov  6 07:06:11 2003 xdm info (pid 510): starting X server on :0
  Thu Nov  6 07:06:11 2003 xdm error (pid 14163): can't execute 
"/usr/X11R6/lib/X11/xdm/Xsetup" (err 2)
  Thu Nov  6 07:06:15 2003 xdm error (pid 14232): can't execute 
"/usr/X11R6/lib/X11/xdm/Xreset" (err 2)
  (EE) [GLX]: Failed to add GLX extension (NVIDIA XFree86 driver not found)
  Thu Nov  6 07:06:17 2003 xdm info (pid 510): starting X server on :0
  Thu Nov  6 07:06:17 2003 xdm error (pid 14239): can't execute 
"/usr/X11R6/lib/X11/xdm/Xsetup" (err 2)
  Thu Nov  6 07:06:21 2003 xdm error (pid 14308): can't execute 
"/usr/X11R6/lib/X11/xdm/Xreset" (err 2)

So it exited, started up, exited shortly thereafter, started up again,
exited shortly thereafter, etc.  Something was screwed up.

>From your comments, it looks like XDM was handling the missing Xsetup
and Xreset files correctly.  The message just needs to be downgraded
from "xdm error" to "xdm warning".

The more interesting issue is that the normal X server messages are
missing.  That's why I focused on the XDM errors in the first place.
I expect those missing messages are related to the X failure, but I
can't say for sure because (all together now!) I can't reproduce it.
Running X through XDM is working fine now.

So yeah, either close it, or mark it as a "wishlist" item to change
"error" to "warning".

Thanks,

Derek

-- 
Derek Upham
[EMAIL PROTECTED]

"Ha!  Your Leaping Tiger Kung Fu is no match for my Frightened Piglet style!"




Bug#219311: xdm: Default install missing referenced config files

2003-11-05 Thread sand
Package: xdm
Version: 4.2.1-13
Severity: grave

The "Confiles" section of the package description lists various files
in /etc/X11/xdm (and "/usr/X11R6/lib/X11/xdm" links to this directory):

 /etc/X11/xdm/Xaccess df56c4c3eb66cbc9470c07da301acd7b
 /etc/X11/xdm/Xresources 06d02faa0199503f98c9ebd9b7a81517
 /etc/X11/xdm/Xservers 6689c34e7b3f2e1f7af17a3350c1490c
 /etc/X11/xdm/Xsession 7665beb7c953f2ad9df08f7f73b64fb7
 /etc/X11/xdm/Xstartup 8e6bb9af52a4f6dced7b7a890aa34851
 /etc/X11/xdm/Xwilling 5aec82ecf912e050a02f84d8d572

The "xdm-config" file references the following scripts:

  DisplayManager*startup:   /usr/X11R6/lib/X11/xdm/Xstartup
  DisplayManager*resources: /usr/X11R6/lib/X11/xdm/Xresources
  DisplayManager*session:   /usr/X11R6/lib/X11/xdm/Xsession
  DisplayManager*setup: /usr/X11R6/lib/X11/xdm/Xsetup
  DisplayManager*reset: /usr/X11R6/lib/X11/xdm/Xreset

"Xsetup" and "Xreset" are referenced in the config file, but they no
longer exist on disk.  This causes "xdm" to bomb out on startup.

Derek

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux priss 2.6.0-test9 #1 Mon Nov 3 16:11:30 PST 2003 i686
Locale: LANG=POSIX, LC_CTYPE=POSIX

Versions of packages xdm depends on:
ii  cpp-3.2  1:3.2.3-8   The GNU C preprocessor
ii  debconf  1.3.20  Debian configuration management sy
ii  libc62.3.2.ds1-9 GNU C Library: Shared libraries an
ii  libpam0g 0.76-14 Pluggable Authentication Modules l
ii  libxaw7  4.2.1-13X Athena widget set library
ii  xbase-clients4.2.1-13miscellaneous X clients
ii  xlibs4.2.1-13X Window System client libraries

-- debconf information:
* xdm/default_servers_nolisten_tcp: 
  xdm/stop_running_server_with_children: false
* xdm/default_servers_100dpi: 
  xdm/daemon_name: /usr/bin/X11/xdm
* xdm/default_nolisten_udp: 
  shared/default-x-display-manager: xdm