| Summary: | kwin crashed randomly | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | wzab <wzab01> |
| Component: | scene-opengl | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | cll2jr, dcahilla, erichgamba, girard.cool, narkhedkarcn, rec9140, scheel.karl, wzab |
| Priority: | NOR | Flags: | mgraesslin:
Intel+
|
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
wzab
2012-04-02 23:13:39 UTC
It crashes right in the driver - nothing we can do about it. *** Bug 299561 has been marked as a duplicate of this bug. *** *** Bug 299557 has been marked as a duplicate of this bug. *** *** Bug 296496 has been marked as a duplicate of this bug. *** From the duplicates we see that this happens quite often with Ubuntu. "It crashes right in the driver - nothing we can do about it." What driver? Any clue on how to fix this? xf86-video-intel
as workaround don't use opengl compositing with intel i8xx chips but the xrender backend ("kcmshell4 kwincompositing", 3rd tab)
*** Bug 300616 has been marked as a duplicate of this bug. *** *** Bug 302454 has been marked as a duplicate of this bug. *** *** Bug 302933 has been marked as a duplicate of this bug. *** *** Bug 303583 has been marked as a duplicate of this bug. *** This is marked solved upstream?!?? Where is the updated driver? I don't see one being pushed to users? Only update has been for foomatic-filters. Where is this updated driver? "Resolved" != "Fixed" "Resolved Upstream" == "This is not our bug. Solution is to blame somebody else being responsive" Ask intel, but there's unlikely a fixed driver - the chip is too old and its GL caps too lousy to be seriously used (besides maybe desktop effects - iff at all) The core issue is that it -apparently- fails as soon as there's more than one GL context (eg. GL acceleration in browser) -> As told, use the xrender backend and avoid the GL functionalities in other applications as much as possible. Then this is *not* "resolved upstream" this is referred to upstream or something. This is not resolved in any form. xrender is not a choice. > Then this is *not* "resolved upstream" this is referred to upstream or
> something.
>
> This is not resolved in any form.
resolved upstream means in KDE land "not our problem, someone else's". At
Akademy we had a discussion about it and it will in future probably be
replaced by "RESOLVED CANTFIX" which currently does not yet exist.
*** Bug 303583 has been marked as a duplicate of this bug. *** (In reply to comment #14) > Then this is *not* "resolved upstream" this is referred to upstream or > something. I acknowledge your confusion but discussions on ambiguous terminology has to happen with the bugtracker admins and no in bugs. > This is not resolved in any form. In addition I suggest to consult a dictionary about the term "resolved". The bug *is* resolved to not be dealt in the KDE context. *** Bug 306115 has been marked as a duplicate of this bug. *** Created attachment 74489 [details]
New crash information added by DrKonqi
kwin (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1
- What I was doing when the application crashed:
Intalling skype with software manager when the error message appeared, Skype as installed itself and seem to be working properly.
The only misbehavior is from the panel bar wich occassionnaly disappears. The only way to recover is by a reboot.
-- Backtrace (Reduced):
#12 0x04da3aaa in do_bo_emit_reloc (bo=0x91a96c0, offset=<optimized out>, target_bo=0x91bf5b0, target_offset=0, read_domains=4, write_domain=0, need_fence=false) at ../../intel/intel_bufmgr_gem.c:1579
#13 0x04d9e2c8 in drm_intel_bo_emit_reloc (bo=0x91a96c0, offset=5868, target_bo=0x91bf5b0, target_offset=0, read_domains=4, write_domain=0) at ../../intel/intel_bufmgr.c:181
#14 0x0335e78e in intel_batchbuffer_emit_reloc (intel=0x8ed3638, buffer=0x91bf5b0, read_domains=4, write_domain=0, delta=0) at intel_batchbuffer.c:235
#15 0x0335b28c in i830_emit_state (intel=0x8ed3638) at i830_vtbl.c:542
#16 0x03380754 in intelRenderStart (ctx=0x8ed3638) at intel_tris.c:1109
You know, I get this because I joined the forum to report this error with Kubuntu, but seeing as how it's not going to be fixed, I switched to openSuSE 12.2 and haven't experience the problem since. Seems to be unique to Kubuntu. KDE on openSuSE runs just fine. -----Original Message----- From: girard.cool <girard.cool@yahoo.ca> To: cll2jr <cll2jr@aol.com> Sent: Thu, Oct 11, 2012 6:22 pm Subject: [Bug 297348] kwin crashed randomly https://bugs.kde.org/show_bug.cgi?id=297348 --- Comment #19 from girard.cool@yahoo.ca --- Created attachment 74489 [details] --> https://bugs.kde.org/attachment.cgi?id=74489&action=edit New crash information added by DrKonqi kwin (4.8.5 (4.8.5)) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 - What I was doing when the application crashed: Intalling skype with software manager when the error message appeared, Skype as installed itself and seem to be working properly. The only misbehavior is from the panel bar wich occassionnaly disappears. The only way to recover is by a reboot. -- Backtrace (Reduced): #12 0x04da3aaa in do_bo_emit_reloc (bo=0x91a96c0, offset=<optimized out>, target_bo=0x91bf5b0, target_offset=0, read_domains=4, write_domain=0, need_fence=false) at ../../intel/intel_bufmgr_gem.c:1579 #13 0x04d9e2c8 in drm_intel_bo_emit_reloc (bo=0x91a96c0, offset=5868, target_bo=0x91bf5b0, target_offset=0, read_domains=4, write_domain=0) at ../../intel/intel_bufmgr.c:181 #14 0x0335e78e in intel_batchbuffer_emit_reloc (intel=0x8ed3638, buffer=0x91bf5b0, read_domains=4, write_domain=0, delta=0) at intel_batchbuffer.c:235 #15 0x0335b28c in i830_emit_state (intel=0x8ed3638) at i830_vtbl.c:542 #16 0x03380754 in intelRenderStart (ctx=0x8ed3638) at intel_tris.c:1109 -- You are receiving this mail because: You are on the CC list for the bug. |