Strange graphics issue after upgrading to 18.04 that affects only one user account
After upgrading from 17.10 to 18.04, I started experiencing a strange graphics issue: text and background in scrollable parts of some windows were getting "scrambled". I performed a fresh installation of Ubuntu 18.04.1 when it became available (formatting the system partitions), but this did not resolve the problem.
However, I cannot reproduce this problem in a fresh account, even if I copy over my entire dconf
configuration! I also tried resetting the dconf
configuration in the affected account and disabling (all) GNOME Shell extensions, but it did not help.
The problem appears usually when I try to scroll the text in a scrollable area or resize the window. Maybe other parts of windows are also affected. Sometimes the problem appears immediately on opening a window.
When I scroll a scrollable area or resize the whole window, text and background get scrambled by overlapping on themselves. Sometimes black or transparent areas appear. GNOME Calculator 3.28.2 and gitg 3.26 windows are strongly affected. With GNOME Calculator the issue it the easiest to reproduce -- it suffices to launch it.
Which system or user settings could cause such problem?
I am attaching pictures which show the problem.
I have Intel HD Graphics 520 (Skylake GT2).
By the way, 3D gaming works fine.
Things I tried that did not help:
sudo apt install xserver-xorg-video-intel
,sudo update-initramfs -u
.Reinstall Ubuntu 18.04.1 completely.
dconf reset -f /
and disable GNOME Shell extensions.
xorg 18.04 ubuntu-gnome window-manager
add a comment |
After upgrading from 17.10 to 18.04, I started experiencing a strange graphics issue: text and background in scrollable parts of some windows were getting "scrambled". I performed a fresh installation of Ubuntu 18.04.1 when it became available (formatting the system partitions), but this did not resolve the problem.
However, I cannot reproduce this problem in a fresh account, even if I copy over my entire dconf
configuration! I also tried resetting the dconf
configuration in the affected account and disabling (all) GNOME Shell extensions, but it did not help.
The problem appears usually when I try to scroll the text in a scrollable area or resize the window. Maybe other parts of windows are also affected. Sometimes the problem appears immediately on opening a window.
When I scroll a scrollable area or resize the whole window, text and background get scrambled by overlapping on themselves. Sometimes black or transparent areas appear. GNOME Calculator 3.28.2 and gitg 3.26 windows are strongly affected. With GNOME Calculator the issue it the easiest to reproduce -- it suffices to launch it.
Which system or user settings could cause such problem?
I am attaching pictures which show the problem.
I have Intel HD Graphics 520 (Skylake GT2).
By the way, 3D gaming works fine.
Things I tried that did not help:
sudo apt install xserver-xorg-video-intel
,sudo update-initramfs -u
.Reinstall Ubuntu 18.04.1 completely.
dconf reset -f /
and disable GNOME Shell extensions.
xorg 18.04 ubuntu-gnome window-manager
Useless comment: don't fight it. Just reinstall. I had that issue askubuntu.com/q/1031549/350004 and gave up and reinstall a fresh ubuntu.
– solsTiCe
May 8 '18 at 17:33
have you installed graphics drivers? what is your graphics card?
– Joshua Besneatte
May 8 '18 at 18:05
My update today installed "intel-firmware-microcode"... I wonder if that would do anything for you? I swear I have had this happen to me before and it was a driver of some sort that fixed it. What is your lsmod and lspci output?
– Joshua Besneatte
May 8 '18 at 20:37
add a comment |
After upgrading from 17.10 to 18.04, I started experiencing a strange graphics issue: text and background in scrollable parts of some windows were getting "scrambled". I performed a fresh installation of Ubuntu 18.04.1 when it became available (formatting the system partitions), but this did not resolve the problem.
However, I cannot reproduce this problem in a fresh account, even if I copy over my entire dconf
configuration! I also tried resetting the dconf
configuration in the affected account and disabling (all) GNOME Shell extensions, but it did not help.
The problem appears usually when I try to scroll the text in a scrollable area or resize the window. Maybe other parts of windows are also affected. Sometimes the problem appears immediately on opening a window.
When I scroll a scrollable area or resize the whole window, text and background get scrambled by overlapping on themselves. Sometimes black or transparent areas appear. GNOME Calculator 3.28.2 and gitg 3.26 windows are strongly affected. With GNOME Calculator the issue it the easiest to reproduce -- it suffices to launch it.
Which system or user settings could cause such problem?
I am attaching pictures which show the problem.
I have Intel HD Graphics 520 (Skylake GT2).
By the way, 3D gaming works fine.
Things I tried that did not help:
sudo apt install xserver-xorg-video-intel
,sudo update-initramfs -u
.Reinstall Ubuntu 18.04.1 completely.
dconf reset -f /
and disable GNOME Shell extensions.
xorg 18.04 ubuntu-gnome window-manager
After upgrading from 17.10 to 18.04, I started experiencing a strange graphics issue: text and background in scrollable parts of some windows were getting "scrambled". I performed a fresh installation of Ubuntu 18.04.1 when it became available (formatting the system partitions), but this did not resolve the problem.
However, I cannot reproduce this problem in a fresh account, even if I copy over my entire dconf
configuration! I also tried resetting the dconf
configuration in the affected account and disabling (all) GNOME Shell extensions, but it did not help.
The problem appears usually when I try to scroll the text in a scrollable area or resize the window. Maybe other parts of windows are also affected. Sometimes the problem appears immediately on opening a window.
When I scroll a scrollable area or resize the whole window, text and background get scrambled by overlapping on themselves. Sometimes black or transparent areas appear. GNOME Calculator 3.28.2 and gitg 3.26 windows are strongly affected. With GNOME Calculator the issue it the easiest to reproduce -- it suffices to launch it.
Which system or user settings could cause such problem?
I am attaching pictures which show the problem.
I have Intel HD Graphics 520 (Skylake GT2).
By the way, 3D gaming works fine.
Things I tried that did not help:
sudo apt install xserver-xorg-video-intel
,sudo update-initramfs -u
.Reinstall Ubuntu 18.04.1 completely.
dconf reset -f /
and disable GNOME Shell extensions.
xorg 18.04 ubuntu-gnome window-manager
xorg 18.04 ubuntu-gnome window-manager
edited Aug 31 '18 at 14:53
Alexey
asked May 8 '18 at 16:41
AlexeyAlexey
326520
326520
Useless comment: don't fight it. Just reinstall. I had that issue askubuntu.com/q/1031549/350004 and gave up and reinstall a fresh ubuntu.
– solsTiCe
May 8 '18 at 17:33
have you installed graphics drivers? what is your graphics card?
– Joshua Besneatte
May 8 '18 at 18:05
My update today installed "intel-firmware-microcode"... I wonder if that would do anything for you? I swear I have had this happen to me before and it was a driver of some sort that fixed it. What is your lsmod and lspci output?
– Joshua Besneatte
May 8 '18 at 20:37
add a comment |
Useless comment: don't fight it. Just reinstall. I had that issue askubuntu.com/q/1031549/350004 and gave up and reinstall a fresh ubuntu.
– solsTiCe
May 8 '18 at 17:33
have you installed graphics drivers? what is your graphics card?
– Joshua Besneatte
May 8 '18 at 18:05
My update today installed "intel-firmware-microcode"... I wonder if that would do anything for you? I swear I have had this happen to me before and it was a driver of some sort that fixed it. What is your lsmod and lspci output?
– Joshua Besneatte
May 8 '18 at 20:37
Useless comment: don't fight it. Just reinstall. I had that issue askubuntu.com/q/1031549/350004 and gave up and reinstall a fresh ubuntu.
– solsTiCe
May 8 '18 at 17:33
Useless comment: don't fight it. Just reinstall. I had that issue askubuntu.com/q/1031549/350004 and gave up and reinstall a fresh ubuntu.
– solsTiCe
May 8 '18 at 17:33
have you installed graphics drivers? what is your graphics card?
– Joshua Besneatte
May 8 '18 at 18:05
have you installed graphics drivers? what is your graphics card?
– Joshua Besneatte
May 8 '18 at 18:05
My update today installed "intel-firmware-microcode"... I wonder if that would do anything for you? I swear I have had this happen to me before and it was a driver of some sort that fixed it. What is your lsmod and lspci output?
– Joshua Besneatte
May 8 '18 at 20:37
My update today installed "intel-firmware-microcode"... I wonder if that would do anything for you? I swear I have had this happen to me before and it was a driver of some sort that fixed it. What is your lsmod and lspci output?
– Joshua Besneatte
May 8 '18 at 20:37
add a comment |
4 Answers
4
active
oldest
votes
I decided to clean up a bit some abandoned "dot-files" in my home folder (the home directory of the affected account) and managed to resolve the problem.
The problem was caused by my .xinputrc
file that contained a single line of code:
run_im xim
In comments it was saying that it was created by im-config
. (I do not remember why I executed im-config
.) After I removed this file, the glitches were gone.
Update. It seems that the file got automatically regenerated with the following content:
# im-config(8) generated on Sun, 29 Jul 2018 09:11:43 +0200
run_im ibus
# im-config signature: 1badc17f2a2c24108e97cd2fd412e476 -
There is currently no problems with this new content. (I am not sure if the file was regenerated by Ubuntu.)
add a comment |
Reinstall the Drivers
Per this answerr try reinstalling intel drivers:
sudo apt-get update
sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
If this doesn't work, you might be able to fix it by tweaking settings with intel goodies:
sudo apt install intel-microcode inteltool intel-gpu-tools
But I don't know how to use them so you are on your own. Here is a reference manual for intel-gpu-tools and you can always read the manpages. eg
man intel-gpu-tools
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
Everything is the same. I installedxserver-xorg-video-intel
and rebooted, and i already hadintel-microcode
(but i would be quite surprised if it was related).
– Alexey
May 9 '18 at 6:45
add a comment |
When you run update-initramfs
you should not be getting error messages for missing skylake drivers.
Under Ubuntu 16.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.14.34-041434-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
Under Ubuntu 18.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
In particular you should be seeing the last line. If not follow the instructions here: Updated kernel to 4.8 now missing firmware warnings
I tried, thanks. The only line it printed was:update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.
– Alexey
May 9 '18 at 6:48
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings withkbl
are not relevant to me because they are about Kaby Lake
– Alexey
May 9 '18 at 7:20
@Alexey OK. But did you runupdate-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?
– WinEunuuchs2Unix
May 9 '18 at 10:35
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
|
show 2 more comments
I had the same graphical issues in Ubuntu 18.04 LTS (after upgrading from version 16.04.5 to 18.04.1), only the following command solved the problems:
$ dconf reset -f /org/gnome/
As i mentioned,dconf reset
did not work for me.
– Alexey
Aug 12 '18 at 13:10
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%2f1033665%2fstrange-graphics-issue-after-upgrading-to-18-04-that-affects-only-one-user-accou%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I decided to clean up a bit some abandoned "dot-files" in my home folder (the home directory of the affected account) and managed to resolve the problem.
The problem was caused by my .xinputrc
file that contained a single line of code:
run_im xim
In comments it was saying that it was created by im-config
. (I do not remember why I executed im-config
.) After I removed this file, the glitches were gone.
Update. It seems that the file got automatically regenerated with the following content:
# im-config(8) generated on Sun, 29 Jul 2018 09:11:43 +0200
run_im ibus
# im-config signature: 1badc17f2a2c24108e97cd2fd412e476 -
There is currently no problems with this new content. (I am not sure if the file was regenerated by Ubuntu.)
add a comment |
I decided to clean up a bit some abandoned "dot-files" in my home folder (the home directory of the affected account) and managed to resolve the problem.
The problem was caused by my .xinputrc
file that contained a single line of code:
run_im xim
In comments it was saying that it was created by im-config
. (I do not remember why I executed im-config
.) After I removed this file, the glitches were gone.
Update. It seems that the file got automatically regenerated with the following content:
# im-config(8) generated on Sun, 29 Jul 2018 09:11:43 +0200
run_im ibus
# im-config signature: 1badc17f2a2c24108e97cd2fd412e476 -
There is currently no problems with this new content. (I am not sure if the file was regenerated by Ubuntu.)
add a comment |
I decided to clean up a bit some abandoned "dot-files" in my home folder (the home directory of the affected account) and managed to resolve the problem.
The problem was caused by my .xinputrc
file that contained a single line of code:
run_im xim
In comments it was saying that it was created by im-config
. (I do not remember why I executed im-config
.) After I removed this file, the glitches were gone.
Update. It seems that the file got automatically regenerated with the following content:
# im-config(8) generated on Sun, 29 Jul 2018 09:11:43 +0200
run_im ibus
# im-config signature: 1badc17f2a2c24108e97cd2fd412e476 -
There is currently no problems with this new content. (I am not sure if the file was regenerated by Ubuntu.)
I decided to clean up a bit some abandoned "dot-files" in my home folder (the home directory of the affected account) and managed to resolve the problem.
The problem was caused by my .xinputrc
file that contained a single line of code:
run_im xim
In comments it was saying that it was created by im-config
. (I do not remember why I executed im-config
.) After I removed this file, the glitches were gone.
Update. It seems that the file got automatically regenerated with the following content:
# im-config(8) generated on Sun, 29 Jul 2018 09:11:43 +0200
run_im ibus
# im-config signature: 1badc17f2a2c24108e97cd2fd412e476 -
There is currently no problems with this new content. (I am not sure if the file was regenerated by Ubuntu.)
edited Jan 14 at 15:03
answered Jul 27 '18 at 14:54
AlexeyAlexey
326520
326520
add a comment |
add a comment |
Reinstall the Drivers
Per this answerr try reinstalling intel drivers:
sudo apt-get update
sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
If this doesn't work, you might be able to fix it by tweaking settings with intel goodies:
sudo apt install intel-microcode inteltool intel-gpu-tools
But I don't know how to use them so you are on your own. Here is a reference manual for intel-gpu-tools and you can always read the manpages. eg
man intel-gpu-tools
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
Everything is the same. I installedxserver-xorg-video-intel
and rebooted, and i already hadintel-microcode
(but i would be quite surprised if it was related).
– Alexey
May 9 '18 at 6:45
add a comment |
Reinstall the Drivers
Per this answerr try reinstalling intel drivers:
sudo apt-get update
sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
If this doesn't work, you might be able to fix it by tweaking settings with intel goodies:
sudo apt install intel-microcode inteltool intel-gpu-tools
But I don't know how to use them so you are on your own. Here is a reference manual for intel-gpu-tools and you can always read the manpages. eg
man intel-gpu-tools
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
Everything is the same. I installedxserver-xorg-video-intel
and rebooted, and i already hadintel-microcode
(but i would be quite surprised if it was related).
– Alexey
May 9 '18 at 6:45
add a comment |
Reinstall the Drivers
Per this answerr try reinstalling intel drivers:
sudo apt-get update
sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
If this doesn't work, you might be able to fix it by tweaking settings with intel goodies:
sudo apt install intel-microcode inteltool intel-gpu-tools
But I don't know how to use them so you are on your own. Here is a reference manual for intel-gpu-tools and you can always read the manpages. eg
man intel-gpu-tools
Reinstall the Drivers
Per this answerr try reinstalling intel drivers:
sudo apt-get update
sudo apt-get install --reinstall xserver-xorg-video-intel xserver-xorg-core
sudo dpkg-reconfigure xserver-xorg
If this doesn't work, you might be able to fix it by tweaking settings with intel goodies:
sudo apt install intel-microcode inteltool intel-gpu-tools
But I don't know how to use them so you are on your own. Here is a reference manual for intel-gpu-tools and you can always read the manpages. eg
man intel-gpu-tools
answered May 8 '18 at 21:44
Joshua BesneatteJoshua Besneatte
2,06711024
2,06711024
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
Everything is the same. I installedxserver-xorg-video-intel
and rebooted, and i already hadintel-microcode
(but i would be quite surprised if it was related).
– Alexey
May 9 '18 at 6:45
add a comment |
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
Everything is the same. I installedxserver-xorg-video-intel
and rebooted, and i already hadintel-microcode
(but i would be quite surprised if it was related).
– Alexey
May 9 '18 at 6:45
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
I tried the first three commands, they didn't help. gitg windows are still scrambled.
– Alexey
May 8 '18 at 22:57
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
is it just gitg? did you reinstall that? did you install xserver-xorg-video-intel and reboot? did you install intel-microcode?
– Joshua Besneatte
May 8 '18 at 23:11
Everything is the same. I installed
xserver-xorg-video-intel
and rebooted, and i already had intel-microcode
(but i would be quite surprised if it was related).– Alexey
May 9 '18 at 6:45
Everything is the same. I installed
xserver-xorg-video-intel
and rebooted, and i already had intel-microcode
(but i would be quite surprised if it was related).– Alexey
May 9 '18 at 6:45
add a comment |
When you run update-initramfs
you should not be getting error messages for missing skylake drivers.
Under Ubuntu 16.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.14.34-041434-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
Under Ubuntu 18.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
In particular you should be seeing the last line. If not follow the instructions here: Updated kernel to 4.8 now missing firmware warnings
I tried, thanks. The only line it printed was:update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.
– Alexey
May 9 '18 at 6:48
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings withkbl
are not relevant to me because they are about Kaby Lake
– Alexey
May 9 '18 at 7:20
@Alexey OK. But did you runupdate-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?
– WinEunuuchs2Unix
May 9 '18 at 10:35
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
|
show 2 more comments
When you run update-initramfs
you should not be getting error messages for missing skylake drivers.
Under Ubuntu 16.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.14.34-041434-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
Under Ubuntu 18.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
In particular you should be seeing the last line. If not follow the instructions here: Updated kernel to 4.8 now missing firmware warnings
I tried, thanks. The only line it printed was:update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.
– Alexey
May 9 '18 at 6:48
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings withkbl
are not relevant to me because they are about Kaby Lake
– Alexey
May 9 '18 at 7:20
@Alexey OK. But did you runupdate-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?
– WinEunuuchs2Unix
May 9 '18 at 10:35
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
|
show 2 more comments
When you run update-initramfs
you should not be getting error messages for missing skylake drivers.
Under Ubuntu 16.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.14.34-041434-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
Under Ubuntu 18.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
In particular you should be seeing the last line. If not follow the instructions here: Updated kernel to 4.8 now missing firmware warnings
When you run update-initramfs
you should not be getting error messages for missing skylake drivers.
Under Ubuntu 16.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.14.34-041434-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
Under Ubuntu 18.04 LTS:
$ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
Adding /lib/firmware/i915/skl_guc_ver9_33.bin
In particular you should be seeing the last line. If not follow the instructions here: Updated kernel to 4.8 now missing firmware warnings
edited May 9 '18 at 11:31
answered May 8 '18 at 23:46
WinEunuuchs2UnixWinEunuuchs2Unix
44.7k1080170
44.7k1080170
I tried, thanks. The only line it printed was:update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.
– Alexey
May 9 '18 at 6:48
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings withkbl
are not relevant to me because they are about Kaby Lake
– Alexey
May 9 '18 at 7:20
@Alexey OK. But did you runupdate-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?
– WinEunuuchs2Unix
May 9 '18 at 10:35
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
|
show 2 more comments
I tried, thanks. The only line it printed was:update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.
– Alexey
May 9 '18 at 6:48
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings withkbl
are not relevant to me because they are about Kaby Lake
– Alexey
May 9 '18 at 7:20
@Alexey OK. But did you runupdate-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?
– WinEunuuchs2Unix
May 9 '18 at 10:35
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
I tried, thanks. The only line it printed was:
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.– Alexey
May 9 '18 at 6:48
I tried, thanks. The only line it printed was:
update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic
.– Alexey
May 9 '18 at 6:48
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings with
kbl
are not relevant to me because they are about Kaby Lake– Alexey
May 9 '18 at 7:20
In fact, i used to see the warning mentioned in the question you linked in previous versions of Ubuntu (before my graphics issues), but i haven't noticed them so far in 18.04. I understand that those warnings with
kbl
are not relevant to me because they are about Kaby Lake– Alexey
May 9 '18 at 7:20
@Alexey OK. But did you run
update-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?– WinEunuuchs2Unix
May 9 '18 at 10:35
@Alexey OK. But did you run
update-iniitramfs
above and see the Skylake driver (skl_guc_ver9_33.bin
)added?– WinEunuuchs2Unix
May 9 '18 at 10:35
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
As i said, it only printed one line.
– Alexey
May 9 '18 at 11:19
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
@Alexey You might want to add the Skylake driver then. I can't say if it will fix the problem though.
– WinEunuuchs2Unix
May 9 '18 at 11:32
|
show 2 more comments
I had the same graphical issues in Ubuntu 18.04 LTS (after upgrading from version 16.04.5 to 18.04.1), only the following command solved the problems:
$ dconf reset -f /org/gnome/
As i mentioned,dconf reset
did not work for me.
– Alexey
Aug 12 '18 at 13:10
add a comment |
I had the same graphical issues in Ubuntu 18.04 LTS (after upgrading from version 16.04.5 to 18.04.1), only the following command solved the problems:
$ dconf reset -f /org/gnome/
As i mentioned,dconf reset
did not work for me.
– Alexey
Aug 12 '18 at 13:10
add a comment |
I had the same graphical issues in Ubuntu 18.04 LTS (after upgrading from version 16.04.5 to 18.04.1), only the following command solved the problems:
$ dconf reset -f /org/gnome/
I had the same graphical issues in Ubuntu 18.04 LTS (after upgrading from version 16.04.5 to 18.04.1), only the following command solved the problems:
$ dconf reset -f /org/gnome/
answered Aug 12 '18 at 11:27
realmicrealmic
112
112
As i mentioned,dconf reset
did not work for me.
– Alexey
Aug 12 '18 at 13:10
add a comment |
As i mentioned,dconf reset
did not work for me.
– Alexey
Aug 12 '18 at 13:10
As i mentioned,
dconf reset
did not work for me.– Alexey
Aug 12 '18 at 13:10
As i mentioned,
dconf reset
did not work for me.– Alexey
Aug 12 '18 at 13:10
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%2f1033665%2fstrange-graphics-issue-after-upgrading-to-18-04-that-affects-only-one-user-accou%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
Useless comment: don't fight it. Just reinstall. I had that issue askubuntu.com/q/1031549/350004 and gave up and reinstall a fresh ubuntu.
– solsTiCe
May 8 '18 at 17:33
have you installed graphics drivers? what is your graphics card?
– Joshua Besneatte
May 8 '18 at 18:05
My update today installed "intel-firmware-microcode"... I wonder if that would do anything for you? I swear I have had this happen to me before and it was a driver of some sort that fixed it. What is your lsmod and lspci output?
– Joshua Besneatte
May 8 '18 at 20:37