FS#33513 - [catalyst] Programs crash all the time with Catalyst driver
Attached to Project:
Community Packages
Opened by Bill Seremetis (bserem) - Tuesday, 22 January 2013, 11:59 GMT
Last edited by Laurent Carlier (lordheavy) - Tuesday, 23 April 2013, 07:05 GMT
Opened by Bill Seremetis (bserem) - Tuesday, 22 January 2013, 11:59 GMT
Last edited by Laurent Carlier (lordheavy) - Tuesday, 23 April 2013, 07:05 GMT
|
Details
Description:
I switched to Catalyst a few weeks ago, thought it would be better and I wanted to give Steam a try. Since then I started having very strange crashing, one after the other, non stop. Firefox, Thunderbird and Chromium all crashed with a "segmentation fault". I had to open them from a terminal to see that. If I opened them from a desktop-shortcut they simply vanished. The most important is that this was random, I couldn't find out what was triggering the crash. Opera on the other hand was crashing and providing a debug/restart window. The opera crash log said this "/usr/lib/opera/pluginwrapper/operapluginwrapper-native got signal SIGSEGV at address 7FAFAD201F42". Upon restart opera would crash again, and again, and again... indefinetally, until I did a clean start (with no tabs). I run memtest86+ for two passes (5+ hours) and I had no problems with my RAM. I switched from XFCE to i3 for a few days. The problem remained. I switched to LXDE, the problem remained. I enabled the testing repositories. The problem remained. Then it hit me and I switched back to radeon driver, the open source one. Things work since then. No crashes, no programs vanishing from my desktop, all seem to work fine. Additional info: * package version(s) Catalyst 13.1-1 (and the previous ones). Steps to reproduce: Install catalyst on a x64_86 system and fire up some of the aforementioned programs, they should crash sooner or later. I know that this is a crazy bug, because it leaves no traces/logs for it to be solved. But for the time being I solved it by using the open-drivers. So I'm blaiming catalyst for the crash-experience. It might be an upstream bug (wouldn't be the first time, hehehe). I'm mentioning it here, in case anybody had the same experience so as to gather intel and see if it can be solved. |
This task depends upon
Closed by Laurent Carlier (lordheavy)
Tuesday, 23 April 2013, 07:05 GMT
Reason for closing: Won't fix
Additional comments about closing: catalyst isn't anymore in our repos
Tuesday, 23 April 2013, 07:05 GMT
Reason for closing: Won't fix
Additional comments about closing: catalyst isn't anymore in our repos