Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Logitech "back" button no longer works after 6.0.2 update

  • 2 件の返信
  • 34 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: TedM

more options

The navigation buttons (back and forward) on my Logitech mouse have worked correctly in every version of Firefox I've used, including 6.0.1. I just updated to 6.0.1, and the buttons no longer work. I have tried Opera and Internet Explorer, and confirmed that the buttons work correctly with those browsers.

The navigation buttons (back and forward) on my Logitech mouse have worked correctly in every version of Firefox I've used, including 6.0.1. I just updated to 6.0.1, and the buttons no longer work. I have tried Opera and Internet Explorer, and confirmed that the buttons work correctly with those browsers.

選ばれた解決策

Hmm...

I had this issue on 6.0.1.

And then I decided, since I already have the problem, I'll just update to 6.0.2, and see if it works.

Same problem.

And then by some powers-that-be, the problem fixed itself.

(nobody but me uses my computer, so I have absolutely no idea what I did to fix it. Possibly from restarting the computer).

この回答をすべて読む 👍 0

すべての返信 (2)

more options

選ばれた解決策

Hmm...

I had this issue on 6.0.1.

And then I decided, since I already have the problem, I'll just update to 6.0.2, and see if it works.

Same problem.

And then by some powers-that-be, the problem fixed itself.

(nobody but me uses my computer, so I have absolutely no idea what I did to fix it. Possibly from restarting the computer).

more options

The same powers-that-be fixed the problem for me. It's even more mysterious, since I know I did not restart the computer. I was just surfing along, laboriously using the browser's navigation buttons, when out of habit I pressed the button on the mouse and it worked. It's been working ever since.

Since I notice that 23 other people have this problem (so far), there's clearly something that needs looking at even if the problem somehow corrects itself.