[Bug 1948704] Re: segfault with gnome-shell & gdm-session-worker

2021-10-28 Thread Daniel van Vugt
OK I have now opened your gdm-session-worker crash formally in bug 1949127. If you want to report a crash of gnome-shell too then it will need a separate bug following: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - segfault with

[Bug 1948704] Re: segfault with gnome-shell & gdm-session-worker

2021-10-28 Thread Robert Kudyba
It ran for 47 hours and yes all tests passed ** Attachment added: "Screenshot of Memtest completed" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1948704/+attachment/5536844/+files/IMG_0332.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 1948704] Re: segfault with gnome-shell & gdm-session-worker

2021-10-28 Thread Daniel van Vugt
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948704 Title: segfault with gnome-shell & gdm-session-worker To manage notifications about t

[Bug 1948704] Re: segfault with gnome-shell & gdm-session-worker

2021-10-28 Thread Daniel van Vugt
That screenshot doesn't show that memory tests actually ran. Did you run the memory tests (which would take several hours)? Your crash has been recorded at https://errors.ubuntu.com/oops/0d1b7258-3816-11ec-ae83-fa163e102db1 but since it's the only crash of its kind I'm not yet sure that is valid.

[Bug 1948704] Re: segfault with gnome-shell & gdm-session-worker

2021-10-28 Thread Robert Kudyba
memtest showing now errors I uploaded the results of ubuntu-bug: cat /var/crash/_usr_lib_gdm3_gdm-session-worker.0.uploaded 0d1b7258-3816-11ec-ae83-fa163e102db1 Perhaps the stacktrace will help or perhaps warnings can be added if memory is suspected? Thread 3 (Thread 0x7f9f50e77700 (LWP 1292)): #

[Bug 1948704] Re: segfault with gnome-shell & gdm-session-worker

2021-10-25 Thread Daniel van Vugt
Thanks for the bug report. I think this looks like faulty RAM so the first thing you should do is run memory tests for a few hours by booting one of these tools: http://memtest.org/ https://www.memtest86.com/ If no memory errors are found then the next steps are outlined in: https://wiki.ub