** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: mesa (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Whoops, sorry, you are not the original reporter.
sfc: Please subscribe to bug 1731911 instead.
This bug remains about "intel_do_flush_locked failed: Bad address"
** This bug is no longer a duplicate of bug 1731911
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
Thanks. That is bug 1731911. Although what you're seeing with your
desktop is gnome-shell committing suicide as a result of Xwayland
crashing, so that is bug 1505409 or bug 1556601.
It would be most useful to you to track the root cause of the problem so
I'll mark this as a duplicate of bug
Today I got the coredump, but ubuntu-bug cannot upload it, saying
"ValueError ('not enough values to unpack (expected 2, got 1)',)". So I
use "ubuntu-bug xwayland" command, and attached the generated report.
This crash now seems only happens when the system is under load for some
time (in my case
Please don't attach crash files or core dumps to bugs. It is a security
risk for you, and not helpful to us. Instead use the 'ubuntu-bug'
command to upload .crash files automatically and securely.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
As for the log timestamp, mine is the same order as the themusicgod1's,
first intel_do_flush_locked, then xwayland connection lost. I'm using
journalctl -r to print the log, so the order is reversed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Thanks for your reply. Sometimes the crash will produce a huge coredump
in my home (~200MB), but I cannot find anything useful in it with gdb. I
will attach it when the next time it occurs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in
Also, it appears Mesa could be trying harder to handle the error without
taking down the whole process. At present Mesa will just kill the gnome-
shell process when the error occcurs:
if (ret != 0) {
fprintf(stderr, "intel_do_flush_locked failed: %s\n", strerror(-ret));
exit(1);
If we assume that "intel_do_flush_locked" is related to the gnome-shell
crash and this is a specific and not general duplicate of one of the
above bugs, the we should be looking in the package where
"intel_do_flush_locked" exists too. So that's the function
"do_flush_locked" in mesa's
10 matches
Mail list logo