| Summary: | kwin from kde 4.6.5 crashes on first start with mesa 7.11 on Intel Sandybridge | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Martin Steigerwald <Martin> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | thomas.luebking |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian unstable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Martin Steigerwald
2011-09-07 12:41:43 UTC
*** This bug has been marked as a duplicate of bug 270818 *** Thanks. I reported this downstream as: kwin: crashes on login (sandybridge/mesa7.11/blur effect) http://bugs.debian.org/640799 Errrmmm this is unlikely a good general downstream solution since eg. afaik fglrx will segfault with indirect rendering. Recent kwin version (git master) removed the user choice altogether and enforce direct/indirect rendering depending on backend (4.7 has 3 GL paths) and driver (since only the nvidia css driver can actually do both w/o crashing) a) can you test 4.7 (or even git master) b) what's the output when starting kwin from konsole resp. "glxinfo | grep -iE '(renderer|vendor)' Thomas, what solution do you mean? I did not suggest any concrete solution, just gave all the pointers to possibly relevant information regarding the issue. Its up to the Debian developers to decide for the best possible solution. a) Although I have a pretty fast ThinkPad T520 with Intel SSD 320 its a question of time spent. I never compiled KDE myself before so I nonetheless likely need some time to get a test setup running. Debian packages of 4.7 do not seem to be available ATM. b) martin@merkaba:~> glxinfo | grep -iE '(renderer|vendor)' server glx vendor string: SGI client glx vendor string: Mesa Project and SGI OpenGL vendor string: Tungsten Graphics, Inc OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile Actually I do think that mesa drivers should reliably advertise their features. Client software guessing driver capabilities from vendor and renderer strings does seem like a workaround for me. So if mesa drivers do not advertise features reliably via a good API, then possibly its best to report there first? - I was referring to the "export KWIN_DIRECT_GL=1" solution - At least 4.7 should be available in binary form, yeso? - In an ideal world. In the real world things are advertised but not available, available but not advertised and advertised and available but broken (indirect rendering should always work) - at least under some conditions.... There's also more than mesa. :-( That discussion however took place when 4.6 was released and the current checks are far more broad. (Mesa & Nvidia are assumed to support direct rendering unless the driver fails to create such context altogether) I saw "export KWIN_DIRECT_GL=1" as a work around, not a solution. For Debian 4.7 is not yet available in binary form. I also do not find a KDE 4.7 live cd ATM: http://dewiki.opensuse.org/KDE_Live still lists 4.6.5 as latest version. Hmmm, Chakra might be providing a LiveCD image at: http://chakra-project.org/get/ Might try that as I manage to take time for this. |