Bug 42279 - [i965] Crash in KDE 4.7.2 after Setting the Colours of the Crackberg screensaver on Mageia Linux 2.
Summary: [i965] Crash in KDE 4.7.2 after Setting the Colours of the Crackberg screensa...
Status: RESOLVED DUPLICATE of bug 41211
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: 7.11
Hardware: x86-64 (AMD64) Linux (All)
: medium critical
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 06:43 UTC by Shlomi Fish
Modified: 2011-11-23 11:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
The dmesg output (37.25 KB, text/plain)
2011-10-26 06:44 UTC, Shlomi Fish
Details
My xorg.conf (2.14 KB, text/plain)
2011-10-26 06:44 UTC, Shlomi Fish
Details
The Xorg.0.log. (22.23 KB, text/plain)
2011-10-26 06:45 UTC, Shlomi Fish
Details

Description Shlomi Fish 2011-10-26 06:43:01 UTC
On my Mageia Linux 2 (Cauldron) Core i3 system, I'm getting a crash after I set the colours in the crackberg screensaver (from XScreensaver) in KDE 4's systemsettings -> Display -> Screensaver, and get this gdb backtrace:

Program received signal SIGSEGV, Segmentation fault.
DRI2WaitSwap (client=0x5883ed0, pDrawable=<optimized out>) at dri2.c:774
774	    if ((pPriv->swapsPending) &&
#0  DRI2WaitSwap (client=0x5883ed0, pDrawable=<optimized out>) at dri2.c:774
#1  0x00007f2d6dc66618 in __glXDRIcontextWait (baseContext=<optimized out>, cl=0x5884000, error=0x7fff2735e6dc) at glxdri2.c:304
#2  0x00007f2d6dc5c13b in __glXForceCurrent (cl=0x5884000, tag=100663298, error=0x7fff2735e6dc) at glxext.c:417
#3  0x00007f2d6dc2d741 in __glXDisp_GetBooleanv (cl=0x5884000, pc=0x8c53020 "\233p\003") at indirect_dispatch.c:1770
#4  0x00007f2d6dc5bda5 in __glXDispatch (client=0x5883ed0) at glxext.c:556
#5  0x000000000042db51 in Dispatch () at dispatch.c:431
#6  0x00000000004218ee in main (argc=6, argv=<optimized out>, envp=<optimized out>) at main.c:287
A debugging session is active.

	Inferior 1 [process 13549] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]

I can reproduce this crash every time with my account, but it does not happen in a new UNIX user account. 

I'll attach other information (xorg.conf, dmesg, etc. soon).
Comment 1 Shlomi Fish 2011-10-26 06:44:10 UTC
Created attachment 52791 [details]
The dmesg output
Comment 2 Shlomi Fish 2011-10-26 06:44:48 UTC
Created attachment 52792 [details]
My xorg.conf
Comment 3 Shlomi Fish 2011-10-26 06:45:39 UTC
Created attachment 52794 [details]
The Xorg.0.log.
Comment 4 Chris Wilson 2011-11-23 11:16:40 UTC

*** This bug has been marked as a duplicate of bug 41211 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.