FS#26632 - xorg segfaults

Attached to Project: Arch Linux
Opened by Simone Lazzaris (ziopera) - Wednesday, 26 October 2011, 15:43 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 06 November 2011, 13:02 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andrea Scarpino (BaSh)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
I get random segfaults in xorg. It seems to happen more when the screensaver (opengl) is active

In xorg.log I see:

Backtrace:
[ 13074.670] 0: /usr/bin/X (xorg_backtrace+0x26) [0x566b16]
[ 13074.670] 1: /usr/bin/X (0x400000+0x16a789) [0x56a789]
[ 13074.670] 2: /lib/libpthread.so.0 (0x7f7e608db000+0xf800) [0x7f7e608ea800]
[ 13074.670] 3: /lib/libpthread.so.0 (0x7f7e608db000+0xffff8081a449c098) [0x4d77098]
[ 13074.671] Segmentation fault at address 0x4d77098
[ 13074.671]
Fatal server error:
[ 13074.671] Caught signal 11 (Segmentation fault). Server aborting
[ 13074.671]
[ 13074.671]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.

Additional info:
* package version(s)
xorg-server 1.11.1.901-1
* config and/or log files etc.
- intel graphic card
- no configuration file
- kde 4.7.2

Steps to reproduce:
Just work normally. More often when the screensaver is active
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Sunday, 06 November 2011, 13:02 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#23479 
Comment by Jelle van der Waa (jelly) - Friday, 28 October 2011, 14:45 GMT
For this to be usefull you will have to have debugging enabled.
Comment by Simone Lazzaris (ziopera) - Thursday, 03 November 2011, 11:28 GMT
I know that the debuggin will be useful, but I'm quite busy at the moment and so I don't know if I can recompile X with debug support.
Anyway, I've switched the screensaver from OpenGL to traditional and the problem is (apparently) gone.
So maybe this report can be a duplicate of bug number 23479 ?

Loading...