Thanks for the bug report. Unfortunately Javascript errors are not the
same thing as a gnome-shell crash. To help us find the cause of the
crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1791899

Title:
  gnome crashes, all running applications are closed (even vpn, etc)

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Sep 11 09:27:10 edbwp400322 gnome-shell[1593]: JS ERROR: TypeError: 
this._currentWindow is 
null#012_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
  Sep 11 09:27:10 edbwp400322 gnome-shell[1593]: JS ERROR: TypeError: 
this._currentWindow is 
null#012_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
  Sep 11 09:27:10 edbwp400322 systemd-udevd[11383]: link_config: 
autonegotiation is unset or enabled, the speed and duplex are not writable.
  Sep 11 09:27:10 edbwp400322 systemd-udevd[11383]: link_config: could not get 
ethtool features for cscotun0
  Sep 11 09:27:10 edbwp400322 systemd-udevd[11383]: Could not set offload 
features of cscotun0: No such device
  Sep 11 09:27:11 edbwp400322 NetworkManager[1291]: <info>  [1536650831.0082] 
devices added (path: /sys/devices/virtual/net/cscotun0, iface: cscotun0)
  Sep 11 09:27:11 edbwp400322 NetworkManager[1291]: <info>  [1536650831.0083] 
device added (path: /sys/devices/virtual/net/cscotun0, iface: cscotun0): no 
ifupdown configuration found.
  Sep 11 09:27:11 edbwp400322 NetworkManager[1291]: <info>  [1536650831.0142] 
devices removed (path: /sys/devices/virtual/net/cscotun0, iface: cscotun0)
  Sep 11 09:27:11 edbwp400322 gnome-shell[1593]: JS ERROR: TypeError: 
this._currentWindow is 
null#012_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
  Sep 11 09:27:11 edbwp400322 gnome-shell[1593]: message repeated 4 times: [ JS 
ERROR: TypeError: this._currentWindow is 
null#012_setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 11 09:32:31 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-08-17 (389 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-05-10 (123 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to