Gnome - Cannot click between windows or click on UI elements with Mad Catz R.A.T. 3 mouse
I recently switched to Linux. Everything went fine, but when I installed the gnome-shell, it started to ignore clicks outside the focused window. I cannot click on another window to focus it or click on any gnome UI elements. The super key also does nothing. I installed gnome-tweaks and I use a user theme, but that shouldn't be the problem because the problem remained even when I had a fresh install. Also, sometimes when I reboot it works normally. But after another reboot, it comes back.
PS- I found a very temporary fix: If I move the focused (or sometimes other windows) it will start recognizing my keystrokes. On Firefox I need to move the window by the bar with open tabs, as I cannot move it with the title bar.
I read this thread by someone who had a very similar issue, but the solution did not work for me. I think it has to do something with NVidia drivers, because if I change them then the frequency of this happening changes.
Sorry if something is weirdly written. English is not my native language.
18.04 nvidia keyboard mouse gnome-shell
edited Feb 2 at 22:43
pomsky
32.2k11100131
asked Feb 2 at 15:11
bainbain
287
add a comment |
I recently switched to Linux. Everything went fine, but when I installed the gnome-shell, it started to ignore clicks outside the focused window. I cannot click on another window to focus it or click on any gnome UI elements. The super key also does nothing. I installed gnome-tweaks and I use a user theme, but that shouldn't be the problem because the problem remained even when I had a fresh install. Also, sometimes when I reboot it works normally. But after another reboot, it comes back.
PS- I found a very temporary fix: If I move the focused (or sometimes other windows) it will start recognizing my keystrokes. On Firefox I need to move the window by the bar with open tabs, as I cannot move it with the title bar.
I read this thread by someone who had a very similar issue, but the solution did not work for me. I think it has to do something with NVidia drivers, because if I change them then the frequency of this happening changes.
Sorry if something is weirdly written. English is not my native language.
18.04 nvidia keyboard mouse gnome-shell
edited Feb 2 at 22:43
pomsky
32.2k11100131
asked Feb 2 at 15:11
bainbain
287
Hi, welcome to Linux! English shouldn't be a barrier in the way of solution as long as you can adequately explain your troubles. Cheerios! :) PS - Windows key is supposedly refered to as the Super Key.
– thephoenix01
Feb 2 at 15:52
Thanks, I approved the edit. And changed the 'windows key' to super key.
– bain
Feb 2 at 16:07
Did you try all the answers posted to the question you mentioned? For example are you in a Wayland session? What is the output of the following command in Terminal:echo $XDG_SESSION_TYPE?
– pomsky
Feb 2 at 16:24
@pomsky The output of the command is x11. So I'm not in a Wayland session. I guess? EDIT 1 and 2: I'm dumb
– bain
Feb 2 at 16:30
Also, yes I did try all the answers. The second one even booted me to a black screen.
– bain
Feb 2 at 16:55
add a comment |
I recently switched to Linux. Everything went fine, but when I installed the gnome-shell, it started to ignore clicks outside the focused window. I cannot click on another window to focus it or click on any gnome UI elements. The super key also does nothing. I installed gnome-tweaks and I use a user theme, but that shouldn't be the problem because the problem remained even when I had a fresh install. Also, sometimes when I reboot it works normally. But after another reboot, it comes back.
PS- I found a very temporary fix: If I move the focused (or sometimes other windows) it will start recognizing my keystrokes. On Firefox I need to move the window by the bar with open tabs, as I cannot move it with the title bar.
I read this thread by someone who had a very similar issue, but the solution did not work for me. I think it has to do something with NVidia drivers, because if I change them then the frequency of this happening changes.
Sorry if something is weirdly written. English is not my native language.
18.04 nvidia keyboard mouse gnome-shell
edited Feb 2 at 22:43
pomsky
32.2k11100131
asked Feb 2 at 15:11
bainbain
287
I recently switched to Linux. Everything went fine, but when I installed the gnome-shell, it started to ignore clicks outside the focused window. I cannot click on another window to focus it or click on any gnome UI elements. The super key also does nothing. I installed gnome-tweaks and I use a user theme, but that shouldn't be the problem because the problem remained even when I had a fresh install. Also, sometimes when I reboot it works normally. But after another reboot, it comes back.
PS- I found a very temporary fix: If I move the focused (or sometimes other windows) it will start recognizing my keystrokes. On Firefox I need to move the window by the bar with open tabs, as I cannot move it with the title bar.
I read this thread by someone who had a very similar issue, but the solution did not work for me. I think it has to do something with NVidia drivers, because if I change them then the frequency of this happening changes.
Sorry if something is weirdly written. English is not my native language.
18.04 nvidia keyboard mouse gnome-shell
18.04 nvidia keyboard mouse gnome-shell
edited Feb 2 at 22:43
pomsky
32.2k11100131
asked Feb 2 at 15:11
bainbain
287
edited Feb 2 at 22:43
pomsky
32.2k11100131
asked Feb 2 at 15:11
bainbain
287
edited Feb 2 at 22:43
pomsky
32.2k11100131
edited Feb 2 at 22:43
pomsky
32.2k11100131
edited Feb 2 at 22:43
pomsky
32.2k11100131
32.2k11100131
asked Feb 2 at 15:11
bainbain
287
asked Feb 2 at 15:11
bainbain
287
asked Feb 2 at 15:11
bainbain
287
287
Hi, welcome to Linux! English shouldn't be a barrier in the way of solution as long as you can adequately explain your troubles. Cheerios! :) PS - Windows key is supposedly refered to as the Super Key.
– thephoenix01
Feb 2 at 15:52
Thanks, I approved the edit. And changed the 'windows key' to super key.
– bain
Feb 2 at 16:07
Did you try all the answers posted to the question you mentioned? For example are you in a Wayland session? What is the output of the following command in Terminal:echo $XDG_SESSION_TYPE?
– pomsky
Feb 2 at 16:24
@pomsky The output of the command is x11. So I'm not in a Wayland session. I guess? EDIT 1 and 2: I'm dumb
– bain
Feb 2 at 16:30
Also, yes I did try all the answers. The second one even booted me to a black screen.
– bain
Feb 2 at 16:55
add a comment |
Hi, welcome to Linux! English shouldn't be a barrier in the way of solution as long as you can adequately explain your troubles. Cheerios! :) PS - Windows key is supposedly refered to as the Super Key.
– thephoenix01
Feb 2 at 15:52
Thanks, I approved the edit. And changed the 'windows key' to super key.
– bain
Feb 2 at 16:07
Did you try all the answers posted to the question you mentioned? For example are you in a Wayland session? What is the output of the following command in Terminal:echo $XDG_SESSION_TYPE?
– pomsky
Feb 2 at 16:24
@pomsky The output of the command is x11. So I'm not in a Wayland session. I guess? EDIT 1 and 2: I'm dumb
– bain
Feb 2 at 16:30
Also, yes I did try all the answers. The second one even booted me to a black screen.
– bain
Feb 2 at 16:55
Hi, welcome to Linux! English shouldn't be a barrier in the way of solution as long as you can adequately explain your troubles. Cheerios! :) PS - Windows key is supposedly refered to as the Super Key.
– thephoenix01
Feb 2 at 15:52
Hi, welcome to Linux! English shouldn't be a barrier in the way of solution as long as you can adequately explain your troubles. Cheerios! :) PS - Windows key is supposedly refered to as the Super Key.
– thephoenix01
Feb 2 at 15:52
Thanks, I approved the edit. And changed the 'windows key' to super key.
– bain
Feb 2 at 16:07
Thanks, I approved the edit. And changed the 'windows key' to super key.
– bain
Feb 2 at 16:07
Did you try all the answers posted to the question you mentioned? For example are you in a Wayland session? What is the output of the following command in Terminal:
echo $XDG_SESSION_TYPE?– pomsky
Feb 2 at 16:24
Did you try all the answers posted to the question you mentioned? For example are you in a Wayland session? What is the output of the following command in Terminal:
echo $XDG_SESSION_TYPE?– pomsky
Feb 2 at 16:24
@pomsky The output of the command is x11. So I'm not in a Wayland session. I guess? EDIT 1 and 2: I'm dumb
– bain
Feb 2 at 16:30
@pomsky The output of the command is x11. So I'm not in a Wayland session. I guess? EDIT 1 and 2: I'm dumb
– bain
Feb 2 at 16:30
Also, yes I did try all the answers. The second one even booted me to a black screen.
– bain
Feb 2 at 16:55
Also, yes I did try all the answers. The second one even booted me to a black screen.
– bain
Feb 2 at 16:55
add a comment |
1 Answer
1
active
oldest
votes
So after doing some more research, I stumbled upon a thread with the same question. It turned out to be a problem with my Mad Catz R.A.T. 3 mouse. I didn't realise that i didn't have any drivers for it. Here's how you can fix this issue.
Write this section to /etc/X11/xorg.conf:
Section "InputClass" Identifier "Mouse Remap"
MatchProduct "Madcatz Mad Catz R.A.T.3 Mouse"
MatchDevicePath "/dev/input/event*"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 0 0 0"
EndSection
PS: Here's a link to ArchWiki. It has all the information you need to set up your mad catz mouse.
answered Feb 2 at 19:12
bainbain
287
1
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115001%2fgnome-cannot-click-between-windows-or-click-on-ui-elements-with-mad-catz-r-a-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So after doing some more research, I stumbled upon a thread with the same question. It turned out to be a problem with my Mad Catz R.A.T. 3 mouse. I didn't realise that i didn't have any drivers for it. Here's how you can fix this issue.
Write this section to /etc/X11/xorg.conf:
Section "InputClass" Identifier "Mouse Remap"
MatchProduct "Madcatz Mad Catz R.A.T.3 Mouse"
MatchDevicePath "/dev/input/event*"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 0 0 0"
EndSection
PS: Here's a link to ArchWiki. It has all the information you need to set up your mad catz mouse.
answered Feb 2 at 19:12
bainbain
287
1
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
add a comment |
So after doing some more research, I stumbled upon a thread with the same question. It turned out to be a problem with my Mad Catz R.A.T. 3 mouse. I didn't realise that i didn't have any drivers for it. Here's how you can fix this issue.
Write this section to /etc/X11/xorg.conf:
Section "InputClass" Identifier "Mouse Remap"
MatchProduct "Madcatz Mad Catz R.A.T.3 Mouse"
MatchDevicePath "/dev/input/event*"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 0 0 0"
EndSection
PS: Here's a link to ArchWiki. It has all the information you need to set up your mad catz mouse.
answered Feb 2 at 19:12
bainbain
287
1
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
add a comment |
So after doing some more research, I stumbled upon a thread with the same question. It turned out to be a problem with my Mad Catz R.A.T. 3 mouse. I didn't realise that i didn't have any drivers for it. Here's how you can fix this issue.
Write this section to /etc/X11/xorg.conf:
Section "InputClass" Identifier "Mouse Remap"
MatchProduct "Madcatz Mad Catz R.A.T.3 Mouse"
MatchDevicePath "/dev/input/event*"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 0 0 0"
EndSection
PS: Here's a link to ArchWiki. It has all the information you need to set up your mad catz mouse.
answered Feb 2 at 19:12
bainbain
287
So after doing some more research, I stumbled upon a thread with the same question. It turned out to be a problem with my Mad Catz R.A.T. 3 mouse. I didn't realise that i didn't have any drivers for it. Here's how you can fix this issue.
Write this section to /etc/X11/xorg.conf:
Section "InputClass" Identifier "Mouse Remap"
MatchProduct "Madcatz Mad Catz R.A.T.3 Mouse"
MatchDevicePath "/dev/input/event*"
Option "ButtonMapping" "1 2 3 4 5 6 7 8 0 0 0 0 0 0 0 0 0 0 0"
EndSection
PS: Here's a link to ArchWiki. It has all the information you need to set up your mad catz mouse.
answered Feb 2 at 19:12
bainbain
287
edited Feb 3 at 16:24
answered Feb 2 at 19:12
bainbain
287
answered Feb 2 at 19:12
bainbain
287
answered Feb 2 at 19:12
bainbain
287
287
1
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
add a comment |
1
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
1
1
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
Please do not delete your question! Links to outside website may not work in the future, and you have attributed your answer to these outside sources and included the relevant bits to the answer that you have provided.
– Charles Green
Feb 3 at 14:28
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1115001%2fgnome-cannot-click-between-windows-or-click-on-ui-elements-with-mad-catz-r-a-t%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hi, welcome to Linux! English shouldn't be a barrier in the way of solution as long as you can adequately explain your troubles. Cheerios! :) PS - Windows key is supposedly refered to as the Super Key.
– thephoenix01
Feb 2 at 15:52
Thanks, I approved the edit. And changed the 'windows key' to super key.
– bain
Feb 2 at 16:07
Did you try all the answers posted to the question you mentioned? For example are you in a Wayland session? What is the output of the following command in Terminal:
echo $XDG_SESSION_TYPE?– pomsky
Feb 2 at 16:24
@pomsky The output of the command is x11. So I'm not in a Wayland session. I guess? EDIT 1 and 2: I'm dumb
– bain
Feb 2 at 16:30
Also, yes I did try all the answers. The second one even booted me to a black screen.
– bain
Feb 2 at 16:55