session freezes/hangs after undetermined amount of time

[Nathanel Titane]

Currently using the default wayland session on 17.10: the computer eventually hangs/freezes after an undetermined amount of time, whether it'S still powered on and unused or when put on standby. Resuming the session is impossible as the device is frozen and needs to bee reset with power button.

Critical bug as the issues has provoked major data loss and work in progress loss.

Possibly a functional regression due to the use of wayland or the newer kernel provided with this release.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 4 12:29:03 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (15 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Please look in /var/crash for crashes. If there are none then log into a VT (if you can - Ctrl+Alt+F4) and run:

  killall -ABRT gnome-shell

Now look in /var/crash again. And upload the file using:

  ubuntu-bug /var/crash/_my_crash_report.crash

[Nathanel Titane (nathanel.titane)]

Here it is. Copied from /var/crash/ - original name _usr_bin_gnome-shell.1000.crash

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[Daniel van Vugt (vanvugt)]

Please upload the crash file using this command only:

  ubuntu-bug /var/crash/_my_crash_report.crash

[Nathanel Titane (nathanel.titane)]

Daniel,

the reason i copied the crash information and uploaded it is because apport (ubuntu-bug) seems to crash for no apparent reason when I try to get the file to the bug report.

I understand there are protocols to follow but your removal of the file is kind of counter productive...

[Daniel van Vugt (vanvugt)]

Sorry if you got a surprise. But there is nothing we can do with a crash file -- it needs to be analysed by the automatic upload procedure of 'ubuntu-bug'.

So aside from us not needing it, it is potentially a security risk for you leaving the crash file there as any crash file could contain passwords or other sensitive data. An alternative approach is to mark the bug itself as Private to keep such attachments fairly private, but in this case we didn't need to keep the attachment.

I know ubuntu-bug/apport does crash in some cases, which blocks us from getting bug reports. This is a significant issue which I have tried to make more people aware of (see bug 1552577).

When 'ubuntu-bug' fails do you find it leaves its own crash file in /var/crash? Or can you see any evidence of your system reporting apport crashes on the page that this command opens?...

xdg-open "https://errors.ubuntu.com/user/"`sudo cat /var/lib/whoopsie/whoopsie-id`

[Daniel van Vugt (vanvugt)]

Actually that gives me an idea. What if you use 'apport-cli' in place of 'ubuntu-bug'. Does it work then?

[Nathanel Titane (nathanel.titane)]

Thank you for clarifying Dniel.

Both instances crash regardless. apport does leave a crash file under /var/crash/ as well...

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]