*** 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
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
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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
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
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
... 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:
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
At a guess, probably some Bourne shell script used in suspend/resume is
missing the line '#!/bin/sh' at its top. That would cause the script to
fail if you changed default shell.
I have no idea where to start looking for such a mistake though.
** Summary changed:
- segfault in libmutter-2.so
okay its definitely associated with zsh as login shell. I now have >50
successful resume/suspends.
So to summarize:
- mutter crashes in 1 out of 10 suspend/resumes when zsh is set as login shell
- however, i cannot use apport to get a crash log due to zsh
-> i cannot get both apport (requires
Hi,
i switched my login shell back to bash (chsh -s /bin/bash) and i was not
able to reproduce the issue in ~30 resume/suspend cycles. This is still
no valid statistic but is it possible that zsh as login shell can
segfault mutter? Of course, I will report if it occurs!
ubuntu-bug still has the
Hi, thanks for the answer. My problem is always something like "The
problem cannot be reported: Invalid core dump: BFD: warning
/tmp/apport_core_ersfx7ym is truncated: expected core file size >=
846290944, found: 216288" (the size mentioned after found differs.)
I found my crash to be reported at
I notice you're using zsh... I vaguely recall other people having
trouble with crash reports related to that. Maybe try resetting your
default shell to /bin/bash
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Unfortunately we can't do anything with such invalid core files. What we
can do is try to make them valid in future...
Please run 'ulimit -a' and send us the output.
And please do the same for 'cat /proc/sys/kernel/core_pipe_limit'.
Is your system low on disk space at all? (run 'df -h')
--
apport information
** Tags added: apport-collected bionic wayland-session
** Description changed:
Hi,
i have the problem when running the gnome wayland session in ubuntu
18.04 that in ~1 out of 5 resume/suspend cycles a segfault in
libmutter-2.so occurs which then kills my current
Sorry but we can't diagnose a crash without a crash report, as outlined in the
standard response:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
If you do not find success from following those steps then the next step
I suggest is to look up automatic
15 matches
Mail list logo
