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

** Changed in: xorg-server (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  Xorg crash report after resume

Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  Crash Report when resuming from sleep.
  Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223
  This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 
970M, driver 390.77
  The crash log doesn't have much info in it IMO, but I uploaded here 
http://s000.tinyupload.com/?file_id=09497843963607449328

  Output from sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
  4.6.5
  11/14/2014

  Output from uname -a
  Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux

  Output from cat /etc/*ase
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"
  NAME="Ubuntu"
  VERSION="18.04.1 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.1 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  Output from lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
DRAM Controller (rev 06)
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor 
PCI Express x16 Controller (rev 06)
  00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor 
Integrated Graphics Controller (rev 06)
  00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller (rev 06)
  00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB xHCI (rev 05)
  00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #2 (rev 05)
  00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High 
Definition Audio Controller (rev 05)
  00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #1 (rev d5)
  00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #2 (rev d5)
  00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #3 (rev d5)
  00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI 
Express Root Port #4 (rev d5)
  00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family 
USB EHCI #1 (rev 05)
  00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
  00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset 
Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
  00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus 
Controller (rev 05)
  01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 
970M] (rev a1)
  03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI 
Bridge [Cheetah Express] (rev 01)
  04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b 
OHCI Controller [Cheetah Express] (rev 01)
  05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI 
Express Card Reader (rev 01)
  05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a)
  06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  The nuisance inspired me to create a script on the desktop called 
ClearCrashLog.sh (info I got from a YouTube video)
  ls /var/crash
  sudo rm /var/crash/*

  It's annoying to have to type the password every time, but since root owns 
the crash log it's necessary.
  I've used Lubuntu for years.  My prior laptop was a Sager with an AMD card.  
It had the same sort of issue versions ago.  I got in the habit of just 
clicking it away.  I think that the Report Crash fails because the log is owned 
by root and I don't have rights to it.  Perhaps adding myself to the whoopsie 
group would resolve that (and needing sudo to delete too), so I think I'll try 
that.
  It's the only thing about Lubuntu that would be a turn off to new users. 

  It's not a high priority thing, because the system works just fine.
  But it is a nuisance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to