Created attachment 782416 [details] Crash Log report from system. Description of problem: X always crash and can not start with new Catalyst driver.So I can't start both KDE and GNOME. Version-Release number of selected component (if applicable): kmod-catalyst-3.10.4-300.fc19.x86_64-13.8-0.1.beta1.fc19.x86_64 xorg-x11-drv-catalyst-13.8-0.1.beta1.fc19.x86_64 xorg-x11-drv-catalyst-libs-13.8-0.1.beta1.fc19.x86_64 akmod-catalyst-13.8-0.1.beta1.fc19.x86_64 How reproducible: always Steps to Reproduce: 1.Boot and start X 2. 3. Actual results: crash X system and restart with Log-in screen Expected results: going to normal. Additional info:
I have the same problem. The following is the backtrace of error section from Xorg log: [ 601.477] (EE) [ 601.477] (EE) Backtrace: [ 601.478] (EE) 0: /usr/bin/Xorg (OsLookupColor+0x129) [0x46edb9] [ 601.479] (EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x300a40ef9f] [ 601.479] (EE) 2: /lib64/libc.so.6 (____strtod_l_internal+0x74) [0x300983e0c4] [ 601.480] (EE) 3: /usr/lib64/xorg/modules/extensions/catalyst/libglx.so (GlxInitVisuals2D+0x24772) [0x7f888f91b482] [ 601.480] (EE) 4: /usr/lib64/xorg/modules/extensions/catalyst/libglx.so (__glXSetTexBufferInfo+0x1fd7) [0x7f888f8d38a7] [ 601.480] (EE) 5: /usr/bin/Xorg (SendErrorToClient+0x3f7) [0x436fa7] [ 601.480] (EE) 6: /usr/bin/Xorg (_init+0x3aaa) [0x429b4a] [ 601.481] (EE) 7: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x3009821b75] [ 601.481] (EE) 8: /usr/bin/Xorg (_start+0x29) [0x4267b1] [ 601.481] (EE) 9: ? (?+0x29) [0x29] [ 601.481] (EE) [ 601.481] (EE) Segmentation fault at address 0x0 [ 601.481] (EE) [ 601.481] (EE) Caught signal 11 (Segmentation fault). Server aborting
I have a similar problem; my workstation small to a small window that says: Oops, something went wrong . . . It is very unstable at that point and usually requires a 15 second power off to reset. Here is the last X11/kernel/akmod/kmod that works: 3.9.9-302.fc19.x86_64 #1 SMP Sat Jul 6 13:41:07 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux akmod-catalyst-13.8-0.2.beta1.fc19.x86_64 kmod-catalyst-3.9.9-302.fc19.x86_64-13.8-0.2.beta1.fc19.x86_64 xorg-x11-drv-catalyst-13.8-0.1.beta1.fc19.x86_64 xorg-x11-drv-catalyst-libs-13.8-0.1.beta1.fc19.x86_64 I've blocked kernel updates and keep searching for a solution. Any/all help would be appreciated!
Hello, I was able to successfully update my kernel today: Linux ThriceDarkness 3.11.2-201.fc19.x86_64 #1 SMP Fri Sep 27 19:20:55 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Here are the currently installed files since the updated: xorg-x11-drv-catalyst-libs-13.8-0.1.beta1.fc19.x86_64 kmod-catalyst-3.11.2-201.fc19.x86_64-13.8-0.2.beta1.fc19.8.x86_64 * akmod-catalyst-13.8-0.2.beta1.fc19.8.x86_64 * xorg-x11-drv-catalyst-13.8-0.1.beta1.fc19.x86_64 This seems to have solved my issues since kernel: 3.9.9-302 x86_64 Thank you for all you do for us! -Stephen
I was having the same problem with latest Fedora 18 and latest Fedora 19, versions are: kernel-3.11.6-200.fc19.x86_64 xorg-x11-server-Xorg-1.14.3-1.fc19.x86_64 xorg-x11-drv-catalyst-13.9-1.fc19.x86_64 xorg-x11-drv-catalyst-libs-13.9-1.fc19.x86_64 akmod-catalyst-13.9-2.fc19.x86_64 What fixes the crash for me is # yum remove xorg-x11-glamor -- Maxim
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.