search function (ctrl+f) randomly launching

[mxyzptlk]

After a recent update, the search function (ctrl+f) has started to launch itself at random. It does this in a number of applications -- Nautilus, Chromium, and Liferea have been observed.

The one thing that has accompanied this is mouse scrolling within Nautilus stopped working right around the same time. The scroll bar can still be grabbed and used, but edge scrolling and two-finger scrolling ceased to work in Nautilus at the same time the search function began to randomly launch itself. However, edge scrolling and two-finger scrolling continues to work in other applications -- it's only an issue with Nautilus.

I know that sounds like two separate issues, but since they began at the same time (and I've never experienced either before), I'm guessing they're related.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1010033/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[mxyzptlk (mxyzptlk)]

Two updates:

1.) I've submitted a separate bug for the Nautilus scrolling issue, just in case (Bug #1010120)

2.) I've tried using both Unity and Gnome environments, with the same results (search randomly launching itself)

[mxyzptlk (mxyzptlk)]

I've isolated something: This seems to happen after coming out of a blank screen. In fact it immediately happens on whatever application is up front as soon as I reactivate the screen.