After I exit a game on steam, I did a system update and the crash apperd.

[ahmed nasir al abboudi]

I believe that the crash is related for the Nvidia driver not been compatible kernel update that I did today.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 346.59 Tue Mar 31 14:10:31 PDT 2015
 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
DKMSKernelVersion: 3.19.0-26-generic
Date: Tue Aug 18 14:25:30 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation Device [10de:1073]
InstallationDate: Installed on 2015-07-15 (34 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Gigabyte Technology Co., Ltd. PH67A-UD3-B3
PackageVersion: 2:15.200-0ubuntu4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=e0df2d08-88a0-4271-b94d-b88ade2062af ro quiet splash
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt 1.0.9.7ubuntu4.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module failed to build
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: PH67A-UD3-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnPH67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnPH67A-UD3-B3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: PH67A-UD3-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Tue Aug 18 14:26:26 2015
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Microsoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 8
 input Microsoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 9
 input Microsoft Microsoft® 2.4GHz Transceiver v8.0 KEYBOARD, id 10
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.1-0ubuntu3

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Alex B. (barringer-coding)]

The only work around that I have found is to go back to your old kernel that was installed.

In this case, it's usually this one:

3.19.0-15-generic

The work around (in terminal /konsole):

The offending packages are the following that cause that error:

linux-headers-3.19.0-26
linux-headers-3.19.0-26-generic
linux-image-3.19.0-26-generic
linux-image-extra-3.19.0-26-generic

The old packages for the older kernel when it did work:

linux-headers-3.19.0-15
linux-headers-3.19.0-15-generic
linux-image-3.19.0-15-generic
linux-image-extra-3.19.0-15-generic

What you do is this (if it says they're already installed don't worry, this is also for people those purged these packages from before):

sudo apt-get update
sudo apt-get install -y linux-headers-3.19.0-15 linux-headers-3.19.0-15-generic linux-image-3.19.0-15-generic linux-image-extra-3.19.0-15-generic
sudo apt-get purge -y linux-headers-3.19.0-26 linux-headers-3.19.0-26-generic linux-image-3.19.0-26-generic linux-image-extra-3.19.0-26-generic
sudo update-grub2

When this is done, you might get an error about the grub hidden timeout being set to a non zero number is no longer supported, that's not a real problem, I can tell you how to fix it if it really bothers you, though.

Now, that all of this is done:

Close all your open applications and type in:

sudo reboot

When Ubuntu and forks reboots, login or let the auto login script bring you to the desktop.

Assuming you have the AMD / ATI Catalyst installed: (in terminal / konsole):

sudo amdcccle

When it opens, check all your setting and if you need to make changes do so at this time, since you're running as a super user, you can also change the resolution should you feel you need to do this at this time. When done, close that application and start Steam.

 From here, you should be fine. Just make sure that when you go to update your system, to not allow that bad kernel to be installed onto your system again. I recommend using Synaptic package manager to deal with unruly packages. You can pick and choose what packages are updated and which are left well enough alone.

I hope this helps!

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1479913, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.