fglrx 2:14.200-0ubuntu1: fglrx kernel module failed to build

[Luis E Quesada]

Before installed amd catalyst drivers on my Aspire V5-122P-0857 system crash and a black screen is what i had... Then I tryed to restore default driver and reinstall ubuntu-desktop and unity.
Now I don't I can see desktop background but unity apears to be damage or not function property.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3.8
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 3.16.0-33-generic
Date: Fri Mar 27 11:07:55 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx, 14.501.1003, 3.13.0-48-generic, x86_64: installed
 fglrx, 14.501.1003, 3.16.0-33-generic, x86_64: installed
 virtualbox, 4.3.10, 3.13.0-48-generic, x86_64: installed
 virtualbox, 4.3.10, 3.16.0-31-generic, x86_64: installed
 virtualbox, 4.3.10, 3.16.0-33-generic, x86_64: installed
DuplicateSignature: dkms:fglrx:2:14.200-0ubuntu1:/var/lib/dkms/fglrx/14.200/build/2.6.x/firegl_public.c:1787:5: error: incompatible types when returning type 'kuid_t' but 'KCL_TYPE_Uid' was expected
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:080d]
InstallationDate: Installed on 2015-02-20 (37 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: Acer Aspire V5-122P
PackageVersion: 2:14.200-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=2754a6b0-0101-49dd-86f4-7cc4b0b6d54f ro quiet splash vt.handoff=7
SourcePackage: fglrx-installer
Title: fglrx 2:14.200-0ubuntu1: fglrx kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.03
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire V5-122P
dmi.board.vendor: Acer
dmi.board.version: V2.03
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.03
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.03:bd05/02/2013:svnAcer:pnAspireV5-122P:pvrV2.03:rvnAcer:rnAspireV5-122P:rvrV2.03:cvnAcer:ct10:cvrV2.03:
dmi.product.name: Aspire V5-122P
dmi.product.version: V2.03
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.59+git20150318.d20413a7-0ubuntu0ricotz2~trusty
version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150318.27bf37ba-0ubuntu0ricotz~trusty
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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150318.bacaf7f1-0ubuntu0sarvatt~trusty
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
xserver.bootTime: Mon Mar 30 10:57:47 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: radeon

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