Xorg freeze

Bug #1518614 reported by NoBugs!
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Shortly after plugging in iPad, screen froze (not mouse cursor though). Ctrl+alt+F2 let me killall firefox, killall nautilus, yet it still showed Firefox on the screen, and still was frozen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Nov 21 10:55:31 2015
DistUpgraded: 2014-04-19 04:44:12,758 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.7, 3.19.0-33-generic, x86_64: installed
 nvidia-340, 340.96, 3.19.0-33-generic, x86_64: installed
 vboxhost, 5.0.2, 3.19.0-33-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:054e]
InstallationDate: Installed on 2013-11-23 (728 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. XPS L521X
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic root=UUID=8e997c12-0ee0-422b-a7e4-a7cb0a74f38f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: Xorg freeze
UpgradeStatus: Upgraded to trusty on 2014-04-19 (581 days ago)
dmi.bios.date: 12/17/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 0C5Y96
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A16
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/17/2013:svnDellInc.:pnXPSL521X:pvrA16:rvnDellInc.:rn0C5Y96:rvrA00:cvnDellInc.:ct8:cvrA16:
dmi.product.name: XPS L521X
dmi.product.version: A16
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Nov 16 12:37:37 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 4333
 vendor AUO
xserver.version: 2:1.15.1-0ubuntu2.7

Revision history for this message
NoBugs! (luke32j) wrote :
Revision history for this message
penalvch (penalvch) wrote :

NoBugs!, thank you for reporting this and helping make Ubuntu better.

To clarify, are there any crash files in /var/crash?

tags: added: latest-bios-a16
Changed in xorg (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
NoBugs! (luke32j) wrote :

Yes there are crash reports in /var/crash:

-rw-r----- 1 3.2M Nov 21 10:58 _usr_bin_compiz.1000.crash
-rw-r----- 1 575K Nov 21 10:52 _usr_lib_upower_upowerd.0.crash

Revision history for this message
penalvch (penalvch) wrote :

NoBugs!, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart. Now reproduce the crash, then open a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

If you do open this report, please feel free to subscribe me to it.

However, I'm closing this report since the process outlined above will deal with this issue more efficiently. Also, please do not attach your crash report manually to this report and reopen it. Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
importance: Medium → Undecided
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.