Some icons and text randomly become invisible after waking up from sleep (Ubuntu GNOME)
Icons and application indicators in the dropdown settings sometimes disappear.
This happens after waking up from sleep, and can be fixed until waking up from sleep again by pressing Alt+F2 and typing r.
Does anyone know how to permanently fix this?
Ubuntu 16.04
gnome 3.18.4
gnome suspend icons 16.04
edited Jan 29 at 7:26
karel
60k13129153
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
add a comment |
Icons and application indicators in the dropdown settings sometimes disappear.
This happens after waking up from sleep, and can be fixed until waking up from sleep again by pressing Alt+F2 and typing r.
Does anyone know how to permanently fix this?
Ubuntu 16.04
gnome 3.18.4
gnome suspend icons 16.04
edited Jan 29 at 7:26
karel
60k13129153
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
3
I'm having the same problem.
– Anmol Singh Jaggi
May 14 '16 at 11:21
What is your graphics hardware and driver? Same thing here on a Intel GMA 4500MHD (in GS45 chipset), for me a new problem since Ubuntu 16.04.
– tanius
Aug 20 '16 at 18:50
I havn't installed any drivers, but my processor is an intel i3 4005u.
– smurfendrek123
Aug 21 '16 at 19:53
I will say that i've never had this problem since switching to fedora.
– smurfendrek123
Feb 2 at 9:06
add a comment |
Icons and application indicators in the dropdown settings sometimes disappear.
This happens after waking up from sleep, and can be fixed until waking up from sleep again by pressing Alt+F2 and typing r.
Does anyone know how to permanently fix this?
Ubuntu 16.04
gnome 3.18.4
gnome suspend icons 16.04
edited Jan 29 at 7:26
karel
60k13129153
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
Icons and application indicators in the dropdown settings sometimes disappear.
This happens after waking up from sleep, and can be fixed until waking up from sleep again by pressing Alt+F2 and typing r.
Does anyone know how to permanently fix this?
Ubuntu 16.04
gnome 3.18.4
gnome suspend icons 16.04
gnome suspend icons 16.04
edited Jan 29 at 7:26
karel
60k13129153
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
edited Jan 29 at 7:26
karel
60k13129153
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
edited Jan 29 at 7:26
karel
60k13129153
edited Jan 29 at 7:26
karel
60k13129153
edited Jan 29 at 7:26
karel
60k13129153
60k13129153
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
asked Apr 28 '16 at 14:40
smurfendrek123smurfendrek123
349313
349313
3
I'm having the same problem.
– Anmol Singh Jaggi
May 14 '16 at 11:21
What is your graphics hardware and driver? Same thing here on a Intel GMA 4500MHD (in GS45 chipset), for me a new problem since Ubuntu 16.04.
– tanius
Aug 20 '16 at 18:50
I havn't installed any drivers, but my processor is an intel i3 4005u.
– smurfendrek123
Aug 21 '16 at 19:53
I will say that i've never had this problem since switching to fedora.
– smurfendrek123
Feb 2 at 9:06
add a comment |
3
I'm having the same problem.
– Anmol Singh Jaggi
May 14 '16 at 11:21
What is your graphics hardware and driver? Same thing here on a Intel GMA 4500MHD (in GS45 chipset), for me a new problem since Ubuntu 16.04.
– tanius
Aug 20 '16 at 18:50
I havn't installed any drivers, but my processor is an intel i3 4005u.
– smurfendrek123
Aug 21 '16 at 19:53
I will say that i've never had this problem since switching to fedora.
– smurfendrek123
Feb 2 at 9:06
3
3
I'm having the same problem.
– Anmol Singh Jaggi
May 14 '16 at 11:21
I'm having the same problem.
– Anmol Singh Jaggi
May 14 '16 at 11:21
What is your graphics hardware and driver? Same thing here on a Intel GMA 4500MHD (in GS45 chipset), for me a new problem since Ubuntu 16.04.
– tanius
Aug 20 '16 at 18:50
What is your graphics hardware and driver? Same thing here on a Intel GMA 4500MHD (in GS45 chipset), for me a new problem since Ubuntu 16.04.
– tanius
Aug 20 '16 at 18:50
I havn't installed any drivers, but my processor is an intel i3 4005u.
– smurfendrek123
Aug 21 '16 at 19:53
I havn't installed any drivers, but my processor is an intel i3 4005u.
– smurfendrek123
Aug 21 '16 at 19:53
I will say that i've never had this problem since switching to fedora.
– smurfendrek123
Feb 2 at 9:06
I will say that i've never had this problem since switching to fedora.
– smurfendrek123
Feb 2 at 9:06
add a comment |
3 Answers
3
active
oldest
votes
This seems to be a bug in the graphics driver, so it should be reported once we know what triggers it (hardware, driver).
That said, there have been lots of similar bugs and people came up with workarounds there which you can also try for this one.
In case you have an Intel graphics card, here are some workarounds to try:
Reserve memory for the graphics adapter. In the Intel graphics driver (
i915), pixmap caching issues like yours are often connected to the fact that the graphic card's shared memory is dynamically allocated from system memory, so also takes part in swapping, read-back from disk etc. where things can go wrong. So one workaround is to use thememboot parameter to leave enough RAM unallocated by Linux that is then used exclusively by the graphics card. See the detailed instructions. But note that on x86 systems (32 and 64 bit), thememparameter is actually a maximum address [source], so has to be set higher (determined by experiment) than the amount of RAM to leave for Linux.Disable swap. Again for Intel graphics, not including the shared graphics memory in swapping can be a workaround. Especially promising if the problem mostly does not appear after a fresh reboot, only after prolonged and memory-intensive work. So if you have enough RAM, you can just disable swapping completely by adding
swapoff -ato/etc/rc.local[source].Try UXA acceleration. It's an option for the X config file, details here.
Try framebuffer BLIT mode. Again for Intel graphics, you can try
sudo echo COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer >> /etc/environmentand then reboot. [source]Try to reset Compiz to default settings. Reported here (but quite some time ago) to have helped with similar issues. Or while we're at it, try a non-compositing desktop manager instead of Compiz.
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
2
The tip aboutCOGL_ATLAS_DEFAULT_BLIT_MODEdid it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!
– BingsF
Sep 19 '16 at 0:47
1
COGL_ATLAS_DEFAULT_BLIT_MODEseem to work also for me on xubuntu 16, after logging out and in again, without restart.
– Jonatan Öström
Aug 13 '18 at 21:30
add a comment |
Restart the GNOME shell without interfering with any already opened windows using the following command and the missing Panel icons will reappear.
setsid gnome-shell --replace
Press Enter again before closing the terminal.
answered May 24 '18 at 7:38
karelkarel
60k13129153
add a comment |
Sounds a lot like this bug: Bug #1573959 "On-screen text disappears after suspend"
The suggested solution is to upgrade the kernel from 4.4 to 4.8:
sudo apt install linux-generic-hwe-16.04
I did that today, but since I only had the problem a few times in the last months, I can't testify to the effectiveness of this solution. However, others in the bug comments confirm that it solved the problem for them.
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
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%2f764361%2fsome-icons-and-text-randomly-become-invisible-after-waking-up-from-sleep-ubuntu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
This seems to be a bug in the graphics driver, so it should be reported once we know what triggers it (hardware, driver).
That said, there have been lots of similar bugs and people came up with workarounds there which you can also try for this one.
In case you have an Intel graphics card, here are some workarounds to try:
Reserve memory for the graphics adapter. In the Intel graphics driver (
i915), pixmap caching issues like yours are often connected to the fact that the graphic card's shared memory is dynamically allocated from system memory, so also takes part in swapping, read-back from disk etc. where things can go wrong. So one workaround is to use thememboot parameter to leave enough RAM unallocated by Linux that is then used exclusively by the graphics card. See the detailed instructions. But note that on x86 systems (32 and 64 bit), thememparameter is actually a maximum address [source], so has to be set higher (determined by experiment) than the amount of RAM to leave for Linux.Disable swap. Again for Intel graphics, not including the shared graphics memory in swapping can be a workaround. Especially promising if the problem mostly does not appear after a fresh reboot, only after prolonged and memory-intensive work. So if you have enough RAM, you can just disable swapping completely by adding
swapoff -ato/etc/rc.local[source].Try UXA acceleration. It's an option for the X config file, details here.
Try framebuffer BLIT mode. Again for Intel graphics, you can try
sudo echo COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer >> /etc/environmentand then reboot. [source]Try to reset Compiz to default settings. Reported here (but quite some time ago) to have helped with similar issues. Or while we're at it, try a non-compositing desktop manager instead of Compiz.
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
2
The tip aboutCOGL_ATLAS_DEFAULT_BLIT_MODEdid it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!
– BingsF
Sep 19 '16 at 0:47
1
COGL_ATLAS_DEFAULT_BLIT_MODEseem to work also for me on xubuntu 16, after logging out and in again, without restart.
– Jonatan Öström
Aug 13 '18 at 21:30
add a comment |
This seems to be a bug in the graphics driver, so it should be reported once we know what triggers it (hardware, driver).
That said, there have been lots of similar bugs and people came up with workarounds there which you can also try for this one.
In case you have an Intel graphics card, here are some workarounds to try:
Reserve memory for the graphics adapter. In the Intel graphics driver (
i915), pixmap caching issues like yours are often connected to the fact that the graphic card's shared memory is dynamically allocated from system memory, so also takes part in swapping, read-back from disk etc. where things can go wrong. So one workaround is to use thememboot parameter to leave enough RAM unallocated by Linux that is then used exclusively by the graphics card. See the detailed instructions. But note that on x86 systems (32 and 64 bit), thememparameter is actually a maximum address [source], so has to be set higher (determined by experiment) than the amount of RAM to leave for Linux.Disable swap. Again for Intel graphics, not including the shared graphics memory in swapping can be a workaround. Especially promising if the problem mostly does not appear after a fresh reboot, only after prolonged and memory-intensive work. So if you have enough RAM, you can just disable swapping completely by adding
swapoff -ato/etc/rc.local[source].Try UXA acceleration. It's an option for the X config file, details here.
Try framebuffer BLIT mode. Again for Intel graphics, you can try
sudo echo COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer >> /etc/environmentand then reboot. [source]Try to reset Compiz to default settings. Reported here (but quite some time ago) to have helped with similar issues. Or while we're at it, try a non-compositing desktop manager instead of Compiz.
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
2
The tip aboutCOGL_ATLAS_DEFAULT_BLIT_MODEdid it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!
– BingsF
Sep 19 '16 at 0:47
1
COGL_ATLAS_DEFAULT_BLIT_MODEseem to work also for me on xubuntu 16, after logging out and in again, without restart.
– Jonatan Öström
Aug 13 '18 at 21:30
add a comment |
This seems to be a bug in the graphics driver, so it should be reported once we know what triggers it (hardware, driver).
That said, there have been lots of similar bugs and people came up with workarounds there which you can also try for this one.
In case you have an Intel graphics card, here are some workarounds to try:
Reserve memory for the graphics adapter. In the Intel graphics driver (
i915), pixmap caching issues like yours are often connected to the fact that the graphic card's shared memory is dynamically allocated from system memory, so also takes part in swapping, read-back from disk etc. where things can go wrong. So one workaround is to use thememboot parameter to leave enough RAM unallocated by Linux that is then used exclusively by the graphics card. See the detailed instructions. But note that on x86 systems (32 and 64 bit), thememparameter is actually a maximum address [source], so has to be set higher (determined by experiment) than the amount of RAM to leave for Linux.Disable swap. Again for Intel graphics, not including the shared graphics memory in swapping can be a workaround. Especially promising if the problem mostly does not appear after a fresh reboot, only after prolonged and memory-intensive work. So if you have enough RAM, you can just disable swapping completely by adding
swapoff -ato/etc/rc.local[source].Try UXA acceleration. It's an option for the X config file, details here.
Try framebuffer BLIT mode. Again for Intel graphics, you can try
sudo echo COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer >> /etc/environmentand then reboot. [source]Try to reset Compiz to default settings. Reported here (but quite some time ago) to have helped with similar issues. Or while we're at it, try a non-compositing desktop manager instead of Compiz.
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
This seems to be a bug in the graphics driver, so it should be reported once we know what triggers it (hardware, driver).
That said, there have been lots of similar bugs and people came up with workarounds there which you can also try for this one.
In case you have an Intel graphics card, here are some workarounds to try:
Reserve memory for the graphics adapter. In the Intel graphics driver (
i915), pixmap caching issues like yours are often connected to the fact that the graphic card's shared memory is dynamically allocated from system memory, so also takes part in swapping, read-back from disk etc. where things can go wrong. So one workaround is to use thememboot parameter to leave enough RAM unallocated by Linux that is then used exclusively by the graphics card. See the detailed instructions. But note that on x86 systems (32 and 64 bit), thememparameter is actually a maximum address [source], so has to be set higher (determined by experiment) than the amount of RAM to leave for Linux.Disable swap. Again for Intel graphics, not including the shared graphics memory in swapping can be a workaround. Especially promising if the problem mostly does not appear after a fresh reboot, only after prolonged and memory-intensive work. So if you have enough RAM, you can just disable swapping completely by adding
swapoff -ato/etc/rc.local[source].Try UXA acceleration. It's an option for the X config file, details here.
Try framebuffer BLIT mode. Again for Intel graphics, you can try
sudo echo COGL_ATLAS_DEFAULT_BLIT_MODE=framebuffer >> /etc/environmentand then reboot. [source]Try to reset Compiz to default settings. Reported here (but quite some time ago) to have helped with similar issues. Or while we're at it, try a non-compositing desktop manager instead of Compiz.
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
answered Aug 20 '16 at 19:12
taniustanius
2,5921822
2,5921822
2
The tip aboutCOGL_ATLAS_DEFAULT_BLIT_MODEdid it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!
– BingsF
Sep 19 '16 at 0:47
1
COGL_ATLAS_DEFAULT_BLIT_MODEseem to work also for me on xubuntu 16, after logging out and in again, without restart.
– Jonatan Öström
Aug 13 '18 at 21:30
add a comment |
2
The tip aboutCOGL_ATLAS_DEFAULT_BLIT_MODEdid it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!
– BingsF
Sep 19 '16 at 0:47
1
COGL_ATLAS_DEFAULT_BLIT_MODEseem to work also for me on xubuntu 16, after logging out and in again, without restart.
– Jonatan Öström
Aug 13 '18 at 21:30
2
2
The tip about
COGL_ATLAS_DEFAULT_BLIT_MODE did it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!– BingsF
Sep 19 '16 at 0:47
The tip about
COGL_ATLAS_DEFAULT_BLIT_MODE did it for me! It also resolved an issue I've been having where the screen would take about 5 seconds to turn on when waking up from sleep; now it activates instantaneously!– BingsF
Sep 19 '16 at 0:47
1
1
COGL_ATLAS_DEFAULT_BLIT_MODE seem to work also for me on xubuntu 16, after logging out and in again, without restart.– Jonatan Öström
Aug 13 '18 at 21:30
COGL_ATLAS_DEFAULT_BLIT_MODE seem to work also for me on xubuntu 16, after logging out and in again, without restart.– Jonatan Öström
Aug 13 '18 at 21:30
add a comment |
Restart the GNOME shell without interfering with any already opened windows using the following command and the missing Panel icons will reappear.
setsid gnome-shell --replace
Press Enter again before closing the terminal.
answered May 24 '18 at 7:38
karelkarel
60k13129153
add a comment |
Restart the GNOME shell without interfering with any already opened windows using the following command and the missing Panel icons will reappear.
setsid gnome-shell --replace
Press Enter again before closing the terminal.
answered May 24 '18 at 7:38
karelkarel
60k13129153
add a comment |
Restart the GNOME shell without interfering with any already opened windows using the following command and the missing Panel icons will reappear.
setsid gnome-shell --replace
Press Enter again before closing the terminal.
answered May 24 '18 at 7:38
karelkarel
60k13129153
Restart the GNOME shell without interfering with any already opened windows using the following command and the missing Panel icons will reappear.
setsid gnome-shell --replace
Press Enter again before closing the terminal.
answered May 24 '18 at 7:38
karelkarel
60k13129153
edited Aug 13 '18 at 21:31
answered May 24 '18 at 7:38
karelkarel
60k13129153
answered May 24 '18 at 7:38
karelkarel
60k13129153
answered May 24 '18 at 7:38
karelkarel
60k13129153
60k13129153
add a comment |
add a comment |
Sounds a lot like this bug: Bug #1573959 "On-screen text disappears after suspend"
The suggested solution is to upgrade the kernel from 4.4 to 4.8:
sudo apt install linux-generic-hwe-16.04
I did that today, but since I only had the problem a few times in the last months, I can't testify to the effectiveness of this solution. However, others in the bug comments confirm that it solved the problem for them.
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
add a comment |
Sounds a lot like this bug: Bug #1573959 "On-screen text disappears after suspend"
The suggested solution is to upgrade the kernel from 4.4 to 4.8:
sudo apt install linux-generic-hwe-16.04
I did that today, but since I only had the problem a few times in the last months, I can't testify to the effectiveness of this solution. However, others in the bug comments confirm that it solved the problem for them.
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
add a comment |
Sounds a lot like this bug: Bug #1573959 "On-screen text disappears after suspend"
The suggested solution is to upgrade the kernel from 4.4 to 4.8:
sudo apt install linux-generic-hwe-16.04
I did that today, but since I only had the problem a few times in the last months, I can't testify to the effectiveness of this solution. However, others in the bug comments confirm that it solved the problem for them.
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
Sounds a lot like this bug: Bug #1573959 "On-screen text disappears after suspend"
The suggested solution is to upgrade the kernel from 4.4 to 4.8:
sudo apt install linux-generic-hwe-16.04
I did that today, but since I only had the problem a few times in the last months, I can't testify to the effectiveness of this solution. However, others in the bug comments confirm that it solved the problem for them.
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
answered Jun 15 '17 at 20:22
mivkmivk
2,3332434
2,3332434
add a comment |
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%2f764361%2fsome-icons-and-text-randomly-become-invisible-after-waking-up-from-sleep-ubuntu%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
3
I'm having the same problem.
– Anmol Singh Jaggi
May 14 '16 at 11:21
What is your graphics hardware and driver? Same thing here on a Intel GMA 4500MHD (in GS45 chipset), for me a new problem since Ubuntu 16.04.
– tanius
Aug 20 '16 at 18:50
I havn't installed any drivers, but my processor is an intel i3 4005u.
– smurfendrek123
Aug 21 '16 at 19:53
I will say that i've never had this problem since switching to fedora.
– smurfendrek123
Feb 2 at 9:06