*** This bug is a duplicate of bug 1754949 ***
https://bugs.launchpad.net/bugs/1754949
Thanks.
Your new crash report is a known issue (bug 1754949):
https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
So this is now a duplicate of bug 1754949.
** This bug has been mar
Hi, i reinstalled my system and tried to reproduced the bug and switch
from xorg to wayland session. I think that this time i was able to sent
a complete crash report:
https://errors.ubuntu.com/oops/415ba0dc-7077-11e8-997a-fa163e192766
I don't know whether the new system install or the updates to
beatmaggy, please try following the instructions in:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
gnome-shell[1493]: segfault at 20 ip 7fe7ecafeb17 sp
7fff5e70ba60 error 4 in libmutter-2.so.0.0.0[7fe7eca11000+156000]
I have this exact segfault too. I’m on a cherry trail atom z8350.
Previously this segfault didn’t occur and the system went to suspend and it
could be brought up via key
... because what we see from your crashes is:
UnreportableReason
Invalid core dump: BFD: warning: /tmp/apport_core_r0cnuvqg is truncated:
expected core file size >= 923877376, found: 1114112
UnreportableReason
Invalid core dump: BFD: warning: /tmp/apport_core_8lexsvus is truncated:
I wonder if the truncated core files are a bug in apport? Maybe apport's
not waiting long enough for the core files to be written. They should be
around 1GB each.
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
okay, sry the bug still occurs just far less frequently (1 out of 100 or
so). As stated above i am now using /bin/bash as login shell but i still
cannot submit a crash file.
This time an unhandled exception occurs in the apport log
(/var/log/apport.log)
so the segfault in the dmesg was
gnome-shel