Ubuntu 18.04.1 freezes when connecting to a second screen
Everything worked fine until yesterday :) I use a mini-DP to connect to my screen for over a year now. Now, when I connect the cable it recognizes it (so I see the Ubuntu background in the screen and can work in my laptop) but when I close the lid or set the monitor as the main screen (so as to work only from the monitor screen as I have been doing), the whole system freezes. Removing the cable does nothing. Only hard reboot (pressing continuously the power button) brings it up.
Kernel: 4.15.0-44-generic, on 18.04.1 LTS (Bionic).
I cannot get anything from dmesg because of the freeze, but some errors from /var/log/syslog that maybe can help:
kernel: [ 495.245250] ACPI Error: Method parse/execution failed _GPE.XTBT, AE_ALREADY_EXISTS (20170831/psparse-550)
...
kernel: [ 495.308520] pci 0000:03:00.0: BAR 13: failed to assign [io size 0x2000]
...
gsd-color[1425]: no xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L device found: Failed to find output xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L
...
/usr/lib/gdm3/gdm-x-session[1974]: Errors from xkbcomp are not fatal to the X server
...
systemd-udevd[4191]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
...
gnome-shell[1216]: Failed to apply DRM plane transform 0: Permission denied
gnome-shell[1216]: Failed to read EDID from 'eDP-1': No such file or directory
gnome-shell[1216]: message repeated 3 times: [ Failed to read EDID from 'eDP-1': No such file or directory]
gsd-color[1425]: failed to set screen _ICC_PROFILE: Failed to open file â<80><9c>/home/john/.local/share/icc/edid-18e261c7e650a8a483510701873ac4e2.iccâ<80><9d>: Permission denied
Anyone else with the same problem? What do I have to do if this is a general issue to let Ubuntu developers know about it?
18.04 display monitor bug-reporting displayport
asked Jan 31 at 10:02
JohnJohn
263
|
show 2 more comments
Everything worked fine until yesterday :) I use a mini-DP to connect to my screen for over a year now. Now, when I connect the cable it recognizes it (so I see the Ubuntu background in the screen and can work in my laptop) but when I close the lid or set the monitor as the main screen (so as to work only from the monitor screen as I have been doing), the whole system freezes. Removing the cable does nothing. Only hard reboot (pressing continuously the power button) brings it up.
Kernel: 4.15.0-44-generic, on 18.04.1 LTS (Bionic).
I cannot get anything from dmesg because of the freeze, but some errors from /var/log/syslog that maybe can help:
kernel: [ 495.245250] ACPI Error: Method parse/execution failed _GPE.XTBT, AE_ALREADY_EXISTS (20170831/psparse-550)
...
kernel: [ 495.308520] pci 0000:03:00.0: BAR 13: failed to assign [io size 0x2000]
...
gsd-color[1425]: no xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L device found: Failed to find output xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L
...
/usr/lib/gdm3/gdm-x-session[1974]: Errors from xkbcomp are not fatal to the X server
...
systemd-udevd[4191]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
...
gnome-shell[1216]: Failed to apply DRM plane transform 0: Permission denied
gnome-shell[1216]: Failed to read EDID from 'eDP-1': No such file or directory
gnome-shell[1216]: message repeated 3 times: [ Failed to read EDID from 'eDP-1': No such file or directory]
gsd-color[1425]: failed to set screen _ICC_PROFILE: Failed to open file â<80><9c>/home/john/.local/share/icc/edid-18e261c7e650a8a483510701873ac4e2.iccâ<80><9d>: Permission denied
Anyone else with the same problem? What do I have to do if this is a general issue to let Ubuntu developers know about it?
18.04 display monitor bug-reporting displayport
asked Jan 31 at 10:02
JohnJohn
263
1
I think you have similar problem with me. askubuntu.com/questions/1114052/paralel-monitor-problem
– Huseyin
Jan 31 at 10:05
1
I think is because of a bug in new update package. I am using 4.15.0-43-generic . please look here askubuntu.com/a/82144/139749
– Huseyin
Jan 31 at 10:09
It seems like this bug has not been fixed yet.
– d a i s y
Jan 31 at 10:10
Ok, so it seems it is known. Anything I can do to help with the developers' effort? Will they see this message for example?
– John
Jan 31 at 10:21
Please do consider Huseyin's comment as he said he had similar issue and also see this one too.
– d a i s y
Jan 31 at 10:34
|
show 2 more comments
Everything worked fine until yesterday :) I use a mini-DP to connect to my screen for over a year now. Now, when I connect the cable it recognizes it (so I see the Ubuntu background in the screen and can work in my laptop) but when I close the lid or set the monitor as the main screen (so as to work only from the monitor screen as I have been doing), the whole system freezes. Removing the cable does nothing. Only hard reboot (pressing continuously the power button) brings it up.
Kernel: 4.15.0-44-generic, on 18.04.1 LTS (Bionic).
I cannot get anything from dmesg because of the freeze, but some errors from /var/log/syslog that maybe can help:
kernel: [ 495.245250] ACPI Error: Method parse/execution failed _GPE.XTBT, AE_ALREADY_EXISTS (20170831/psparse-550)
...
kernel: [ 495.308520] pci 0000:03:00.0: BAR 13: failed to assign [io size 0x2000]
...
gsd-color[1425]: no xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L device found: Failed to find output xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L
...
/usr/lib/gdm3/gdm-x-session[1974]: Errors from xkbcomp are not fatal to the X server
...
systemd-udevd[4191]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
...
gnome-shell[1216]: Failed to apply DRM plane transform 0: Permission denied
gnome-shell[1216]: Failed to read EDID from 'eDP-1': No such file or directory
gnome-shell[1216]: message repeated 3 times: [ Failed to read EDID from 'eDP-1': No such file or directory]
gsd-color[1425]: failed to set screen _ICC_PROFILE: Failed to open file â<80><9c>/home/john/.local/share/icc/edid-18e261c7e650a8a483510701873ac4e2.iccâ<80><9d>: Permission denied
Anyone else with the same problem? What do I have to do if this is a general issue to let Ubuntu developers know about it?
18.04 display monitor bug-reporting displayport
asked Jan 31 at 10:02
JohnJohn
263
Everything worked fine until yesterday :) I use a mini-DP to connect to my screen for over a year now. Now, when I connect the cable it recognizes it (so I see the Ubuntu background in the screen and can work in my laptop) but when I close the lid or set the monitor as the main screen (so as to work only from the monitor screen as I have been doing), the whole system freezes. Removing the cable does nothing. Only hard reboot (pressing continuously the power button) brings it up.
Kernel: 4.15.0-44-generic, on 18.04.1 LTS (Bionic).
I cannot get anything from dmesg because of the freeze, but some errors from /var/log/syslog that maybe can help:
kernel: [ 495.245250] ACPI Error: Method parse/execution failed _GPE.XTBT, AE_ALREADY_EXISTS (20170831/psparse-550)
...
kernel: [ 495.308520] pci 0000:03:00.0: BAR 13: failed to assign [io size 0x2000]
...
gsd-color[1425]: no xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L device found: Failed to find output xrandr-Dell Inc.-DELL U2417H-5K9YD7AE224L
...
/usr/lib/gdm3/gdm-x-session[1974]: Errors from xkbcomp are not fatal to the X server
...
systemd-udevd[4191]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
...
gnome-shell[1216]: Failed to apply DRM plane transform 0: Permission denied
gnome-shell[1216]: Failed to read EDID from 'eDP-1': No such file or directory
gnome-shell[1216]: message repeated 3 times: [ Failed to read EDID from 'eDP-1': No such file or directory]
gsd-color[1425]: failed to set screen _ICC_PROFILE: Failed to open file â<80><9c>/home/john/.local/share/icc/edid-18e261c7e650a8a483510701873ac4e2.iccâ<80><9d>: Permission denied
Anyone else with the same problem? What do I have to do if this is a general issue to let Ubuntu developers know about it?
18.04 display monitor bug-reporting displayport
18.04 display monitor bug-reporting displayport
asked Jan 31 at 10:02
JohnJohn
263
asked Jan 31 at 10:02
JohnJohn
263
asked Jan 31 at 10:02
JohnJohn
263
asked Jan 31 at 10:02
JohnJohn
263
asked Jan 31 at 10:02
JohnJohn
263
263
1
I think you have similar problem with me. askubuntu.com/questions/1114052/paralel-monitor-problem
– Huseyin
Jan 31 at 10:05
1
I think is because of a bug in new update package. I am using 4.15.0-43-generic . please look here askubuntu.com/a/82144/139749
– Huseyin
Jan 31 at 10:09
It seems like this bug has not been fixed yet.
– d a i s y
Jan 31 at 10:10
Ok, so it seems it is known. Anything I can do to help with the developers' effort? Will they see this message for example?
– John
Jan 31 at 10:21
Please do consider Huseyin's comment as he said he had similar issue and also see this one too.
– d a i s y
Jan 31 at 10:34
|
show 2 more comments
1
I think you have similar problem with me. askubuntu.com/questions/1114052/paralel-monitor-problem
– Huseyin
Jan 31 at 10:05
1
I think is because of a bug in new update package. I am using 4.15.0-43-generic . please look here askubuntu.com/a/82144/139749
– Huseyin
Jan 31 at 10:09
It seems like this bug has not been fixed yet.
– d a i s y
Jan 31 at 10:10
Ok, so it seems it is known. Anything I can do to help with the developers' effort? Will they see this message for example?
– John
Jan 31 at 10:21
Please do consider Huseyin's comment as he said he had similar issue and also see this one too.
– d a i s y
Jan 31 at 10:34
1
1
I think you have similar problem with me. askubuntu.com/questions/1114052/paralel-monitor-problem
– Huseyin
Jan 31 at 10:05
I think you have similar problem with me. askubuntu.com/questions/1114052/paralel-monitor-problem
– Huseyin
Jan 31 at 10:05
1
1
I think is because of a bug in new update package. I am using 4.15.0-43-generic . please look here askubuntu.com/a/82144/139749
– Huseyin
Jan 31 at 10:09
I think is because of a bug in new update package. I am using 4.15.0-43-generic . please look here askubuntu.com/a/82144/139749
– Huseyin
Jan 31 at 10:09
It seems like this bug has not been fixed yet.
– d a i s y
Jan 31 at 10:10
It seems like this bug has not been fixed yet.
– d a i s y
Jan 31 at 10:10
Ok, so it seems it is known. Anything I can do to help with the developers' effort? Will they see this message for example?
– John
Jan 31 at 10:21
Ok, so it seems it is known. Anything I can do to help with the developers' effort? Will they see this message for example?
– John
Jan 31 at 10:21
Please do consider Huseyin's comment as he said he had similar issue and also see this one too.
– d a i s y
Jan 31 at 10:34
Please do consider Huseyin's comment as he said he had similar issue and also see this one too.
– d a i s y
Jan 31 at 10:34
|
show 2 more comments
1 Answer
1
active
oldest
votes
So, the issue is in the 4.15.0-44-generic kernel and has been solved in the 4.15.0-45-generic. To manually update, run:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
And that fixes it.
answered Feb 4 at 8:31
JohnJohn
263
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%2f1114350%2fubuntu-18-04-1-freezes-when-connecting-to-a-second-screen%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So, the issue is in the 4.15.0-44-generic kernel and has been solved in the 4.15.0-45-generic. To manually update, run:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
And that fixes it.
answered Feb 4 at 8:31
JohnJohn
263
add a comment |
So, the issue is in the 4.15.0-44-generic kernel and has been solved in the 4.15.0-45-generic. To manually update, run:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
And that fixes it.
answered Feb 4 at 8:31
JohnJohn
263
add a comment |
So, the issue is in the 4.15.0-44-generic kernel and has been solved in the 4.15.0-45-generic. To manually update, run:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
And that fixes it.
answered Feb 4 at 8:31
JohnJohn
263
So, the issue is in the 4.15.0-44-generic kernel and has been solved in the 4.15.0-45-generic. To manually update, run:
sudo apt-get update
sudo apt-get upgrade
sudo apt-get dist-upgrade
And that fixes it.
answered Feb 4 at 8:31
JohnJohn
263
answered Feb 4 at 8:31
JohnJohn
263
answered Feb 4 at 8:31
JohnJohn
263
answered Feb 4 at 8:31
JohnJohn
263
263
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%2f1114350%2fubuntu-18-04-1-freezes-when-connecting-to-a-second-screen%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
1
I think you have similar problem with me. askubuntu.com/questions/1114052/paralel-monitor-problem
– Huseyin
Jan 31 at 10:05
1
I think is because of a bug in new update package. I am using 4.15.0-43-generic . please look here askubuntu.com/a/82144/139749
– Huseyin
Jan 31 at 10:09
It seems like this bug has not been fixed yet.
– d a i s y
Jan 31 at 10:10
Ok, so it seems it is known. Anything I can do to help with the developers' effort? Will they see this message for example?
– John
Jan 31 at 10:21
Please do consider Huseyin's comment as he said he had similar issue and also see this one too.
– d a i s y
Jan 31 at 10:34