Bug 321790 - The system does not react to the keyboard and mouse after a few hours of inactivity, only a dark screen
Summary: The system does not react to the keyboard and mouse after a few hours of inac...
Status: RESOLVED DUPLICATE of bug 270818
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-30 13:06 UTC by morowhind
Modified: 2013-06-30 13:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description morowhind 2013-06-30 13:06:56 UTC
Application: kwin (4.8.5 (4.8.5))
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-43-generic x86_64
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:

Failure regularly happens if you leave your computer turned on for a few hours. It goes into standby mode or hibernate mode. Resume help is only a reboot.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[KCrash Handler]
#6  __memcpy_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2819
#7  0x00007f7b3b9a1836 in __indirect_glProgramParameters4fvNV (target=1, index=36279620, num=1067517816, params=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:52
#8  0x00007f7b1f36920f in KWin::ARBBlurShader::init (this=0x2299530) at ../../../kwin/effects/blur/blurshader.cpp:471
#9  0x00007f7b1f364799 in KWin::BlurEffect::reconfigure (this=0x2274120, flags=...) at ../../../kwin/effects/blur/blur.cpp:85
#10 0x00007f7b1f364a77 in KWin::BlurEffect::BlurEffect (this=0x2274120) at ../../../kwin/effects/blur/blur.cpp:53
#11 0x00007f7b1f364b76 in KWin::effect_create_kwin4_effect_blur () at ../../../kwin/effects/blur/blur.cpp:34
#12 0x00007f7b3faec5a4 in KWin::EffectsHandlerImpl::loadEffect (this=0x22370c0, name=..., checkDefault=false) at ../../kwin/effects.cpp:1199
#13 0x00007f7b3faed90a in KWin::EffectsHandlerImpl::reconfigure (this=0x22370c0) at ../../kwin/effects.cpp:196
#14 0x00007f7b3faede28 in KWin::EffectsHandlerImpl::EffectsHandlerImpl (this=0x22370c0, type=<optimized out>) at ../../kwin/effects.cpp:128
#15 0x00007f7b3fac214f in KWin::Workspace::setupCompositing (this=0x21d6710) at ../../kwin/composite.cpp:174
#16 0x00007f7b3fac2aa5 in KWin::Workspace::setupCompositing (this=<optimized out>) at ../../kwin/composite.cpp:87
#17 0x00007f7b3fa5e920 in KWin::Workspace::Workspace (this=0x21d6710, restore=true) at ../../kwin/workspace.cpp:227
#18 0x00007f7b3fa76b8c in KWin::Application::Application (this=<optimized out>) at ../../kwin/main.cpp:322
#19 0x00007f7b3fa7888c in kdemain (argc=<optimized out>, argv=<optimized out>) at ../../kwin/main.cpp:511
#20 0x00007f7b3f67976d in __libc_start_main (main=0x400630 <main(int, char**)>, argc=3, ubp_av=0x7fff9010c538, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff9010c528) at libc-start.c:226
#21 0x0000000000400661 in _start ()

Possible duplicates by query: bug 321613, bug 319520, bug 313923, bug 311930, bug 309625.

Reported using DrKonqi
Comment 1 Thomas Lübking 2013-06-30 13:11:48 UTC
The bug is in the driver and exposed by the blur filter, but "accurate" scaling would likely trigger it as well at some point.

For newer versions of fglrx kwin would use direct rendering (which is however completely broken in the older versions), what bypasses *this* issue in fglrx.

--

I'm not sure that this is related to an inresponsive system (ie. you could not even Ctrl+Alt+F1  to move to VT1) but that would be a kernel (module) issue anyway (if related, then through fglrx)

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