xorg crash while switching between jedit and firefox

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

Bug Description

Xorg crashed when i switched from firefox to jedit, to further edit an HTML file, expected to just go back to jedit as normal, but xorg crashed instead, putting me back at the login screen.

ADDITIONAL INFO

apt-cache policy xorg
xorg:
  Installed: 1:7.7+1ubuntu8.1
  Candidate: 1:7.7+1ubuntu8.1
  Version table:
 *** 1:7.7+1ubuntu8.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1:7.7+1ubuntu8 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

Distribution Ubuntustudio 14.04 LTS

lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04

bug was not reported at time because of error below

Sorry, the program "Xorg" closed unexpectedly

Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-68.111-lowlatency 3.13.11-ckt27
Uname: Linux 3.13.0-68-lowlatency i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: XFCE
Date: Mon Nov 23 21:12:47 2015
InstallationDate: Installed on 2014-11-09 (379 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.1)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
CurrentDmesg:
 [ 28.499680] init: plymouth-upstart-bridge main process ended, respawning
 [ 28.539385] init: plymouth-upstart-bridge main process (1044) terminated with status 1
 [ 28.539415] init: plymouth-upstart-bridge main process ended, respawning
 [ 3742.241867] perf samples too long (2501 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
 [12639.566620] perf samples too long (5001 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
DistUpgraded: Fresh install
DistroCodename: trusty
DistroRelease: Ubuntu 14.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2a08]
   Subsystem: Hewlett-Packard Company Device [103c:2a08]
InstallationDate: Installed on 2014-11-09 (380 days ago)
InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.1)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:1064): WARNING **: Failed to load user image: Failed to open file '/home/shadowwraith/.face': No such file or directory
 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:4294): WARNING **: Failed to load user image: Failed to open file '/home/shadowwraith/.face': No such file or directory
 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
MachineType: HP Pavilion 061 PS258AA-ABU t819.uk
Package: xorg 1:7.7+1ubuntu8.1
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-68-lowlatency root=UUID=14666710-7816-48eb-a619-efd1b296c865 ro
ProcVersionSignature: Ubuntu 3.13.0-68.111-lowlatency 3.13.11-ckt27
Tags: trusty ubuntu
Uname: Linux 3.13.0-68-lowlatency i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/14/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.13
dmi.board.name: Grouper
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.13:bd12/14/2004:svnHPPavilion061:pnPS258AA-ABUt819.uk:pvr0qy0211RE101GROUP00:rvnASUSTeKComputerINC.:rnGrouper:rvr1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: PS258AA-ABU t819.uk
dmi.product.version: 0qy0211RE101GROUP00
dmi.sys.vendor: HP Pavilion 061
version.compiz: compiz 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: Tue Nov 24 14:26:57 2015
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Logitech USB Optical Mouse MOUSE, id 8
 input Logitech USB Keyboard KEYBOARD, id 9
 input Logitech USB Keyboard KEYBOARD, id 10
xserver.errors:

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

Revision history for this message
shadowwraith (tcmitchell957) wrote :
Revision history for this message
penalvch (penalvch) wrote :

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

Could you please run the following command once from a terminal as it will automatically gather and attach updated debug information to this report:
apport-collect -p xorg 1519104

Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
shadowwraith (tcmitchell957) wrote : BootDmesg.txt

apport information

tags: added: apport-collected ubuntu
description: updated
Revision history for this message
shadowwraith (tcmitchell957) wrote : BootLog.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : Dependencies.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : DpkgLog.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : LightdmDisplayLog.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : LightdmLog.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : Lspci.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : Lsusb.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : ProcEnviron.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : ProcInterrupts.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : ProcModules.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : UdevDb.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : UdevLog.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : XorgLog.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : XorgLogOld.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : Xrandr.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote : xdpyinfo.txt

apport information

Revision history for this message
shadowwraith (tcmitchell957) wrote :

should i attach info about jedit as well?

Revision history for this message
penalvch (penalvch) wrote :

shadowwraith, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

Revision history for this message
shadowwraith (tcmitchell957) wrote :

HP Pavilion t819.uk

intel Pentium 4 515 2.93ghz
1.7gb DDR ram
Intel GMA 900 128mb

Revision history for this message
penalvch (penalvch) wrote :

shadowwraith, after the crash, are there any crash files in /var/crash?

Changed in xorg (Ubuntu):
importance: Low → Medium
Revision history for this message
shadowwraith (tcmitchell957) wrote :

yes, there a file called _usr_bin_Xorg.0.crash, do i run it through apport or attach it?

Revision history for this message
penalvch (penalvch) wrote :

shadowwraith, 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.