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 problem with the old crash file, probably since
it wrongly generated or?

Thanks and sry for this non-default setup.

Here is the additional system information:

ulimit -a
    core file size          (blocks, -c) 0
    data seg size           (kbytes, -d) unlimited
    scheduling priority             (-e) 0
    file size               (blocks, -f) unlimited
    pending signals                 (-i) 62722
    max locked memory       (kbytes, -l) 16384
    max memory size         (kbytes, -m) unlimited
    open files                      (-n) 1024
    pipe size            (512 bytes, -p) 8
    POSIX message queues     (bytes, -q) 819200
    real-time priority              (-r) 0
    stack size              (kbytes, -s) 8192
    cpu time               (seconds, -t) unlimited
    max user processes              (-u) 62722
    virtual memory          (kbytes, -v) unlimited
    file locks                      (-x) unlimited

cat /proc/sys/kernel/core_pipe_limit
    0

should be enough space on /: df -h
    Filesystem      Size  Used Avail Use% Mounted on
    udev            7,7G     0  7,7G   0% /dev
    tmpfs           1,6G   10M  1,6G   1% /run
    /dev/nvme0n1p6  246G   39G  195G  17% /
    tmpfs           7,8G   41M  7,7G   1% /dev/shm
    tmpfs           5,0M  4,0K  5,0M   1% /run/lock
    tmpfs           7,8G     0  7,8G   0% /sys/fs/cgroup
    /dev/loop0      3,8M  3,8M     0 100% /snap/gnome-system-monitor/39
    /dev/loop3      140M  140M     0 100% /snap/gnome-3-26-1604/64
    /dev/loop4      141M  141M     0 100% /snap/gnome-3-26-1604/59
    /dev/loop2      3,4M  3,4M     0 100% /snap/gnome-system-monitor/36
    /dev/loop1       21M   21M     0 100% /snap/gnome-logs/25
    /dev/loop5      1,7M  1,7M     0 100% /snap/gnome-calculator/154
    /dev/loop6       87M   87M     0 100% /snap/core/4486
    /dev/loop7      2,4M  2,4M     0 100% /snap/gnome-calculator/167
    /dev/loop8       87M   87M     0 100% /snap/core/4571
    /dev/loop9       22M   22M     0 100% /snap/gnome-logs/31
    /dev/loop11      13M   13M     0 100% /snap/gnome-characters/86
    /dev/loop10      13M   13M     0 100% /snap/gnome-characters/69
    /dev/loop12      87M   87M     0 100% /snap/core/4650
    /dev/loop13     141M  141M     0 100% /snap/gnome-3-26-1604/62
    /dev/nvme0n1p2   96M   29M   68M  30% /boot/efi
    /dev/nvme0n1p7  473G  236G  238G  50% /media/thorsten/daten
    tmpfs           1,6G   20K  1,6G   1% /run/user/119
    tmpfs           1,6G  7,1M  1,6G   1% /run/user/1000

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772638

Title:
  segfault in libmutter-2.so after suspend/resume using wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772638/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to