| Summary: | kwin segmentation fault during logout | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Helmut Robben <helmut.robben> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | ob.harald |
| Priority: | NOR | ||
| Version First Reported In: | 4.10.1 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Helmut Robben
2013-04-05 12:52:39 UTC
consider switching to the proprietary NVIDIA driver. *** This bug has been marked as a duplicate of bug 309280 *** Switching to proprietary NVIDIA driver solves the issue, but it's kind of weird: A few month ago I was told that the proprietary driver higher than version 304.88 doesn't support my video card anymore. Trying to emerge nvidia-driver-304.88 resulted in an error without support (gentoo only supports the nvidia driver up to kernel < 3.7). That's why I switched to nouveau. Actually emerging nvidia-driver-304.88 works with kernel 3.8.5. Don't know how long this will last, but for now everything works well. 304.xx is legacy but not unmaintained. You'll get updates to match recent kernels/XOrg versions. Potentially with (increasingly) more delay than the mainline blob, though. Created attachment 78776 [details]
New crash information added by DrKonqi
kwin (4.10.00 "release 1") on KDE Platform 4.10.00 "release 1" using Qt 4.8.4
- What I was doing when the application crashed:
Each time when a user logs out or shutdown from a KDE session, kwin crashes with a segfault.
The crash can be reproduced every time.
-- Backtrace (Reduced):
#6 PUSH_RESRC (tor=<optimized out>, data=<optimized out>, r=<optimized out>, bin=<optimized out>, mthd=<optimized out>, push=<optimized out>, subc=<optimized out>, access=<optimized out>, vor=<optimized out>) at nv30_winsys.h:107
#7 nv30_vbo_validate (nv30=0x92ce688) at nv30_vbo.c:239
#8 0xada72a82 in nv30_state_validate (nv30=nv30@entry=0x92ce688, hwtnl=hwtnl@entry=1 '\001') at nv30_state_validate.c:487
#9 0xada50505 in nv30_clear (pipe=0x92ce688, buffers=1, color=0xbfb2afcc, depth=1, stencil=0) at nv30_clear.c:61
#10 0xadc91c62 in st_Clear (ctx=0x932acf8, mask=2) at ../../src/mesa/state_tracker/st_cb_clear.c:557
kcmshell4 kwincompositing, 2nd tab. disable the "logout" effect or try kwriteconfig --file kwinrc --group Effect-Logout --key UseBlur false qdbus org.kde.kwin /KWin reconfigure qdbus org.kde.kwin /KWin reconfigureEffect kwin4_effect_logout Am 10.04.2013 18:00, schrieb Thomas Lübking : > https://bugs.kde.org/show_bug.cgi?id=317880 > > --- Comment #5 from Thomas Lübking <thomas.luebking@gmail.com> --- > kcmshell4 kwincompositing, 2nd tab. disable the "logout" effect or try > kwriteconfig --file kwinrc --group Effect-Logout --key UseBlur false > qdbus org.kde.kwin /KWin reconfigure > qdbus org.kde.kwin /KWin reconfigureEffect kwin4_effect_logout > Dies beseitigt das Problem, besten Dank. Vielleicht lässt sich ja das Fehlverhalten eleganter durch einen zukünftigen Patch beseitigen ! Thanks a lot, Harald Huber The problem is that the patch is in the driver (even if KWin would do really really wrong by -actually- ignoring limitations, which you should however rather not hit on that GPU, the GL call should yell an error, but no way crash), so a patch could at best blacklist the driver. Now, the particular issue about the nouveau drivers is that their OpenGL implementation is not considered "reliable" and you're actually supposed to expect issues [1], so they'll be rather used by developers and driver testers - therefore blacklisting explicitly them would be rather not helpful. Upstream bug *might* be https://bugs.freedesktop.org/show_bug.cgi?id=56474 (do you have that chip?) [1] http://nouveau.freedesktop.org/wiki/MesaDrivers |