[hardy] Nautilus ignores clicks on icons after selecting an empty desktop area.

Bug #201436 reported by Elizabeth Greene
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-input-synaptics (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: nautilus

Hi!

I have an intermittent issue with nautilus, and have finally been able to find the sequence of events to cause it. It seems that during use, my PC will stop responding to Icon clicks on the desktop. I can draw a select box around them, and I can right click on the desktop, but I can't right or left-click the icons. I am able to work normally other than this, and the gnome-panels all remain responsive. The only way to run icons from the desktop is to open a places window of the desktop, and run them from there, or kill nautilus and wait for it to respawn.

Steps to reproduce:
From the desktop, draw a box around an empty area of the desktop, and then draw an area around another empty section of the desktop. Then try to click on a desktop icon. Your click event is ignored, and two tiny artifacts of the select boxes remain visible on the screen.

Note: I thought this might be a duplicate of Bug #164996, but I disabled all of the inputdevices sections in my xorg.conf except for Synaptic (Touchpad) and the keyboard, and still experience the behavior.

<email address hidden>

Nautilus 1.2.22.0
Ubuntu 8.04 Hardy (Development Release)

It's worth noting that I have experienced this since upgrading to Hardy, so it's not a recent bug. I cannot say if it happened in Gutsy.

Tags: hardy
Revision history for this message
Sebastien Bacher (seb128) wrote :

Not confirming there. Does the selection is still displayed after you stop clicking?

Changed in nautilus:
importance: Undecided → Low
Revision history for this message
Elizabeth Greene (nerdygirl-ellie) wrote :

Sort of. The shaded area inside the select box returns to normal, but the selection border box remains visible.

It's possible there is something broken on my system, I've noticed an aberrant looks like I'm double clicking but I am only single clicking in evolution too.

-ellie

Revision history for this message
Sebastien Bacher (seb128) wrote :

I tried on several boxes and can't confirm that, doesn't seem to really be a nautilus issue from the description

Revision history for this message
Benjamin Thyreau (benji2) wrote :

Hi,
I remember experiencing almost the same kind of annoying behaviour, as a side effect of the "double-click" issue that i describe at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/197121
I guess the two bugs are somehow related.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still get the issue? do you get similar issues in other applications?

Changed in nautilus:
status: New → Incomplete
Revision history for this message
Elizabeth Greene (nerdygirl-ellie) wrote :

Hi Sebastien,

Yes, the issue is still occurring, but it is not really a nautilus issue. This problem only seems to occur on laptops with touchpads and pointing sticks. A bug somewhere else is causing the system to send an incorrect click event.

Somewhere inside of nautilus there is a race condition or somesuch that can be set off by calling onmousedown followed by onclick without calling onmouseup inbetween. It is ignorable as it only occurs because of the trackpad issue.

-ellie

Revision history for this message
Sebastien Bacher (seb128) wrote :

reassigning tentatively to xorg though I'm not sure the issue is there, they might have a better idea though

Changed in nautilus:
status: Incomplete → New
Revision history for this message
Morten (morethan) wrote :

Belongs in xserver-xorg-input-synaptics with 203296, 201436 and 197121 (and possibly others)

Setting your system to using only one mouse, with driver "mouse", restores normal function. This disables all synaptics-specific configuration, though. Affects laptops with synaptics mousepad+trackpoint and mouse buttons for each of them (e.g. my Dell Latitude D420).

Through experimenting with xorg.conf I have managed to enable/disable each of the devices, but bugs *always* occur when using driver "synaptics" for the touchpad (either with device /dev/psaux or /dev/input/mice) and driver "mouse" for the stick. It would appear pressing the mouse button on the touchpad whilst moving the trackpoint generates an extra click event. When I disable the Touchpad, I cannot press anything with the buttons on the touchpad *unless* I am moving the trackpoint... ^_^

Revision history for this message
Bryce Harrington (bryce) wrote :

Please attach your /var/log/Xorg.0.log when booting into a configuration showing the erroneous situation.

Changed in xorg:
status: New → Incomplete
Revision history for this message
Morten (morethan) wrote :

Here is my Xorg.0.log and xorg.conf.

Bryce Harrington (bryce)
Changed in xserver-xorg-input-synaptics:
status: Incomplete → Triaged
Revision history for this message
Morten (morethan) wrote :

Quoting https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/197121/comments/12 :

> Attaching the output/log files mentioned on https://wiki.ubuntu.com/X/Debugging
[...]

(File uploaded in bug #197121 as http://launchpadlibrarian.net/16051924/bug_197121_text_files.tgz )

This bug and bug #197121 are closely related, it appears to be a manifestation of this bug. This bug would be "solved" by the other one, but there's also most likely another bug (IMO), possibly in in nautilus, that causes the disability to click stuff after selecting an area of the desktop with trackpoint + mousepad :)

Revision history for this message
Niels Egberts (nielsegberts) wrote :

I'm still having this exact same issue in a fully updated Intrepid. The problems started in Hardy, but unfortunately its still in intrepid.

Bryce Harrington (bryce)
tags: added: hardy
Revision history for this message
Niels Egberts (nielsegberts) wrote :

I'm not having this issue with Jaunty or the latest Karmic. Mark as fixed?

Revision history for this message
bugbot (bugbot) wrote :

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Triaged → New
status: New → Incomplete
Morten (morethan)
Changed in xserver-xorg-input-synaptics (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.