Bug 15956

Created attachment 16573 [details]
output of dmesg

The attached file is the output of the dmesg command so the intel-developers can see which Intel graphics card is being used.

Created attachment 16574 [details]
output of kern.log

As this bug has caused hard crashes I am attaching the kern.log file.

Created attachment 16575 [details]
xorg.conf-file

(In reply to comment #0)
> Created an attachment (id=16572) [details]
> the copy of Xorg.0.log
> 
> Under Ubuntu Hardy 8.04 I get the following odd performance:
> 1) When moving a window (let's say console) it first goes into Maximize before
> it is possible to move it.
> 2) When selecting parts of the desktop the selected area is not cleared.
> 3) When trying to move icons, the documents, program, directory is opened
> instead.

At least 1 and 3 sound like you're getting double clicks instead of single clicks which would indicate an input issue.
does this happen when you click with your touchpad?

From your log file I see that you have /dev/input/mice and /dev/input/event9 (synaptics). If you click with the touchpad, the same button event would appear through event9 and through /dev/input/mice, causing doubleclicks.
Please remove either Configured Mouse or Touchpad from your config and try again, this should fix the issue.


As a side note - please mark attachments as plain text if they are, makes them easier to look at.

(In reply to comment #4)
> (In reply to comment #0)
> > Created an attachment (id=16572) [details] [details]
> > the copy of Xorg.0.log
> > 
> > Under Ubuntu Hardy 8.04 I get the following odd performance:
> > 1) When moving a window (let's say console) it first goes into Maximize before
> > it is possible to move it.
> > 2) When selecting parts of the desktop the selected area is not cleared.
> > 3) When trying to move icons, the documents, program, directory is opened
> > instead.
> 
> At least 1 and 3 sound like you're getting double clicks instead of single
> clicks which would indicate an input issue.
> does this happen when you click with your touchpad?
> 
> From your log file I see that you have /dev/input/mice and /dev/input/event9
> (synaptics). If you click with the touchpad, the same button event would appear
> through event9 and through /dev/input/mice, causing doubleclicks.
> Please remove either Configured Mouse or Touchpad from your config and try
> again, this should fix the issue.
I have tried to remove one at the time, and it results on being able to move mouse, and clicking icons, moving icons is not possible. What happens then is that you only draw a selection box.
As a side note: I have posted more information here as I thought it was related to Nautilus / compiz: https://bugs.launchpad.net/ubuntu/+source/nautilus
/+bug/221691

Since most of the settings in the xorg.conf is set by the system, could it be that the pre configured settings are wrong? 

What would be the normal settings for the Dell d420?

(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #0)
> > > Created an attachment (id=16572) [details] [details] [details]
> > > the copy of Xorg.0.log
> > > 
> > > Under Ubuntu Hardy 8.04 I get the following odd performance:
> > > 1) When moving a window (let's say console) it first goes into Maximize before
> > > it is possible to move it.
> > > 2) When selecting parts of the desktop the selected area is not cleared.
> > > 3) When trying to move icons, the documents, program, directory is opened
> > > instead.
> > 
> > At least 1 and 3 sound like you're getting double clicks instead of single
> > clicks which would indicate an input issue.
> > does this happen when you click with your touchpad?
> > 
> > From your log file I see that you have /dev/input/mice and /dev/input/event9
> > (synaptics). If you click with the touchpad, the same button event would appear
> > through event9 and through /dev/input/mice, causing doubleclicks.
> > Please remove either Configured Mouse or Touchpad from your config and try
> > again, this should fix the issue.
> I have tried to remove one at the time, and it results on being able to move
> mouse, and clicking icons, moving icons is not possible. What happens then is
> that you only draw a selection box.


can you please open up xev and click into the window. check the output on the console if it reports a single or a double press and release event (please check both)

i remember that when I didn't have grabs sorted out in mpx, i had a similar issue to 2) due to nautilus not releasing the grab properly. what we need to figure out is whether this is a nautilus or an X issue.

Created attachment 16642 [details]
output of xev

After running the xev command I clicked buttons and tried to move the window. Compiz is enabled.

