CTRL+f shortcut does not work in any application after Oneiric upgrade

ctrl + f

KeyPress event, serial 36, synthetic NO, window 0x4400001,
    root 0xbd, subw 0x0, time 18055956, (983,208), root:(1050,591),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES, ##
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x4400001,
    root 0xbd, subw 0x0, time 18056036, (983,208), root:(1050,591),
    state 0x4, keycode 41 (keysym 0x66, f), same_screen YES, ##
    XLookupString gives 1 bytes: (06) ""
    XmbLookupString gives 1 bytes: (06) ""
    XFilterEvent returns: False

ctrl + t

KeyPress event, serial 36, synthetic NO, window 0x4400001,
    root 0xbd, subw 0x0, time 18127028, (1105,34), root:(1172,417),
    state 0x0, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyPress event, serial 36, synthetic NO, window 0x4400001,
    root 0xbd, subw 0x0, time 18127116, (1105,34), root:(1172,417),
    state 0x4, keycode 28 (keysym 0x74, t), same_screen YES,
    XLookupString gives 1 bytes: (14) ""
    XmbLookupString gives 1 bytes: (14) ""
    XFilterEvent returns: False

Seems that in your the key f is having problems
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

I can independently confirm that after upgrading to Oneiric 11.10, the Ctrl-F shortcut is no longer working in any application. Typing Ctrl-F in Firefox should open the text finder window, but it doesn't anymore.

Weirdly, typing Ctrl-F in Oneiric now opens an X-Terminal. Why? I didn't create that shortcut, and when I look at System Settings / Keyboard / Shortcuts / Launchers and Custom Shortcuts etc, there is no shortcut using Ctrl-F. So, where is it?

I cannot reproduce it on my Oneiric installed from scratch, it works as expected.

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Assign to Xorg for a better triage

As the bug reporter said, this bug exists after upgrading to Oneiric. It does not exist for a fresh installation of Oneiric. I have the bug after upgrading from Maverick via Natty to Oneiric. Anybody should be able to reproduce this. Just do a fresh installation of Maverick, upgrade to Natty, and then upgrade to Oneiric.

When I run gconf-editor, I can see lots of relevant apps such as lightdm, metacity, unity*, etc, but none of these have a Ctrl-F shortcut defined. I cannot find a Ctrl-F shortcut definition anywhere in Oneiric. So, where does it come from? How can we delete it?

Does anybody know how to find out where this Ctrl-F shortcut is being defined in Oneiric?

Hello
Can you confirm when you press 'f' key without Ctrl it appear as 'f' and the bug is showing only in association with Ctrl key?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

1. Pressing 'f' key works ok in any window. It produces an 'f' character. In xev, it produces keysym 0x66 'f'.

2. Pressing 'Ctrl-f' opens an X-Terminal. This happens where ever the pointer is. If the pointer is outside any firefox windows, pressing 'Ctrl-f' still open an xterm. In xev, it produces keysym 0xffe3 Control_L, but when the X-Terminal window opens, the xev window loses the input focus, so it never sees the 'f' key and there is no 'f' keysym event listed.

Something has defined a Ctrl-f shortcut in Unity that works across all applications.

Also, I am using Unity-2D. I can't use Unity-3D or anything else because they are too buggy in Oneiric on this pc. Maybe that makes a difference.

I searched all of the config files in the .gconf and .local directories, but none of them contain a 'Ctrl-f' shortcut definition.

Where else could this shortcut be defined?

Any suggestions?

Just tested in Unity-3D. The bug is there too.

Thats definitely not a Unity bug. I have removed unity from affects

@ Omer Akram

Why? Have you seen this bug before, or do you know what is causing it? Please explain.

No answers? I'm re-adding.

@ Omer

Please would you explain why you think this report is incomplete, and please would you answer my questions above in comment #13?

this bug report is marked incomplete for Unity since unity is not a cause of this bug or neither have any relation to this issue, thats why it was removed as affects for this bug in the first place, since you re-added Unity marking it as incomplete is the only way for it to not appear in the NEW untouched bugs list.

@ Omer

With the greatest respect, you haven't given any reasons why you think it is incomplete or answered my other questions which I asked. Please would you explain why you think this report is incomplete, and please would you answer my questions above in comment #13?

B, the way launchpad handles bugs is that you can add several components to a single bug report. In this bug report unity, unity-2d, lightdm, xorg, firefox and gnome-session are marked as "affects" (scroll to the top of the page). As I am responsible for Unity bugs here I marked the unity task as 'incomplete'(so that this bug is cleared from the list of untouched bugs of Unity) since its totally unrelated to this specific bug report. Other than Unity every other component is have the status NEW, that may change when someone who understands the cause of this bug visits this report. Thanks for understanding.

@ Omer

I'm not sure what you mean by "the unity task". Is that jargon? Do you mean the unity project or something else?

And why do you think "the unity task" is "totally unrelated to this specific bug report"?
Perhaps we are talking at crossed purposes.

It's been more than a week with no reply. It's better to keep this issue open on unity as well.

Closing LightDM task as I see no reason to think this is caused by the display manager.

is that still an issue in precise?

I found the cause of the problem in my case. As part of the Maverick to Natty to Oneiric upgrade, something installed the xbindkeys package (xbindkeys-1.8.5-1). The file ~/.xbindkeysrc has definitions including:

"xterm"
  c:41 + m:0x4

This unfortunately defines a Ctrl-f shortcut which has global scope (i.e. cuts across all applications) that starts an xterm.
I uninstalled xbindkeys, and of course its global Ctrl-f shortcut is now gone, thus enabling all of the application-specific Ctrl-f shortcuts, such as Ctrl-f for opening the search box in firefox, to work again.

I'm not sure why xbindkeys was installed during the Maverick-Natty-Oneiric upgrade. Anyway, I hope this bug report will help others who may encounter the same issue.

@Karl Ostmo, is xbindkeys installed on your system?

Status changed to 'Confirmed' because the bug affects multiple users.

Karl Ostmo, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p xorg <replace-with-bug-number>

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

I've since done a clean install of Xubuntu 13.10, and this issue is not present.

Karl Ostmo, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/880517/comments/26 regarding this being fixed with a fresh install of Saucy. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.