fglrx gcc5 patch doesn't fix crash on 4.3 kernel

[TJ Buchanan]

fglrx-installer-updates (2:15.201-0ubuntu2~15.10.2) wily-proposed does not fix crash on startup on the 4.3 stable kernel. Installed from ubuntu mainline ppa.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: fglrx-updates-core 2:15.201-0ubuntu2~15.10.2
Uname: Linux 4.2.5-040205-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
BootLog:
 fsck from util-linux 2.26.2
 /dev/sda3: recovering journal
 /dev/sda3: clean, 387094/1204224 files, 1861663/4811520 blocks
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSKernelVersion: 4.3.0-040300rc7-generic
Date: Sun Nov 1 18:00:15 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 fglrx-updates-core, 15.201, 4.0.5-040005-generic, x86_64: installed
 fglrx-updates-core, 15.201, 4.2.5-040205-generic, x86_64: installed
 virtualbox, 5.0.4, 4.0.5-040005-generic, x86_64: installed
 virtualbox, 5.0.4, 4.2.5-040205-generic, x86_64: installed
DuplicateSignature: dkms:fglrx-updates-core:2:15.201-0ubuntu2~15.10.2:/var/lib/dkms/fglrx-updates-core/15.201/build/2.6.x/firegl_public.c:639:9: error: void value not ignored as it ought to be
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290] [1002:67b1] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0b00]
InstallationDate: Installed on 2015-10-23 (9 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
PackageVersion: 2:15.201-0ubuntu2~15.10.2
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.5-040205-generic root=UUID=e46d88f9-1a02-4f78-9ff3-fa4aeaf7e1c1 ro noprompt quiet splash
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5
 apt 1.0.10.2ubuntu1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.201-0ubuntu2~15.10.2: 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: 05/13/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.name: H97 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd05/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Mon Nov 2 11:51:58 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: fglrx

[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 1502978, 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.