https://bugs.kde.org/show_bug.cgi?id=359079
Thomas Lübking <thomas.luebk...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|core |scene-opengl
Status|UNCONFIRMED |RESOLVED
Resolution|--- |UPSTREAM
Flags| |Catalyst+
--- Comment #1 from Thomas Lübking <thomas.luebk...@gmail.com> ---
> #6 0x00007fda4db36aa9 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
> #7 0x00007fda4d221ff8 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
> #8 0x00007fda4d222292 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
> #9 0x00007fda4d653b23 in () at /usr/X11R6/lib64/modules/dri/fglrx_dri.so
> #10 0x00007fda7522ba32 in () at /usr/lib64/libkwin4_effect_builtins.so.1
> #11 0x00007fda7522c6e4 in () at /usr/lib64/libkwin4_effect_builtins.so.1
> #12 0x00007fda77f58a31 in () at /usr/lib64/libkwin.so.5
Crash in fglrx, most likely caused by blur and/or contrast effect, see bug
#349862, but the backtrace lacks the necessary debug symbols to be sure; you
need to install at least kwin-debuginfo.
If it's the same bug, disabling caching in the blur effect *might* prevent this
(but we don't know what the actual reason is since fglrx remains opaque)
--
You are receiving this mail because:
You are watching all bug changes.