On Mon, May 19, 2008 at 11:41:28PM -0700, bugzilla-daemon@freedesktop.org wrote:
> Created an attachment (id=16642)
>  --> (http://bugs.freedesktop.org/attachment.cgi?id=16642)
> output of xev
> 
> After running the xev command I clicked buttons and tried to move the window.
> Compiz is enabled.
 
well that is some weird output.

I don't see any drag events at all (MotionEvent, state 0x100). And you get a
configure notify before the button press/release events, which I don't even
know how to reproduce. I guess it's the WM interfering somehow.
Can you please just drag your mouse around inside the xev window with button
1 pressed and attach the xev log. Thx.

Created attachment 16643 [details]
output of xev while draging and holding mouse button

As requested I have moved the mouse inside the box while holding the left mouse button (button 1).

Output saved to txt-file which is attached.

On Tue, May 20, 2008 at 01:41:05AM -0700, bugzilla-daemon@freedesktop.org wrote:
> --- Comment #10 from Trond Husø <trond@trondhuso.no>  2008-05-20 01:41:03 PST ---
> Created an attachment (id=16643)
>  --> (http://bugs.freedesktop.org/attachment.cgi?id=16643)
> output of xev while draging and holding mouse button
> 
> As requested I have moved the mouse inside the box while holding the left mouse
> button (button 1).
> 
> Output saved to txt-file which is attached.

Here's the problem:


ButtonPress event, serial 28, synthetic NO, window 0x4400001,
root 0x5a, subw 0x0, time 6229820, (165,168), root:(594,219),
state 0x0, button 1, same_screen YES

ConfigureNotify event, serial 28, synthetic YES, window 0x4400001,
event 0x4400001, window 0x4400001, (427,49), width 178, height
178, border_width 2, above 0x12007c4, override NO

MotionNotify event, serial 28, synthetic NO, window 0x4400001,
root 0x5a, subw 0x0, time 6229951, (164,168), root:(593,219),
state 0x100, is_hint 0, same_screen YES

ButtonPress event, serial 28, synthetic NO, window 0x4400001,
root 0x5a, subw 0x0, time 6230000, (164,168), root:(593,219),
state 0x100, button 1, same_screen YES

For some reason you get two button press events with button 1. IIRC, this is
something nautilus doesn't like, leading to the symptoms described above.

Now we need to figure out how that could happen. The server is supposed to
filter these events if they happen. Do you still use both devices or just one?
If just one, which one?

> MotionNotify event, serial 28, synthetic NO, window 0x4400001,
> root 0x5a, subw 0x0, time 6229951, (164,168), root:(593,219),
> state 0x100, is_hint 0, same_screen YES
> 
> ButtonPress event, serial 28, synthetic NO, window 0x4400001,
> root 0x5a, subw 0x0, time 6230000, (164,168), root:(593,219),
> state 0x100, button 1, same_screen YES
> 
> For some reason you get two button press events with button 1. IIRC, this is
> something nautilus doesn't like, leading to the symptoms described above.
> 
> Now we need to figure out how that could happen. The server is supposed to
> filter these events if they happen. Do you still use both devices or just one?
> If just one, which one?
> 
> 
> -- 
> Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
All I use is the mousepad / synaptic on this computer. In the keyboard
there is a mousebutton and I use this as well. I mostly use this. The
buttons are related to the touchpad. 
Link to a review of the computer, but is used here more to show that I
use the blue button and the left mouse button near the end of the
computer most. that is the button 1.

http://www.notebookreview.com/default.asp?newsID=3101&review=Dell+Latitude+D420

Update:
Mousepad + left mouse button below = can move window
Mousepad + left mouse button above = can move window
Blue button + left mouse button closest to blue button = can move window
Blue button + left mouse button furthest away from blue button = can't move window.

This could mean that other users with the same setup would/could get the same problem.

-trond-

Created attachment 16651 [details]
output of xev while using the pad and clicking the "correct" mouse button

I have tested more mouse combinations and found that I can move windows with the correct combination.
Please check latest attachment.

> --- Comment #12 from Trond Husø <trond@trondhuso.no>  2008-05-20 03:33:24 PST ---
> Update:
> Mousepad + left mouse button below = can move window
> Mousepad + left mouse button above = can move window
> Blue button + left mouse button closest to blue button = can move window
> Blue button + left mouse button furthest away from blue button = can't move
> window.
> 
> This could mean that other users with the same setup would/could get the same
> problem.

this indicates either a device issue or an issue with the synaptics driver.
Without going into the driver and adding printfs or debugging what is
happening when you press the button, I can't really help much.


On Tue, 2008-05-20 at 22:28 -0700, bugzilla-daemon@freedesktop.org wrote:
--- Comment #14 from Peter Hutterer <peter@cs.unisa.edu.au>  2008-05-20 22:28:34 PST ---
> 
> > This could mean that other users with the same setup would/could get the same
> > problem.
> 
> this indicates either a device issue or an issue with the synaptics driver.
> Without going into the driver and adding printfs or debugging what is
> happening when you press the button, I can't really help much.
> 

I don't mind using a driver with some debugging information if it solves
the problem.

-Trond-



I have filed this bug at launchpad, and another user - also using a Dell
has the same problem. He has reported this:

----
When I use the "normal" left mouse button (the one below the touchpad)
the spots return, the desktop icons can no longer be moved and in short
the bug returns.  If I click with the mouse buttons below the spacebar
numerous times I can get the bug to "disengage" in that the new desktop
icons can be moved and the spots do not re-occur but the old ones are
still present and the old desktop icons cannot be moved......

I am running a Dell Inspiron 8500 from 2003.  It has a P4 with 1560MB
PC
2100 SD Ram and a Nvidia graphics card.  It is indeed equipped with the
dual mouse buttons.  One set is below the spacebar and the other is
below the finger pad.

USING THE MOUSE BUTTONS BELOW THE SPACEBAR EVERYTHING WORKS AS IT
SHOULD.

What is it you would like form me xev output.  It is pages long and both
the outputs after mouse clicks from the middle and bottom sets are the
same.

On Wed, May 21, 2008 at 12:01:13PM -0700, bugzilla-daemon@freedesktop.org wrote:
> --- Comment #15 from Trond Husø <trond@trondhuso.no>  2008-05-21 12:01:12 PST ---
> 
> I don't mind using a driver with some debugging information if it solves
> the problem.
 
great. In this case you need to get the synaptics driver and salt it with
xf86Msg(X_ERROR, "blah blah").
Look for any calls to xf86Post{Motion|Button}Event, that is the hook into the
server
 
> I have filed this bug at launchpad, and another user - also using a Dell
> has the same problem. He has reported this:
> 
> ----
> When I use the "normal" left mouse button (the one below the touchpad)
> the spots return, the desktop icons can no longer be moved and in short
> the bug returns.  If I click with the mouse buttons below the spacebar
> numerous times I can get the bug to "disengage" in that the new desktop
> icons can be moved and the spots do not re-occur but the old ones are
> still present and the old desktop icons cannot be moved......

yeah, don't worry about the leftover spots, they will be gone when this bug if
fixed.

 
> USING THE MOUSE BUTTONS BELOW THE SPACEBAR EVERYTHING WORKS AS IT
> SHOULD.

this really indicated driver/device issues.
 
> What is it you would like form me xev output.  It is pages long and both
> the outputs after mouse clicks from the middle and bottom sets are the
> same.

excerpts of the events around button press/release are interesting.


One other thing we could do to narrow it down:
get the event number from /proc/bus/input/devices, then create an InputDevice
section with driver evdev and device /dev/input/event... Remove the synaptics
device, restart the server.
You'll loose some touchpad functionality, but if the same bug appears with the
evdev driver, it's a device issue. otherwise it'll be synaptics.

Created attachment 16698 [details]
Output of /proc/bus/input/devices

Attached is the output of /proc/bus/input/devices
I won't mind if someone told me how to set up the device as suggested in last post.

> --- Comment #17 from Trond Husø <trond@trondhuso.no>  2008-05-22 13:34:23 PST ---
> Created an attachment (id=16698)
>  --> (http://bugs.freedesktop.org/attachment.cgi?id=16698)
> Output of /proc/bus/input/devices
> 
> Attached is the output of /proc/bus/input/devices
> I won't mind if someone told me how to set up the device as suggested in last
> post.

Section "InputDevice"
     Identifier "dodgy touchpad"
     Driver "evdev"
     Option "Device" "/dev/input/event9"
EndSection

Section "ServerLayout"
 [...]
 InputDevice "dodgy touchpad" "CorePointer"
EndSection


This uses evdev instead of synaptics (make sure you remove the InputDevice
that references synaptics from your ServerLayout)

Then try the same thing again, but with Driver "mouse" and Device
"/dev/input/mouse2".

If both work as expected, it's a synaptics issue. If both fail with the same
problems, its probably the device.

Trond:

did you get a chance to try the different drivers?

On Wed, 2008-05-21 at 16:41 -0700, bugzilla-daemon@freedesktop.org
wrote:
> /proc/bus/input/devices
I: Bus=0011 Vendor=0002 Product=0008 Version=0000
N: Name="PS/2 Mouse"
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=mouse1 event3 
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=mouse0 event0 
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0002 Product=0008 Version=6337
N: Name="AlpsPS/2 ALPS GlidePoint"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input4
U: Uniq=
H: Handlers=mouse2 event4 
B: EV=f
B: KEY=420 0 70000 0 0 0 0 0 0 0 0
B: REL=3
B: ABS=1000003

Ten year old bugs are probably not going to be followed up on...