Mouse cursor flickering and disappearing
I installed Ubuntu today and since the first start up I have a problem with the mouse cursor.
It starts randomly disappearing and flickering a lot.
I have searched for a solution on Google and here but didn't find anything.
cursor
edited May 7 '14 at 6:41
kiri
19.2k1359105
asked Oct 17 '13 at 18:32
user203715user203715
651263
add a comment |
I installed Ubuntu today and since the first start up I have a problem with the mouse cursor.
It starts randomly disappearing and flickering a lot.
I have searched for a solution on Google and here but didn't find anything.
cursor
edited May 7 '14 at 6:41
kiri
19.2k1359105
asked Oct 17 '13 at 18:32
user203715user203715
651263
Welcome! How is your mouse connected (USB maybe)? Try with another mouse device and see what happens. Also you may try plugging into another port
– Lucio
Oct 17 '13 at 19:04
Its happening in 14.04 as well and this trick saved my time.
– Nagendhiran
Apr 13 '14 at 3:33
if you are having flickering in chrome only , try this answer, adding one section to the 20-intel.conf file fixed my issues with flicker in chrome. askubuntu.com/questions/766725/…
– Brandon Søren Culley
May 18 '18 at 15:19
add a comment |
I installed Ubuntu today and since the first start up I have a problem with the mouse cursor.
It starts randomly disappearing and flickering a lot.
I have searched for a solution on Google and here but didn't find anything.
cursor
edited May 7 '14 at 6:41
kiri
19.2k1359105
asked Oct 17 '13 at 18:32
user203715user203715
651263
I installed Ubuntu today and since the first start up I have a problem with the mouse cursor.
It starts randomly disappearing and flickering a lot.
I have searched for a solution on Google and here but didn't find anything.
cursor
cursor
edited May 7 '14 at 6:41
kiri
19.2k1359105
asked Oct 17 '13 at 18:32
user203715user203715
651263
edited May 7 '14 at 6:41
kiri
19.2k1359105
asked Oct 17 '13 at 18:32
user203715user203715
651263
edited May 7 '14 at 6:41
kiri
19.2k1359105
edited May 7 '14 at 6:41
kiri
19.2k1359105
edited May 7 '14 at 6:41
kiri
19.2k1359105
19.2k1359105
asked Oct 17 '13 at 18:32
user203715user203715
651263
asked Oct 17 '13 at 18:32
user203715user203715
651263
asked Oct 17 '13 at 18:32
user203715user203715
651263
651263
Welcome! How is your mouse connected (USB maybe)? Try with another mouse device and see what happens. Also you may try plugging into another port
– Lucio
Oct 17 '13 at 19:04
Its happening in 14.04 as well and this trick saved my time.
– Nagendhiran
Apr 13 '14 at 3:33
if you are having flickering in chrome only , try this answer, adding one section to the 20-intel.conf file fixed my issues with flicker in chrome. askubuntu.com/questions/766725/…
– Brandon Søren Culley
May 18 '18 at 15:19
add a comment |
Welcome! How is your mouse connected (USB maybe)? Try with another mouse device and see what happens. Also you may try plugging into another port
– Lucio
Oct 17 '13 at 19:04
Its happening in 14.04 as well and this trick saved my time.
– Nagendhiran
Apr 13 '14 at 3:33
if you are having flickering in chrome only , try this answer, adding one section to the 20-intel.conf file fixed my issues with flicker in chrome. askubuntu.com/questions/766725/…
– Brandon Søren Culley
May 18 '18 at 15:19
Welcome! How is your mouse connected (USB maybe)? Try with another mouse device and see what happens. Also you may try plugging into another port
– Lucio
Oct 17 '13 at 19:04
Welcome! How is your mouse connected (USB maybe)? Try with another mouse device and see what happens. Also you may try plugging into another port
– Lucio
Oct 17 '13 at 19:04
Its happening in 14.04 as well and this trick saved my time.
– Nagendhiran
Apr 13 '14 at 3:33
Its happening in 14.04 as well and this trick saved my time.
– Nagendhiran
Apr 13 '14 at 3:33
if you are having flickering in chrome only , try this answer, adding one section to the 20-intel.conf file fixed my issues with flicker in chrome. askubuntu.com/questions/766725/…
– Brandon Søren Culley
May 18 '18 at 15:19
if you are having flickering in chrome only , try this answer, adding one section to the 20-intel.conf file fixed my issues with flicker in chrome. askubuntu.com/questions/766725/…
– Brandon Søren Culley
May 18 '18 at 15:19
add a comment |
3 Answers
3
active
oldest
votes
I had the same problem. You can fix it manually.
Open System Settings > Displays.
In the Displays window, you will see an Unknown monitor.
Click it and disable it.
edited Oct 28 '13 at 12:13
Ibungo
23226
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
2
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
8
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
2
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
1
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
|
show 4 more comments
I ran, from within 16.04, the command:
sudo apt-get upgrade
and it seems to have appeased the pointer, so far.
I had instability, especially over the Chrome browser tabs.
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
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.
answered yesterday
intikaintika
25016
add a comment |
protected by Community♦ Oct 19 '13 at 16:16
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had the same problem. You can fix it manually.
Open System Settings > Displays.
In the Displays window, you will see an Unknown monitor.
Click it and disable it.
edited Oct 28 '13 at 12:13
Ibungo
23226
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
2
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
8
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
2
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
1
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
|
show 4 more comments
I had the same problem. You can fix it manually.
Open System Settings > Displays.
In the Displays window, you will see an Unknown monitor.
Click it and disable it.
edited Oct 28 '13 at 12:13
Ibungo
23226
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
2
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
8
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
2
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
1
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
|
show 4 more comments
I had the same problem. You can fix it manually.
Open System Settings > Displays.
In the Displays window, you will see an Unknown monitor.
Click it and disable it.
edited Oct 28 '13 at 12:13
Ibungo
23226
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
I had the same problem. You can fix it manually.
Open System Settings > Displays.
In the Displays window, you will see an Unknown monitor.
Click it and disable it.
edited Oct 28 '13 at 12:13
Ibungo
23226
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
edited Oct 28 '13 at 12:13
Ibungo
23226
edited Oct 28 '13 at 12:13
Ibungo
23226
edited Oct 28 '13 at 12:13
Ibungo
23226
23226
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
answered Oct 17 '13 at 19:51
Anıl KaraağaçAnıl Karaağaç
2,180167
2,180167
2
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
8
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
2
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
1
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
|
show 4 more comments
2
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
8
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
2
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
1
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
2
2
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
And to remove that screen you can follow this: askubuntu.com/a/365017/34385
– Jeggy
Oct 25 '13 at 8:23
8
8
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
Great! How did you figure out??
– sobi3ch
Oct 28 '13 at 11:43
2
2
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
There is no unknown display for me. But I can see 2 built in display in red and green color. I tried disabling one of those alternatively but that also didn't solved my issue. Please help
– Vishal Vijay
Nov 22 '13 at 5:16
1
1
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
Ho sorry... Disabling the green built in display solved the issue. Thanks
– Vishal Vijay
Nov 22 '13 at 5:24
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
This didn't work in my case (I had no "Unknown Monitor"). I have posted a question here but given that the OP is a superset of my question I think this answer should provide other possible solutions (or at least avenues to investigate).
– quant
Nov 23 '14 at 21:09
|
show 4 more comments
I ran, from within 16.04, the command:
sudo apt-get upgrade
and it seems to have appeased the pointer, so far.
I had instability, especially over the Chrome browser tabs.
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
add a comment |
I ran, from within 16.04, the command:
sudo apt-get upgrade
and it seems to have appeased the pointer, so far.
I had instability, especially over the Chrome browser tabs.
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
add a comment |
I ran, from within 16.04, the command:
sudo apt-get upgrade
and it seems to have appeased the pointer, so far.
I had instability, especially over the Chrome browser tabs.
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
I ran, from within 16.04, the command:
sudo apt-get upgrade
and it seems to have appeased the pointer, so far.
I had instability, especially over the Chrome browser tabs.
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
answered Aug 4 '17 at 14:33
Juan LanusJuan Lanus
16115
16115
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.
answered yesterday
intikaintika
25016
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.
answered yesterday
intikaintika
25016
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.
answered yesterday
intikaintika
25016
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 yesterday
intikaintika
25016
edited yesterday
answered yesterday
intikaintika
25016
answered yesterday
intikaintika
25016
answered yesterday
intikaintika
25016
25016
add a comment |
add a comment |
protected by Community♦ Oct 19 '13 at 16:16
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Welcome! How is your mouse connected (USB maybe)? Try with another mouse device and see what happens. Also you may try plugging into another port
– Lucio
Oct 17 '13 at 19:04
Its happening in 14.04 as well and this trick saved my time.
– Nagendhiran
Apr 13 '14 at 3:33
if you are having flickering in chrome only , try this answer, adding one section to the 20-intel.conf file fixed my issues with flicker in chrome. askubuntu.com/questions/766725/…
– Brandon Søren Culley
May 18 '18 at 15:19