Mouse is flickering in new debian install
Clash Royale CLAN TAG#URR8PPP
I initially thought this might be a display driver issue but after installing the proprietary ATI drivers and now the free ones I am still getting it.
My mouse disappears when I scroll or write sometimes (but not always). It also flickers when I move, especially when I am in the system settings
menu hovering over icons (it is only visible when I move the mouse, and even then it flickers a lot).
I did a search and this seems to be a common problem. This post for ubuntu suggests removing an unknown monitor, but I only have 1 monitor that I can't remove. This post suggests the problem is unclutter
, which I don't have installed. Besides, the mouse disappearing doesn't seem to be time-related.
Any suggestions? I'm new to linux so I don't know what information I should be providing about my system. I'm running Debian Wheezy with a USB mouse. I have tried attaching it to the PC's usb port as well as a USB hub, without any change. It's a fresh install and this problem has existed since the first boot.
debian drivers
add a comment |
I initially thought this might be a display driver issue but after installing the proprietary ATI drivers and now the free ones I am still getting it.
My mouse disappears when I scroll or write sometimes (but not always). It also flickers when I move, especially when I am in the system settings
menu hovering over icons (it is only visible when I move the mouse, and even then it flickers a lot).
I did a search and this seems to be a common problem. This post for ubuntu suggests removing an unknown monitor, but I only have 1 monitor that I can't remove. This post suggests the problem is unclutter
, which I don't have installed. Besides, the mouse disappearing doesn't seem to be time-related.
Any suggestions? I'm new to linux so I don't know what information I should be providing about my system. I'm running Debian Wheezy with a USB mouse. I have tried attaching it to the PC's usb port as well as a USB hub, without any change. It's a fresh install and this problem has existed since the first boot.
debian drivers
Does it happen with a different mouse? Is this a desktop? If not, does it happen with the touchpad? Which desktop environment are you using? Does it happen in others?
– terdon♦
Apr 19 '14 at 12:47
@terdon 64-bit PC. Tried a different mouse, same thing. I'm using Gnome classic. Tried logging into "Gnome" which looks the same (!?) and same problem. One interesting observation is that it doesn't occur when I first log in, only once I open up system settings or a browser, then it flickers even if I click around in the desktop menus (on first log in it doesn't flicker when I click on those menus).
– quant
Apr 19 '14 at 12:57
@terdon just installed those proprietary drivers again as per the suggestions from my other question and it seems to be working now..
– quant
Apr 19 '14 at 13:40
add a comment |
I initially thought this might be a display driver issue but after installing the proprietary ATI drivers and now the free ones I am still getting it.
My mouse disappears when I scroll or write sometimes (but not always). It also flickers when I move, especially when I am in the system settings
menu hovering over icons (it is only visible when I move the mouse, and even then it flickers a lot).
I did a search and this seems to be a common problem. This post for ubuntu suggests removing an unknown monitor, but I only have 1 monitor that I can't remove. This post suggests the problem is unclutter
, which I don't have installed. Besides, the mouse disappearing doesn't seem to be time-related.
Any suggestions? I'm new to linux so I don't know what information I should be providing about my system. I'm running Debian Wheezy with a USB mouse. I have tried attaching it to the PC's usb port as well as a USB hub, without any change. It's a fresh install and this problem has existed since the first boot.
debian drivers
I initially thought this might be a display driver issue but after installing the proprietary ATI drivers and now the free ones I am still getting it.
My mouse disappears when I scroll or write sometimes (but not always). It also flickers when I move, especially when I am in the system settings
menu hovering over icons (it is only visible when I move the mouse, and even then it flickers a lot).
I did a search and this seems to be a common problem. This post for ubuntu suggests removing an unknown monitor, but I only have 1 monitor that I can't remove. This post suggests the problem is unclutter
, which I don't have installed. Besides, the mouse disappearing doesn't seem to be time-related.
Any suggestions? I'm new to linux so I don't know what information I should be providing about my system. I'm running Debian Wheezy with a USB mouse. I have tried attaching it to the PC's usb port as well as a USB hub, without any change. It's a fresh install and this problem has existed since the first boot.
debian drivers
debian drivers
edited Apr 13 '17 at 12:22
Community♦
1
1
asked Apr 19 '14 at 12:43
quantquant
1,56372042
1,56372042
Does it happen with a different mouse? Is this a desktop? If not, does it happen with the touchpad? Which desktop environment are you using? Does it happen in others?
– terdon♦
Apr 19 '14 at 12:47
@terdon 64-bit PC. Tried a different mouse, same thing. I'm using Gnome classic. Tried logging into "Gnome" which looks the same (!?) and same problem. One interesting observation is that it doesn't occur when I first log in, only once I open up system settings or a browser, then it flickers even if I click around in the desktop menus (on first log in it doesn't flicker when I click on those menus).
– quant
Apr 19 '14 at 12:57
@terdon just installed those proprietary drivers again as per the suggestions from my other question and it seems to be working now..
– quant
Apr 19 '14 at 13:40
add a comment |
Does it happen with a different mouse? Is this a desktop? If not, does it happen with the touchpad? Which desktop environment are you using? Does it happen in others?
– terdon♦
Apr 19 '14 at 12:47
@terdon 64-bit PC. Tried a different mouse, same thing. I'm using Gnome classic. Tried logging into "Gnome" which looks the same (!?) and same problem. One interesting observation is that it doesn't occur when I first log in, only once I open up system settings or a browser, then it flickers even if I click around in the desktop menus (on first log in it doesn't flicker when I click on those menus).
– quant
Apr 19 '14 at 12:57
@terdon just installed those proprietary drivers again as per the suggestions from my other question and it seems to be working now..
– quant
Apr 19 '14 at 13:40
Does it happen with a different mouse? Is this a desktop? If not, does it happen with the touchpad? Which desktop environment are you using? Does it happen in others?
– terdon♦
Apr 19 '14 at 12:47
Does it happen with a different mouse? Is this a desktop? If not, does it happen with the touchpad? Which desktop environment are you using? Does it happen in others?
– terdon♦
Apr 19 '14 at 12:47
@terdon 64-bit PC. Tried a different mouse, same thing. I'm using Gnome classic. Tried logging into "Gnome" which looks the same (!?) and same problem. One interesting observation is that it doesn't occur when I first log in, only once I open up system settings or a browser, then it flickers even if I click around in the desktop menus (on first log in it doesn't flicker when I click on those menus).
– quant
Apr 19 '14 at 12:57
@terdon 64-bit PC. Tried a different mouse, same thing. I'm using Gnome classic. Tried logging into "Gnome" which looks the same (!?) and same problem. One interesting observation is that it doesn't occur when I first log in, only once I open up system settings or a browser, then it flickers even if I click around in the desktop menus (on first log in it doesn't flicker when I click on those menus).
– quant
Apr 19 '14 at 12:57
@terdon just installed those proprietary drivers again as per the suggestions from my other question and it seems to be working now..
– quant
Apr 19 '14 at 13:40
@terdon just installed those proprietary drivers again as per the suggestions from my other question and it seems to be working now..
– quant
Apr 19 '14 at 13:40
add a comment |
2 Answers
2
active
oldest
votes
Installing the proprietary ATI drivers again seems to have fixed it...
add a comment |
Possible cause 1:
Screen settings: resolution and refresh rate.
Can be checked (On KDE) under systemsettings5
then display and monitor
Possible cause 2:
Screen compositor: it could be caused by the sale-method/rendering-backend/tearing-prevention those settings can be changed (On KDE) under systemsettings5
, display and monitor
then compositor
... apply new settings and compare
Possible cause 3:
Display server mis-configuration: you can regenerate the display server config file with X -configure
or similar but first make a copy of /etc/X11
Possible cause 4:
System failure, crash, reboot: on system failure especially for systems equipped with SSD you may loose important files; Files under directories like /home/user/
, /etc/
or /usr/
can cause serious damages, as these directories contain important settings/packages files for different aspect of the desktop. usually when a file is lost after a crash, the file may be completely deleted or zeroed, you can then search for file with zero size and check out if important file are corrupted with the command find /etc -size 0 -print
(this is for /etc) you can also check packages integrity for missing/modified file, on rpm based system it's done with the command rpm -Va
you would then reinstall the broken package.
A common situation in this case is loosing the file /etc/X11/xorg.conf
or one of the config file under /etc/X11/
responsible for the display server; If recovering the file is not possible the config can be regenerated with X -configure
or similar command
Possible cause 5:
Mis-configuration of user files under /home/user
... you can verify this by login with an other user... to fix it eventually delete and recreate the user (after backup)
Possible cause 7:
Graphic drivers, you need to check if you are using the proper graphic driver and or try a different version of the used driver, usually this often happen with nvidia graphical cards.
Other...
The listed situations are not the only possibilities of failure.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f125538%2fmouse-is-flickering-in-new-debian-install%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Installing the proprietary ATI drivers again seems to have fixed it...
add a comment |
Installing the proprietary ATI drivers again seems to have fixed it...
add a comment |
Installing the proprietary ATI drivers again seems to have fixed it...
Installing the proprietary ATI drivers again seems to have fixed it...
answered Apr 19 '14 at 13:40
quantquant
1,56372042
1,56372042
add a comment |
add a comment |
Possible cause 1:
Screen settings: resolution and refresh rate.
Can be checked (On KDE) under systemsettings5
then display and monitor
Possible cause 2:
Screen compositor: it could be caused by the sale-method/rendering-backend/tearing-prevention those settings can be changed (On KDE) under systemsettings5
, display and monitor
then compositor
... apply new settings and compare
Possible cause 3:
Display server mis-configuration: you can regenerate the display server config file with X -configure
or similar but first make a copy of /etc/X11
Possible cause 4:
System failure, crash, reboot: on system failure especially for systems equipped with SSD you may loose important files; Files under directories like /home/user/
, /etc/
or /usr/
can cause serious damages, as these directories contain important settings/packages files for different aspect of the desktop. usually when a file is lost after a crash, the file may be completely deleted or zeroed, you can then search for file with zero size and check out if important file are corrupted with the command find /etc -size 0 -print
(this is for /etc) you can also check packages integrity for missing/modified file, on rpm based system it's done with the command rpm -Va
you would then reinstall the broken package.
A common situation in this case is loosing the file /etc/X11/xorg.conf
or one of the config file under /etc/X11/
responsible for the display server; If recovering the file is not possible the config can be regenerated with X -configure
or similar command
Possible cause 5:
Mis-configuration of user files under /home/user
... you can verify this by login with an other user... to fix it eventually delete and recreate the user (after backup)
Possible cause 7:
Graphic drivers, you need to check if you are using the proper graphic driver and or try a different version of the used driver, usually this often happen with nvidia graphical cards.
Other...
The listed situations are not the only possibilities of failure.
add a comment |
Possible cause 1:
Screen settings: resolution and refresh rate.
Can be checked (On KDE) under systemsettings5
then display and monitor
Possible cause 2:
Screen compositor: it could be caused by the sale-method/rendering-backend/tearing-prevention those settings can be changed (On KDE) under systemsettings5
, display and monitor
then compositor
... apply new settings and compare
Possible cause 3:
Display server mis-configuration: you can regenerate the display server config file with X -configure
or similar but first make a copy of /etc/X11
Possible cause 4:
System failure, crash, reboot: on system failure especially for systems equipped with SSD you may loose important files; Files under directories like /home/user/
, /etc/
or /usr/
can cause serious damages, as these directories contain important settings/packages files for different aspect of the desktop. usually when a file is lost after a crash, the file may be completely deleted or zeroed, you can then search for file with zero size and check out if important file are corrupted with the command find /etc -size 0 -print
(this is for /etc) you can also check packages integrity for missing/modified file, on rpm based system it's done with the command rpm -Va
you would then reinstall the broken package.
A common situation in this case is loosing the file /etc/X11/xorg.conf
or one of the config file under /etc/X11/
responsible for the display server; If recovering the file is not possible the config can be regenerated with X -configure
or similar command
Possible cause 5:
Mis-configuration of user files under /home/user
... you can verify this by login with an other user... to fix it eventually delete and recreate the user (after backup)
Possible cause 7:
Graphic drivers, you need to check if you are using the proper graphic driver and or try a different version of the used driver, usually this often happen with nvidia graphical cards.
Other...
The listed situations are not the only possibilities of failure.
add a comment |
Possible cause 1:
Screen settings: resolution and refresh rate.
Can be checked (On KDE) under systemsettings5
then display and monitor
Possible cause 2:
Screen compositor: it could be caused by the sale-method/rendering-backend/tearing-prevention those settings can be changed (On KDE) under systemsettings5
, display and monitor
then compositor
... apply new settings and compare
Possible cause 3:
Display server mis-configuration: you can regenerate the display server config file with X -configure
or similar but first make a copy of /etc/X11
Possible cause 4:
System failure, crash, reboot: on system failure especially for systems equipped with SSD you may loose important files; Files under directories like /home/user/
, /etc/
or /usr/
can cause serious damages, as these directories contain important settings/packages files for different aspect of the desktop. usually when a file is lost after a crash, the file may be completely deleted or zeroed, you can then search for file with zero size and check out if important file are corrupted with the command find /etc -size 0 -print
(this is for /etc) you can also check packages integrity for missing/modified file, on rpm based system it's done with the command rpm -Va
you would then reinstall the broken package.
A common situation in this case is loosing the file /etc/X11/xorg.conf
or one of the config file under /etc/X11/
responsible for the display server; If recovering the file is not possible the config can be regenerated with X -configure
or similar command
Possible cause 5:
Mis-configuration of user files under /home/user
... you can verify this by login with an other user... to fix it eventually delete and recreate the user (after backup)
Possible cause 7:
Graphic drivers, you need to check if you are using the proper graphic driver and or try a different version of the used driver, usually this often happen with nvidia graphical cards.
Other...
The listed situations are not the only possibilities of failure.
Possible cause 1:
Screen settings: resolution and refresh rate.
Can be checked (On KDE) under systemsettings5
then display and monitor
Possible cause 2:
Screen compositor: it could be caused by the sale-method/rendering-backend/tearing-prevention those settings can be changed (On KDE) under systemsettings5
, display and monitor
then compositor
... apply new settings and compare
Possible cause 3:
Display server mis-configuration: you can regenerate the display server config file with X -configure
or similar but first make a copy of /etc/X11
Possible cause 4:
System failure, crash, reboot: on system failure especially for systems equipped with SSD you may loose important files; Files under directories like /home/user/
, /etc/
or /usr/
can cause serious damages, as these directories contain important settings/packages files for different aspect of the desktop. usually when a file is lost after a crash, the file may be completely deleted or zeroed, you can then search for file with zero size and check out if important file are corrupted with the command find /etc -size 0 -print
(this is for /etc) you can also check packages integrity for missing/modified file, on rpm based system it's done with the command rpm -Va
you would then reinstall the broken package.
A common situation in this case is loosing the file /etc/X11/xorg.conf
or one of the config file under /etc/X11/
responsible for the display server; If recovering the file is not possible the config can be regenerated with X -configure
or similar command
Possible cause 5:
Mis-configuration of user files under /home/user
... you can verify this by login with an other user... to fix it eventually delete and recreate the user (after backup)
Possible cause 7:
Graphic drivers, you need to check if you are using the proper graphic driver and or try a different version of the used driver, usually this often happen with nvidia graphical cards.
Other...
The listed situations are not the only possibilities of failure.
answered Mar 6 at 15:12
intikaintika
26015
26015
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f125538%2fmouse-is-flickering-in-new-debian-install%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
Does it happen with a different mouse? Is this a desktop? If not, does it happen with the touchpad? Which desktop environment are you using? Does it happen in others?
– terdon♦
Apr 19 '14 at 12:47
@terdon 64-bit PC. Tried a different mouse, same thing. I'm using Gnome classic. Tried logging into "Gnome" which looks the same (!?) and same problem. One interesting observation is that it doesn't occur when I first log in, only once I open up system settings or a browser, then it flickers even if I click around in the desktop menus (on first log in it doesn't flicker when I click on those menus).
– quant
Apr 19 '14 at 12:57
@terdon just installed those proprietary drivers again as per the suggestions from my other question and it seems to be working now..
– quant
Apr 19 '14 at 13:40