Xorg crash during login using additional TV at HDMI
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
login does loop.
Hardware changes, which is responsible:
add TV with HDMI
repeating error messages in dmesg:
[ 7.073512] nouveau [ PGRAPH]
[ 7.073527] nouveau 0000:01:00.0: Direct firmware load for nouveau/
[ 7.073531] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 7.073532] nouveau E[ PGRAPH]
[ 16.105932] nouveau [ PGRAPH]
[ 16.105941] nouveau 0000:01:00.0: Direct firmware load for nouveau/
[ 16.105945] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 16.105946] nouveau E[ PGRAPH]
[ 17.026449] sound hdaudioC1D0: HDMI: invalid ELD data byte 76
[ 17.103147] nouveau [ PGRAPH]
[ 17.103156] nouveau 0000:01:00.0: Direct firmware load for nouveau/
[ 17.103160] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 17.103162] nouveau E[ PGRAPH]
[ 18.003879] sound hdaudioC1D0: HDMI: invalid ELD data byte 74
[ 18.084568] nouveau [ PGRAPH]
[ 18.084583] nouveau 0000:01:00.0: Direct firmware load for nouveau/
[ 18.084590] nouveau 0000:01:00.0: Direct firmware load for nouveau/fuc409c failed with error -2
[ 18.084591] nouveau E[ PGRAPH]
[ 19.005339] sound hdaudioC1D0: HDMI: invalid ELD data byte 76
[ 19.098829] nouveau [ PGRAPH]
[ 19.098838] nouveau 0000:01:00.0: Direct firmware load for nouveau/
hardware (using lshw:)
*-display
bus info: pci@0000:01:00.0
bus info: pci@0000:01:00.1
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSign
Uname: Linux 3.19.0-18-generic x86_64
.tmp.unity.
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
CurrentDesktop: Unity
Date: Wed Jun 3 20:33:35 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Device [1458:362d]
InstallationDate: Installed on 2015-05-09 (24 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: MSI MS-7821
ProcKernelCmdLine: BOOT_IMAGE=
Renderer: Software
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.
dmi.board.name: Z87-G45 GAMING (MS-7821)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7821
dmi.product.
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.12.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Wed Jun 3 20:00:03 2015
xserver.configfile: default
xserver.devices:
input Power Button KEYBOARD, id 6
input Power Button KEYBOARD, id 7
input USB OPTICAL MOUSE MOUSE, id 8
input USB USB Keykoard KEYBOARD, id 9
input USB USB Keykoard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.
tags: | added: latest-bios-1.9 |
Anselm, 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 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 your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If that fails, one may open a terminal and file your report with 'ubuntu-bug /var/crash/ _my_crash_ report. crash' where _my_crash_ report. crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/ _my_crash_ report. crash'.
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/ErrorTracke r .
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 command line: crashdb. conf
sudo nano /etc/apport/
and comment out the line:
'problem_types': ['Bug', 'Package'],
by changing it to:
# 'problem_types': ['Bug', 'Package'],
Save, close, and try to file the crash report again via: _my_crash_ report. crash
ubuntu-bug /var/crash/
I'm closing this bug 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: /wiki.ubuntu. com/ReportingBu gs
https:/