Interesting that errors.ubuntu.com is showing zero reports of this crash
in 19.04, and zero reports in the final release version of Xorg for
18.10 onward. But those same Xorg versions are crashing in 18.04. So I
would have to conclude that this was fixed in mutter in Ubuntu 18.10
onward.
** Also
Just tidying up this bug...
Although this is the top Xwayland crash, I'm now thinking we need to
lower its priority. The reason is that this crash is only a side-effect
of the gnome-shell process going away and not really a bug in Xwayland.
One could argue that Xwayland still shouldn't crash in
I think I'm experiencing the same problem. I installed Ubuntu 18.04
beta last Tuesday. When I power on my computer, the screen blinks 50-53
times over the span of 2-1/2 minutes (this is perfectly reproducible)
and then for the rest of the session, everything works flawlessly.
After LinuxFest
Bump. This bug is the top Xwayland crash by an order of magnitude:
https://errors.ubuntu.com/?package=xwayland=month
** Changed in: xorg-server (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I'm still seeing crashes under the exact same conditions as since
October. When I do ubuntu-bug on the crash file it directs me here, so I
think this bug may still be getting triggered for me at least.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I think there are going to be multiple ways this Xwayland crash could be
triggered. Also we don't seem to have fully deduplicated similar crashes yet:
https://bugs.launchpad.net/ubuntu/+source/xorg-server
So I think it's most helpful to keep this bug open and findable for now.
** Changed in:
Crashed at the same time as I got "gnome-shell crashed with SIGSEGV in
cogl_object_unref()" after entering xorg session from the gnome-greeter
lock-screen. I am not sure if it is related but I had problems with the
wayland sessions crashing in the begining, until I changed to single
monitor in the
I'm on Ubuntu 18.04, still beta, but fully updated, with dual screens on
two AMD R9 390, and it keeps happening after each login / screen unlock.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
@Kir Kolyshkin - did trying the commits on the master branch of mutter
after 3.26 fix this?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1731911
Title:
Xwayland crashed with
Crash occurs every time I turn the monitor off, in my case. Motherb.:
Asrock J4205-itx (Intel HD graphics 505)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1731911
Title:
Crash still occurs every time I turn my monitor back on, as has been the
case since October.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1731911
Title:
Xwayland crashed with
My bug was duped to this one. After dist-upgrading 18.04 yesterday I
consistently get a crash logging into any gnome sessions, only the unity
session doesn't crash on me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1731911
Title:
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError()
This bug bite me on a daily basis, too (in Artful). I'm currently
testing if the fix from Fedora (a cumulative patch of the first 30+
commits landed in mutter-3.26 branch after mutter-3.26.2 release) helps.
Will report back soon.
--
You received this bug notification because you are a member of
I experienced this crash today. Looking at dmesg the only suspicious
line I found was this one:
[397641.528873] traps: gnome-shell[11133] general protection
ip:7f5498d62de2 sp:7ffdd8da76f0 error:0 in
libgobject-2.0.so.0.5400.1[7f5498d2d000+52000]
--
You received this bug notification because
This bug still not fixed, adding a core dump and this might have
relations to bug #1743732 because if you turn the monitor off or lock
the screen, everything in that session are lost. Daniel van Vugt asked
to move that bug to private.
Core was generated by `/usr/bin/Xwayland :0 -rootless
OK, if that's the fix then we'll get it in mutter 3.26.3. Now looking
forward to that one even more.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1731911
Title:
Xwayland crashed
** Changed in: mutter (Fedora)
Status: Unknown => Fix Committed
** Changed in: mutter (Fedora)
Importance: Unknown => Undecided
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
the fedora bug says it's a bug in mutter, fixed by
https://git.gnome.org/browse/mutter/commit/?h=gnome-3-26=cde5454622d99320a66f2fd352df132a4bfdab4b
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Status: Confirmed =>
20 matches
Mail list logo
