Xwayland crashes frequently
My system is running Ubuntu 18.04 LTS. I am facing this bug every time I turn on my pc and when my PC wakes up after sleep. Unfortunately, I found no solution when I searched on Launchpad and Bugzilla.
I have also reported this error every time(1000+ times now) I get it, no fixes yet. In spite of the Xwayland crash, I can successfully login via GDM3 and use Gnome desktop without any problem, but I am not able to resume my work when my PC wakes from sleep (this hurts).
Error details:
Executable path: /usr/bin/Xwayland
Package: xwayland 2:1.19.6-1ubuntu4
Problem Type: Crash
Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
ApportVersion: 2.20.9-0ubuntu72
Architecture: amd64
Machine Type: ASUSTeK COMPUTER INC. GL552JX.
For Bootlog, CurrentDmesg: I will share it when requested via a drive link because it is huge to be posted as text.
Update: The error occurs only when my system is using Intel integrated graphics(Intel Iris Pro 5200). So, temporarily to avoid the error, I have switched to Nvidia Graphics(Nvidia GTX 950M, Driver version: 390.87), no errors since then. But, Dedicated GPU rapidly consumes my laptop battery, I would prefer to use Intel Graphics if the error gets solved.
ubuntu login wayland plymouth
|
show 2 more comments
My system is running Ubuntu 18.04 LTS. I am facing this bug every time I turn on my pc and when my PC wakes up after sleep. Unfortunately, I found no solution when I searched on Launchpad and Bugzilla.
I have also reported this error every time(1000+ times now) I get it, no fixes yet. In spite of the Xwayland crash, I can successfully login via GDM3 and use Gnome desktop without any problem, but I am not able to resume my work when my PC wakes from sleep (this hurts).
Error details:
Executable path: /usr/bin/Xwayland
Package: xwayland 2:1.19.6-1ubuntu4
Problem Type: Crash
Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
ApportVersion: 2.20.9-0ubuntu72
Architecture: amd64
Machine Type: ASUSTeK COMPUTER INC. GL552JX.
For Bootlog, CurrentDmesg: I will share it when requested via a drive link because it is huge to be posted as text.
Update: The error occurs only when my system is using Intel integrated graphics(Intel Iris Pro 5200). So, temporarily to avoid the error, I have switched to Nvidia Graphics(Nvidia GTX 950M, Driver version: 390.87), no errors since then. But, Dedicated GPU rapidly consumes my laptop battery, I would prefer to use Intel Graphics if the error gets solved.
ubuntu login wayland plymouth
I am asking this question on StackExchange because I am hoping for an answer due to its large number of users compared to actual bug report sites, For more details please ask it in comments I will share the logs via drive link.
– FutureJJ
Aug 2 '18 at 10:13
I am facing the same problem. It does not happen at every wake, though, only like 30% of the time.
– Nicolas Raoul
Aug 2 '18 at 10:26
What GPU manufacture do you have?
– Ilia Rostovtsev
Nov 8 '18 at 15:00
@IliaRostovtsev It's Intel Iris Pro 5200 + Dedicated Nvidia GTX 950M. This Wayland error appears when I switch to Intel Graphics. I do not get any error while my system is using Nvidia GPU.
– FutureJJ
Nov 8 '18 at 17:58
@FutureJJ ..and you don't use Nvidia proprietary driver, correct?
– Ilia Rostovtsev
Nov 8 '18 at 21:06
|
show 2 more comments
My system is running Ubuntu 18.04 LTS. I am facing this bug every time I turn on my pc and when my PC wakes up after sleep. Unfortunately, I found no solution when I searched on Launchpad and Bugzilla.
I have also reported this error every time(1000+ times now) I get it, no fixes yet. In spite of the Xwayland crash, I can successfully login via GDM3 and use Gnome desktop without any problem, but I am not able to resume my work when my PC wakes from sleep (this hurts).
Error details:
Executable path: /usr/bin/Xwayland
Package: xwayland 2:1.19.6-1ubuntu4
Problem Type: Crash
Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
ApportVersion: 2.20.9-0ubuntu72
Architecture: amd64
Machine Type: ASUSTeK COMPUTER INC. GL552JX.
For Bootlog, CurrentDmesg: I will share it when requested via a drive link because it is huge to be posted as text.
Update: The error occurs only when my system is using Intel integrated graphics(Intel Iris Pro 5200). So, temporarily to avoid the error, I have switched to Nvidia Graphics(Nvidia GTX 950M, Driver version: 390.87), no errors since then. But, Dedicated GPU rapidly consumes my laptop battery, I would prefer to use Intel Graphics if the error gets solved.
ubuntu login wayland plymouth
My system is running Ubuntu 18.04 LTS. I am facing this bug every time I turn on my pc and when my PC wakes up after sleep. Unfortunately, I found no solution when I searched on Launchpad and Bugzilla.
I have also reported this error every time(1000+ times now) I get it, no fixes yet. In spite of the Xwayland crash, I can successfully login via GDM3 and use Gnome desktop without any problem, but I am not able to resume my work when my PC wakes from sleep (this hurts).
Error details:
Executable path: /usr/bin/Xwayland
Package: xwayland 2:1.19.6-1ubuntu4
Problem Type: Crash
Title: Xwayland crashed with signal 7 in mieqProcessDeviceEvent()
ApportVersion: 2.20.9-0ubuntu72
Architecture: amd64
Machine Type: ASUSTeK COMPUTER INC. GL552JX.
For Bootlog, CurrentDmesg: I will share it when requested via a drive link because it is huge to be posted as text.
Update: The error occurs only when my system is using Intel integrated graphics(Intel Iris Pro 5200). So, temporarily to avoid the error, I have switched to Nvidia Graphics(Nvidia GTX 950M, Driver version: 390.87), no errors since then. But, Dedicated GPU rapidly consumes my laptop battery, I would prefer to use Intel Graphics if the error gets solved.
ubuntu login wayland plymouth
ubuntu login wayland plymouth
edited Nov 10 '18 at 3:54
FutureJJ
asked Aug 2 '18 at 10:12
FutureJJFutureJJ
1386
1386
I am asking this question on StackExchange because I am hoping for an answer due to its large number of users compared to actual bug report sites, For more details please ask it in comments I will share the logs via drive link.
– FutureJJ
Aug 2 '18 at 10:13
I am facing the same problem. It does not happen at every wake, though, only like 30% of the time.
– Nicolas Raoul
Aug 2 '18 at 10:26
What GPU manufacture do you have?
– Ilia Rostovtsev
Nov 8 '18 at 15:00
@IliaRostovtsev It's Intel Iris Pro 5200 + Dedicated Nvidia GTX 950M. This Wayland error appears when I switch to Intel Graphics. I do not get any error while my system is using Nvidia GPU.
– FutureJJ
Nov 8 '18 at 17:58
@FutureJJ ..and you don't use Nvidia proprietary driver, correct?
– Ilia Rostovtsev
Nov 8 '18 at 21:06
|
show 2 more comments
I am asking this question on StackExchange because I am hoping for an answer due to its large number of users compared to actual bug report sites, For more details please ask it in comments I will share the logs via drive link.
– FutureJJ
Aug 2 '18 at 10:13
I am facing the same problem. It does not happen at every wake, though, only like 30% of the time.
– Nicolas Raoul
Aug 2 '18 at 10:26
What GPU manufacture do you have?
– Ilia Rostovtsev
Nov 8 '18 at 15:00
@IliaRostovtsev It's Intel Iris Pro 5200 + Dedicated Nvidia GTX 950M. This Wayland error appears when I switch to Intel Graphics. I do not get any error while my system is using Nvidia GPU.
– FutureJJ
Nov 8 '18 at 17:58
@FutureJJ ..and you don't use Nvidia proprietary driver, correct?
– Ilia Rostovtsev
Nov 8 '18 at 21:06
I am asking this question on StackExchange because I am hoping for an answer due to its large number of users compared to actual bug report sites, For more details please ask it in comments I will share the logs via drive link.
– FutureJJ
Aug 2 '18 at 10:13
I am asking this question on StackExchange because I am hoping for an answer due to its large number of users compared to actual bug report sites, For more details please ask it in comments I will share the logs via drive link.
– FutureJJ
Aug 2 '18 at 10:13
I am facing the same problem. It does not happen at every wake, though, only like 30% of the time.
– Nicolas Raoul
Aug 2 '18 at 10:26
I am facing the same problem. It does not happen at every wake, though, only like 30% of the time.
– Nicolas Raoul
Aug 2 '18 at 10:26
What GPU manufacture do you have?
– Ilia Rostovtsev
Nov 8 '18 at 15:00
What GPU manufacture do you have?
– Ilia Rostovtsev
Nov 8 '18 at 15:00
@IliaRostovtsev It's Intel Iris Pro 5200 + Dedicated Nvidia GTX 950M. This Wayland error appears when I switch to Intel Graphics. I do not get any error while my system is using Nvidia GPU.
– FutureJJ
Nov 8 '18 at 17:58
@IliaRostovtsev It's Intel Iris Pro 5200 + Dedicated Nvidia GTX 950M. This Wayland error appears when I switch to Intel Graphics. I do not get any error while my system is using Nvidia GPU.
– FutureJJ
Nov 8 '18 at 17:58
@FutureJJ ..and you don't use Nvidia proprietary driver, correct?
– Ilia Rostovtsev
Nov 8 '18 at 21:06
@FutureJJ ..and you don't use Nvidia proprietary driver, correct?
– Ilia Rostovtsev
Nov 8 '18 at 21:06
|
show 2 more comments
1 Answer
1
active
oldest
votes
As a root/admin user use vi/vim editor to perform the following changes of the GDM3 custom configuration file
/etc/gdm3/custom.conf
From:
#WaylandEnable=false
To:
WaylandEnable=false
By uncommenting the above line your system will use the Xorg display manager instead of Wayland next time it boots. Just do a reboot and you are done :).
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460041%2fxwayland-crashes-frequently%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
As a root/admin user use vi/vim editor to perform the following changes of the GDM3 custom configuration file
/etc/gdm3/custom.conf
From:
#WaylandEnable=false
To:
WaylandEnable=false
By uncommenting the above line your system will use the Xorg display manager instead of Wayland next time it boots. Just do a reboot and you are done :).
New contributor
add a comment |
As a root/admin user use vi/vim editor to perform the following changes of the GDM3 custom configuration file
/etc/gdm3/custom.conf
From:
#WaylandEnable=false
To:
WaylandEnable=false
By uncommenting the above line your system will use the Xorg display manager instead of Wayland next time it boots. Just do a reboot and you are done :).
New contributor
add a comment |
As a root/admin user use vi/vim editor to perform the following changes of the GDM3 custom configuration file
/etc/gdm3/custom.conf
From:
#WaylandEnable=false
To:
WaylandEnable=false
By uncommenting the above line your system will use the Xorg display manager instead of Wayland next time it boots. Just do a reboot and you are done :).
New contributor
As a root/admin user use vi/vim editor to perform the following changes of the GDM3 custom configuration file
/etc/gdm3/custom.conf
From:
#WaylandEnable=false
To:
WaylandEnable=false
By uncommenting the above line your system will use the Xorg display manager instead of Wayland next time it boots. Just do a reboot and you are done :).
New contributor
New contributor
answered 4 mins ago
user343026user343026
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f460041%2fxwayland-crashes-frequently%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
I am asking this question on StackExchange because I am hoping for an answer due to its large number of users compared to actual bug report sites, For more details please ask it in comments I will share the logs via drive link.
– FutureJJ
Aug 2 '18 at 10:13
I am facing the same problem. It does not happen at every wake, though, only like 30% of the time.
– Nicolas Raoul
Aug 2 '18 at 10:26
What GPU manufacture do you have?
– Ilia Rostovtsev
Nov 8 '18 at 15:00
@IliaRostovtsev It's Intel Iris Pro 5200 + Dedicated Nvidia GTX 950M. This Wayland error appears when I switch to Intel Graphics. I do not get any error while my system is using Nvidia GPU.
– FutureJJ
Nov 8 '18 at 17:58
@FutureJJ ..and you don't use Nvidia proprietary driver, correct?
– Ilia Rostovtsev
Nov 8 '18 at 21:06