Attempting to enable multi-screen mode via amdcccle (with screen 1 to the right of screen 2) causes X to crash severely, as soon as you hit "OK" or "Apply"

Bug #1486673 reported by Rich.T.
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Fix Released
Undecided
Rich.T.

Bug Description

This bug relates directly with https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1479913 (caused by the recent 3.19.0-26 kernel roll-out).

I have implemented the fix, by enabling the "Proposed" repository and also switching to "fglrx updates" but this only worsened the problem as this has caused an issue whereby my system hangs, solid, right at the login screen, when I boot into 3.19.0-26.

When I boot into an earlier kernel build, the problem is not present, but no matter what I try doing; ie. uninstalling flgrx; using xserver-xorg-video-ati; reinstalling fglrx; reinstalling the new kernel; reinstalling xorg; changing the screen configuration; changing and removing monitors and their configuration; the system still hangs on booting into 3.19.0-26.

I have noticed that when I boot into a working kernel however; the login screen seems to still have my old monitor configuration ie. with screen 1 to the right of screen 2, even if, upon logging in, the monitors are configured differently.

I have reported this under the above summary because at least one other user has reported this same behavior (https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1479913/comments/51) and I believe that this has the same root cause as my problem.

As to why the login screen keeps defaulting to my old configuration, I do not know (perhaps a problem with lightdm, or somthing), but the only option that seems left open to me at the moment is a full reinstall, which I would really like to avoid at the moment; at least until Wily comes out.

Sorry to be so long winded, but this seems to be quite a serious issue and I would like it to be resolved.

Thank you,
Rich

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1.3
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
Date: Wed Aug 19 17:49:01 2015
DistUpgraded: Fresh install
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:174b]
InstallationDate: Installed on 2014-11-23 (269 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=ac803c35-9f47-487f-ac09-c35efe8d953f ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1503
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid1
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: Wed Aug 19 17:18:40 2015
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Logitech USB Receiver KEYBOARD, id 8
 input Logitech USB Receiver KEYBOARD, id 9
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: fglrx

Revision history for this message
Rich.T. (rich.t.) wrote :
Revision history for this message
Rich.T. (rich.t.) wrote :

Update: This issue is still not resolved on my system, and I am still stuck on pre-3.19.0-26 kernels.

However, I managed to find an unused SSD knocking around and so I installed a fresh copy of Ubuntu 14.04 to this drive, immediately dist-upgrade-ed, successfully rebooted and logged in, installed flgrx-updates and then successfully rebooted and logged in fine again.

There was no sign of the freezing-up on the login screen this time.

I don't know what happened; whether there was some sort of corruption as a result of the whole process, or whatever; but it looks as though I'm going to have to re-install Ubuntu and migrate all of my settings, fine-tunings, custom scripts, programs and repositories across to the new system.

I'm not happy, but such is life...

I'll mark this bug as closed, but I'm going to link to it in the fglrx-installer bug for future reference.

Thanks,
Rich

Revision history for this message
Rich.T. (rich.t.) wrote :
Changed in xorg (Ubuntu):
assignee: nobody → Rich.T. (rich.t.)
status: New → Fix Released
Revision history for this message
Sinisa Radalj (sinisa1hr) wrote :

interesting is that i fix it ,when i accept fglrx-updates ,after i run apt-get update in recovery console with read write mode with networking,and more interesting is that i do not install fglrx-updates ,and even after log in i double check in over menu in ubuntu in software and updates or neither with package manager i do not have fglrx-updates at all, and i do not use fglrx-updates.. i use fglrx manually installed.. synaptic knows for sure.

sure i will not erase last and older version of kernel so fast ,as i used to be spoiled due no problems for so long time..

well trick is obviously that even one step down to older kernel not help in my case and lead me in wrong way ,seems 2 step down is right to exactly that one which came with 15.04..so that's why when you overwrite with re-install all works.

but i keep with newest,and seems all is not perfect as i keep getting red triangle,not immediately but came after few hours..,but no package is reported broken in package manager..now came again after update of ubuntu base..

sure i will read all mentioned links..well about affected people is more then two,as as soon i can go on internet i read solution for similar& same symptoms,to go back to original kernel which is shipped with 15.04..just those not reported bug..

well it so easy to overwrite just system partition,(and keep all settings in all other partitions),and then reinstall additional programs,seems and look more like update.. . life can be even more easy and good with ubuntu..but i am sorry for those who keep all on one partition..well i have red triangle from time to time, but no package is broken and all i try works...

sure i will now read all mentioned links,and links from there,thanks a lot for that and respond.

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.