| Summary: | Kwin crashed by screensaver | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Andreas Hencke <andreas.hencke> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | wtirado78 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Andreas Hencke
2011-08-06 08:49:30 UTC
call "kcmshell4 kwincompositing", enter the 3rd ("advanced") tab and UNcheck "suspend compositing for fullscreen windows".
Try and report whether you can still reproduce the crash.
What's your GPU/Driver & Mesa version? (in doubt, run "kwin --replace &" from konsole, there's some relevant output)
Am 07.08.2011 00:01, schrieb Thomas Lübking : > https://bugs.kde.org/show_bug.cgi?id=279514 > > > > > > --- Comment #1 from Thomas Lübking<thomas luebking gmail com> 2011-08-06 22:01:44 --- > call "kcmshell4 kwincompositing", enter the 3rd ("advanced") tab and UNcheck > "suspend compositing for fullscreen windows". > Try and report whether you can still reproduce the crash. > > What's your GPU/Driver& Mesa version? (in doubt, run "kwin --replace&" from > konsole, there's some relevant output) > > This is the output of "kwin --replace &": andreas@andreas-Extensa-5220:~$ kwin --replace & [1] 27457 andreas@andreas-Extensa-5220:~$ OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) 965GM GEM 20100330 DEVELOPMENT x86/MMX/SSE2 OpenGL version string: 2.1 Mesa 7.10.2 OpenGL shading language version string: 1.20 Driver: Intel GPU class: i965 OpenGL version: 2.1 GLSL version: 1.20 Mesa version: 7.10.2 X server version: 1.10.1 Linux kernel version: 2.6.38 Direct rendering: yes Requires strict binding: yes GLSL shaders: yes Texture NPOT support: yes QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden QFileSystemWatcher: failed to add paths: /home/andreas/.config/ibus/bus PS.: after runing "kwin --replace &" the transparency got lost. Addition to the PS. in comment #2: The whole desktop freezed, no reaktion to "crtl Alt delete" after Magic SysRq R-E-IS-U-B got a black screen with the cursor, no further reaktion. Created attachment 62949 [details]
New crash information added by DrKonqi
kwin (4.7.00 (4.7.0)) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.2
- What I was doing when the application crashed: Nothing really. I came back to my computer and the screensaver was on. If I move the mouse or touch a keyboard button to get my computer screen back on from the screensaver I get the crash. Happens probably all the time on my computer.
-- Backtrace (Reduced):
#7 prepare_wm_surfaces (brw=0x9dccbc8) at brw_wm_surface_state.c:602
#8 0x096e1ac7 in brw_validate_state (brw=0x9dccbc8) at brw_state_upload.c:397
#9 0x096cfdfe in brw_try_draw_prims (ctx=0x9dccbc8, arrays=0x9e04890, prim=0xbfb407d8, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=5) at brw_draw.c:362
#10 brw_draw_prims (ctx=0x9dccbc8, arrays=0x9e04890, prim=0xbfb407d8, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=5) at brw_draw.c:447
#11 0x028b48bc in vbo_draw_arrays (ctx=0x9dccbc8, mode=<value optimized out>, start=0, count=6, numInstances=1) at vbo/vbo_exec_array.c:588
@William despite the backtrace ended up here you most likely experience bug #252817 (and the "workaround" from comment #1 should work. Andreas also seams to encounter a kernel panic , ie. a really severe bug in the kernel module of the intel driver. @Andreas: did the workaround in comment #1 work for you? The kernel panic on the restart (gl reinit) is a different issue and as mentioned a severe kernel module bug that you should report (unless a recent version fixed it for you) first to your distro (against kernel patches) and then linux. Took care of it. Thanks! On 08/18/2011 11:32 AM, Thomas Lübking wrote: > https://bugs.kde.org/show_bug.cgi?id=279514 > > > > > > --- Comment #5 from Thomas Lübking<thomas luebking gmail com> 2011-08-18 15:32:39 --- > @William > despite the backtrace ended up here you most likely experience bug #252817 (and > the "workaround" from comment #1 should work. > > Andreas also seams to encounter a kernel panic , ie. a really severe bug in the > kernel module of the intel driver. > > @Andreas: did the workaround in comment #1 work for you? > The kernel panic on the restart (gl reinit) is a different issue and as > mentioned a severe kernel module bug that you should report (unless a recent > version fixed it for you) first to your distro (against kernel patches) and > then linux. > Am 18.08.2011 17:32, schrieb Thomas Lübking : > https://bugs.kde.org/show_bug.cgi?id=279514 > > > > > > --- Comment #5 from Thomas Lübking<thomas luebking gmail com> 2011-08-18 15:32:39 --- > @William > despite the backtrace ended up here you most likely experience bug #252817 (and > the "workaround" from comment #1 should work. > > Andreas also seams to encounter a kernel panic , ie. a really severe bug in the > kernel module of the intel driver. > > @Andreas: did the workaround in comment #1 work for you? > The kernel panic on the restart (gl reinit) is a different issue and as > mentioned a severe kernel module bug that you should report (unless a recent > version fixed it for you) first to your distro (against kernel patches) and > then linux. > > Hi Thomas, I'm getting old, sorry I've forgotten to write the feedback: The workaround worked well, I think there were some updates until now, because I can't reproduce that error anymore. Nevermind, happens to everybody. (Me at least) *** This bug has been marked as a duplicate of bug 252817 *** |