Summary: | Java menu problems | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | Alex Austin <Circuitsoft.alex+bugs.kde.org> |
Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Alex Austin
2013-07-25 00:14:50 UTC
The backtrace is from a crash-on-exit, bug #282933 This means kwin was terminated (kill [-15], not -9) what means kwin was still processing events what means: a) the backtrace is not (directly) related b) suspending the compositor (Shift+Alt+F12) would likely unfreeze the screen as well To get a rough idea about the source of the problem: does this happen with xrender compositing as well? ("kcmshell4 kwincompositing", 3rd tab) Can this bug be resolved NOTMYPROBLEM or something along those lines? This failure also happens while kwin isn't running, so it must be some strange interaction between the intel driver and Java. XRender compositing makes no difference and Shift+Alt+F12 does not un-freeze the display. either a bug in the driver or java (that popup at least) grabs the server. Since you mentioned "kwin not running" - but another WM and/or compositor instead? No. Quit kwin, ran without a wm to test, started kwin again when done. what "unfroze" the screen in that case? Just waiting for a few minutes. Did you check /var/log/Xorg.0.log for errors? Eventually dmesg? |