| Summary: | Kwin crashed after checking an advanced setting | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Leonardo La Malfa <leonardo.la.malfa> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | strzol |
| 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
Leonardo La Malfa
2010-07-20 17:08:20 UTC
I'm sorry to say, but you are using a development version with a buggy driver. It crashes in the driver and there is nothing we can do about it. > I'm sorry to say, but you are using a development version
> with a buggy driver. It crashes in the driver and there is nothing we can
> do about it.
It's OK, it's nice you actually replied. It may appear the most normal
behavior, but on Launchpad this bug report would have been left to rot before
the "perfect" 10.
However, I'm aware I'm using a development version of Kubuntu, with the second
release candidate of KDE 4.5, and, well yeah, a crappy driver. And I reported
the bug against Kwin exactly for that, because we are encouraged to report
crashes occurring on development versions in the hope it may help to improve
on them. This time, I hoped in vain, it seems.
However, it was only a one-shot thing, so hopefully it won't occur again.
Thanks anyway!
you want to report this issue to the developers of the (radeon?) driver, since it will prevent any vsync'ing (alongside direct rendering only?!) *** This bug has been marked as a duplicate of bug 241263 *** Thanks for your suggestion, I would be very glad to do that, if it could help. But how would I go about that? I mean, I know how to report bugs with DrKonqi, but how should I report this bug to the driver developers? However, although it crashed when I was checking the setting, I have been using the laptop with full desktop effects (and vsync) without issues (so far). Xorg tracks bugs at https://bugs.freedesktop.org/ - "unfortunately" you need an additional account* there. you can link or copy this bug/stacktrace. > However, although it crashed when I was checking the setting, I have been using... there seems a general problem when re/creating a gl context on the radeon/ati drivers/dri2/whatever, see bug #244820 which has a different backrtace but similar context. *in addition (this is not the preferred way) you can mail xorg@lists.freedesktop.org or (worst and last resort only) lookup a header of the driver for a mail address and contact the developer in person. Thanks a lot for your time, Thomas! I'll do as you said in the suggested order. Created attachment 49448 [details]
New crash information added by DrKonqi
kwin (4.4.93 (KDE 4.4.93 (KDE 4.5 >= 20100713))) on KDE Platform 4.4.93 (KDE 4.4.93 (KDE 4.5 >= 20100713)) using Qt 4.6.3
- What I was doing when the application crashed:
Checking (with altering) advanced settings of konsole window.
-- Backtrace (Reduced):
#6 dri2DrawableGetMSC (psc=0x6ec2d0, pdraw=0x0, ust=0x7fff62dad4c8, msc=0x7fff62dad4c0, sbc=0x7fff62dad4b8) at dri2_glx.c:226
#7 0x00007f3eb19b1185 in __glXGetVideoSyncSGI (count=0x7fff62dad50c) at glxcmds.c:2317
#8 0x00007f3eb3f03c21 in KWin::SceneOpenGL::waitSync (this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.93svn1149349/kwin/scene_opengl.cpp:781
#9 0x00007f3eb3f17520 in KWin::SceneOpenGL::flushBuffer (this=0xa99f90, mask=<value optimized out>, damage=...) at /usr/src/debug/kdebase-workspace-4.4.93svn1149349/kwin/scene_opengl.cpp:830
#10 0x00007f3eb3f40956 in KWin::SceneOpenGL::paint (this=0xa99f90, damage=..., toplevels=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.93svn1149349/kwin/scene_opengl.cpp:761
|