| Summary: | KWD (kde-window-decorator) crashed and caused the signal 11 (SIGSEV) | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Mike Whincup <mwhincup> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | crash | CC: | andresbajotierra, antoniojmg, baniszb, bebedoc, bharattharee, bianchi, caius.brindescu, ct529, elriojas86, enet, geoff3, gribeiro_junior, ha-gie, jcmaktub2004, jeremie.bryon, jeremy, jordan.scott737, julian.bloechinger, kde-2011.08, louis_m_c, msfica, nicolas.ollivier, oli_p, pasconguero, paveldvlip, phantomofneo, renegad123, spiro.letendre, Systemdir, timoteus, tmassimi, zapzap40 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Generated bug kcrash report
New crash information added by DrKonqi |
||
|
Description
Mike Whincup
2007-03-24 11:38:25 UTC
In the console window where I typed kde-window-decorator --replace & I occasionally get error/warning messages, e.g ~> X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3e00001 I probably want to complain to Compiz/KWD developers. This is the most frustrating bug I have encountered so far. I'm not a Linux expert by any means so any simple instructions on how to fix this would be greatly appreciated. Sorry, that was supposed to be "You probably want to complain to Compiz/KWD developers", not I. KDE project does not develop KWD. I had the same behaviour in mandriva 2007 spring edition Are we actually sure the bug is in kde-window-decorator and not in a KDE/QT library? This resolved/invalid status looks kind of fast and unexplained... No, we are not sure. But we're also not sure it is in KDE/Qt. That's up to the KWD developers to find out and tell us if it's KDE/Qt problem. So what's the solution now?? it says *resolved*!! If it is a KDE/Qt problem after all, reopen and provide further information. Glad this thread hasn't died. If there is a resolution, I haven't heard of it... I'll try to capture more details next time it happens. *** Bug 148974 has been marked as a duplicate of this bug. *** *** Bug 150112 has been marked as a duplicate of this bug. *** *** Bug 150208 has been marked as a duplicate of this bug. *** *** Bug 150271 has been marked as a duplicate of this bug. *** *** Bug 150654 has been marked as a duplicate of this bug. *** *** Bug 150821 has been marked as a duplicate of this bug. *** It happens in AIGLX too. I believe it's not a X's problem cause compiz runs fine in the same setup. System here is: Kubuntu 7.10 (amd64) Athlon64 3500+ 4GB RAM. Video board: Nvidia 5700le 256MB *** Bug 152057 has been marked as a duplicate of this bug. *** I get the same type of message. It's random and it only appears when compiz is running (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1226041136 (LWP 6200)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb7ac9875 in raise () from /lib/tls/i686/cmov/libc.so.6 #8 0xb7acb201 in abort () from /lib/tls/i686/cmov/libc.so.6 #9 0xb7b00e5c in ?? () from /lib/tls/i686/cmov/libc.so.6 #10 0x0000000b in ?? () #11 0xbfd8b384 in ?? () #12 0x00000400 in ?? () #13 0xb7bcb0c8 in ?? () from /lib/tls/i686/cmov/libc.so.6 #14 0x00000017 in ?? () #15 0xbfd8cc28 in ?? () #16 0x00000014 in ?? () #17 0xb7bcb0e1 in ?? () from /lib/tls/i686/cmov/libc.so.6 #18 0x00000002 in ?? () #19 0xb7bcb13c in ?? () from /lib/tls/i686/cmov/libc.so.6 #20 0x00000023 in ?? () #21 0xb7bcb0e5 in ?? () from /lib/tls/i686/cmov/libc.so.6 #22 0x00000004 in ?? () #23 0xbfd8b8fb in ?? () #24 0x00000008 in ?? () #25 0xb7bcb0eb in ?? () from /lib/tls/i686/cmov/libc.so.6 #26 0x00000005 in ?? () #27 0x08078610 in ?? () #28 0xb7a9ea2c in ?? () from /usr/lib/libXrender.so.1 #29 0x08078610 in ?? () #30 0x08073bd0 in ?? () #31 0xbfd8b2e8 in ?? () #32 0xb79e2250 in _XAllocID () from /usr/lib/libX11.so.6 #33 0xb7b08d65 in ?? () from /lib/tls/i686/cmov/libc.so.6 #34 0x00000002 in ?? () #35 0xb7bcb0c8 in ?? () from /lib/tls/i686/cmov/libc.so.6 #36 0xbfd8cc28 in ?? () #37 0xb7bcb13c in ?? () from /lib/tls/i686/cmov/libc.so.6 #38 0xbfd8b8fb in ?? () #39 0x08074368 in ?? () #40 0xbfd8b8fb in ?? () #41 0x080a20e8 in ?? () #42 0xb7be6148 in ?? () from /lib/tls/i686/cmov/libc.so.6 #43 0x08073bd0 in ?? () #44 0xb7bcb13c in ?? () from /lib/tls/i686/cmov/libc.so.6 #45 0xb79e46c4 in _XReply () from /usr/lib/libX11.so.6 #46 0xb7b0c800 in free () from /lib/tls/i686/cmov/libc.so.6 #47 0xb79e1d6d in XFree () from /usr/lib/libX11.so.6 #48 0xb6be1118 in CrystalClient::ClientWindows () from /usr/lib/kde3/kwin3_crystal.so #49 0xb6be1574 in CrystalClient::mouseWheelEvent () from /usr/lib/kde3/kwin3_crystal.so #50 0xb6be5dcd in CrystalClient::eventFilter () from /usr/lib/kde3/kwin3_crystal.so #51 0xb7487e40 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3 #52 0xb7487ebe in QObject::event () from /usr/lib/libqt-mt.so.3 #53 0xb74bf5b3 in QWidget::event () from /usr/lib/libqt-mt.so.3 #54 0xb741faf0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #55 0xb7421f4a in QApplication::notify () from /usr/lib/libqt-mt.so.3 #56 0xb7ef7ca2 in KApplication::notify () from /usr/lib/libkdecore.so.4 #57 0xb73b227d in QApplication::sendSpontaneousEvent () from /usr/lib/libqt-mt.so.3 #58 0xb73a351b in QETWidget::translateWheelEvent () from /usr/lib/libqt-mt.so.3 #59 0xb73b0522 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #60 0xb73aefcc in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #61 0x08055e0f in ?? () #62 0xb739e153 in ?? () from /usr/lib/libqt-mt.so.3 #63 0x0806d0f8 in ?? () #64 0xbfd8c6b8 in ?? () #65 0x00000004 in ?? () #66 0xb79508d0 in ?? () from /usr/lib/libqt-mt.so.3 #67 0xbfd8c6b8 in ?? () #68 0xb79508d0 in ?? () from /usr/lib/libqt-mt.so.3 #69 0xbfd8c558 in ?? () #70 0xb73ae8e2 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 Backtrace stopped: frame did not save the PC The last one is a crash because of the Crystal window decoration and not related to KDE or kwin. Crystal was made to embed in kwin and it's own feature "scroll windows on wheel" crashes with kwd running under it when you use the scroll wheel on the decoration. Please disable the feature in the kwin decoration settings dialog and see if it goes away. This bug in Crystal IS ALREADY fixed, but Kubuntu seems to ship an old version of kwin-style-crystal (or whatever it is called). Please feel free to upgrade to 1.0.5. As already mentioned in comment #4, there's really no need to add anything here. KWD is developed by Compiz developers and not by the KDE project. And, as said in https://bugzilla.novell.com/show_bug.cgi?id=304184, there should be already a fix somewhere. *** Bug 152395 has been marked as a duplicate of this bug. *** *** Bug 153601 has been marked as a duplicate of this bug. *** *** Bug 154809 has been marked as a duplicate of this bug. *** *** Bug 155166 has been marked as a duplicate of this bug. *** Guys, I'm not sure whether to close this bug report now. Since I upgraded to Suse 10.3 (and have been running compiz) I don't think I've suffered this problem. Lubos, what do you think? hi, thanks for mailing. am still facing this problem to bring it back to normalcy i logout and login again. but the bug still exists. regards bharatt On 9 Jan 2008 19:40:54 -0000, Mike Whincup <mwhincup@hotmail.com> wrote: [bugs.kde.org quoted mail] hi,<br><br>thanks for mailing.<br><br>am still facing this problem<br><br>to bring it back to normalcy i logout and login again.<br><br>but the bug still exists.<br><br>regards<br>bharatt<br><br><div class="gmail_quote">On 9 Jan 2008 19:40:54 -0000, Mike Whincup < <a href="mailto:mwhincup@hotmail.com">mwhincup@hotmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d"> ------- You are receiving this mail because: -------<br>You are on the CC list for the bug, or are watching someone who is.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=143419" target="_blank">http://bugs.kde.org/show_bug.cgi?id=143419 </a><br><br><br><br><br></div>------- Additional Comments From mwhincup hotmail com 2008-01-09 20:40 -------<br>Guys,<br><br>I'm not sure whether to close this bug report now.<br><br>Since I upgraded to Suse 10.3 (and have been running compiz) I don't think I've suffered this problem. <br><br>Lubos, what do you think?<br></blockquote></div><br> hi didn't know whether i mentioned it or not. am currently using fedora 8. On 9 Jan 2008 19:40:54 -0000, Mike Whincup <mwhincup@hotmail.com> wrote: [bugs.kde.org quoted mail] hi<br><br>didn't know whether i mentioned it or not. <br><br>am currently using fedora 8.<br><br><br><br><div class="gmail_quote">On 9 Jan 2008 19:40:54 -0000, Mike Whincup <<a href="mailto:mwhincup@hotmail.com">mwhincup@hotmail.com </a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">------- You are receiving this mail because: -------<br> You are on the CC list for the bug, or are watching someone who is.<br><br><a href="http://bugs.kde.org/show_bug.cgi?id=143419" target="_blank">http://bugs.kde.org/show_bug.cgi?id=143419</a><br><br><br><br><br></div>------- Additional Comments From mwhincup hotmail com 2008-01-09 20:40 ------- <br>Guys,<br><br>I'm not sure whether to close this bug report now.<br><br>Since I upgraded to Suse 10.3 (and have been running compiz) I don't think I've suffered this problem.<br><br>Lubos, what do you think? <br></blockquote></div><br> This is not a KDE problem and it's been already fixed in Compiz. I am using Mandriva 2008 with KDE and Compiz and I STILL regularly get this bug. Usually it happens at first login but sometimes, like just now, it happens after i have been logged in for quite a while. It is VERY irritating! *** Bug 151168 has been marked as a duplicate of this bug. *** Lubos - I have faith that you know what you're talking about, and that the problem lies with Compiz or KWD. I'm just not sure how best to proceed - Others have the same symptoms. Can you give me a link so I can map this problem to KWD?... All I know is that in this Novell/SUSE bugreport I helped to fix the problem : https://bugzilla.novell.com/show_bug.cgi?id=304184 . But for Compiz problems you have to ask Compiz developers, sorry. *** Bug 157415 has been marked as a duplicate of this bug. *** *** Bug 157622 has been marked as a duplicate of this bug. *** *** Bug 158351 has been marked as a duplicate of this bug. *** Created attachment 23970 [details]
Generated bug kcrash report
Running Mandriva 2008.0 with kernel 2.6.22.18 The kde-window-decorator crashed while rpmdrake finished successfully the installation of xine-faad package. This kind of crash is still very rare for me and this distribution apparently. Yet I attached my crash report on the comment above. *** Bug 161184 has been marked as a duplicate of this bug. *** *** Bug 161485 has been marked as a duplicate of this bug. *** *** Bug 161636 has been marked as a duplicate of this bug. *** Я думаю это связано с программами в системном трее, в частности с kopete. *** Bug 161889 has been marked as a duplicate of this bug. *** *** Bug 152792 has been marked as a duplicate of this bug. *** *** Bug 206163 has been marked as a duplicate of this bug. *** *** Bug 220902 has been marked as a duplicate of this bug. *** *** Bug 227452 has been marked as a duplicate of this bug. *** *** Bug 228407 has been marked as a duplicate of this bug. *** *** Bug 229127 has been marked as a duplicate of this bug. *** *** Bug 229797 has been marked as a duplicate of this bug. *** *** Bug 231233 has been marked as a duplicate of this bug. *** Created attachment 42183 [details]
New crash information added by DrKonqi
After every boot of KDE, I see this error.
I use compiz + emerald.
(In reply to comment #52) > After every boot of KDE, I see this error. > I use compiz + emerald. You should report this crash to the Compiz developers. Adding it here won't fix the issue. Btw you are not using emerald - the crash report says you are using kwd *** Bug 231893 has been marked as a duplicate of this bug. *** *** Bug 232914 has been marked as a duplicate of this bug. *** Bug 232213 has a reference to the fix inside Compiz code for KDE4.4 code... *** Bug 233465 has been marked as a duplicate of this bug. *** *** Bug 264199 has been marked as a duplicate of this bug. *** (In reply to comment #58) > *** Bug 264199 has been marked as a duplicate of this bug. *** I do not think it is really a duplicate because: 1) I do not use compiz, I use kwin 2) The decorator crashes with segfault and restarts itself normally (In reply to comment #58) > *** Bug 264199 has been marked as a duplicate of this bug. *** Oh, and the platform is not at all OpenSUSE, it is kubuntu 1004 LTS. (In reply to comment #59) > (In reply to comment #58) > I do not think it is really a duplicate because: > 1) I do not use compiz, I use kwin From bug #264199: "Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault" You /do/ use compiz - running kde4-window-decorator together with kwin would be completely pointless and wrong. Also a crash in kde4-window-decorator while kwin is your windowmanager (or virtually everything bug compiz) wouldn't lead to anything onscreen, but the crashreport - which you could safely ignore since "running kde4-window-decorator together with kwin would be completely pointless and wrong" ;-P Most important is that the _reported_ crash is a crash in kde4-window-decorator and therefore it is (for now) a "duplicate" - even if the traces don't match exactly (still it's "outside", the reason are likely incompatible API/ABI versions) If you experience other crashes (which are really in kwin) you'll have to report them :) (In reply to comment #61) > (In reply to comment #59) > > (In reply to comment #58) > > I do not think it is really a duplicate because: > > 1) I do not use compiz, I use kwin > > From bug #264199: > "Application: KDE Window Decorator (kde4-window-decorator), signal: > Segmentation > fault" > > You /do/ use compiz - running kde4-window-decorator together with kwin would be > completely pointless and wrong. > Also a crash in kde4-window-decorator while kwin is your windowmanager (or > virtually everything bug compiz) wouldn't lead to anything onscreen, but the > crashreport - which you could safely ignore since "running > kde4-window-decorator together with kwin would be completely pointless and > wrong" ;-P > > Most important is that the _reported_ crash is a crash in kde4-window-decorator > and therefore it is (for now) a "duplicate" - even if the traces don't match > exactly (still it's "outside", the reason are likely incompatible API/ABI > versions) > If you experience other crashes (which are really in kwin) you'll have to > report them :) Hi Thomas, Thanks for coming back to me. ps -ef | grep -i kwin reports kwin running, so does top (which actually shows xorg + kwin are consuming a vaste amount of resources). compiz is not reported running. Best, What is going on here? hard to say. you probably ran compiz sometime in the past which successively launched kde4-window-decorator. when you re-replaced compiz by kwin, the decorator was not shut down by compiz, stored with the session and restarted with every login (doing nothing but sucking some resources, it's not a window manager by its own but just a compiz "plugin", so there's no _real_ conflict with kwin) at some point it then apparently crashed, but that should not have had any impact on kwin (the only result would be the crashdialog) - if there was really another issue (crash) with kwin in consequence it's not been in your report. Thanks Thomas. I think I will clean up the installation and see what happens. I agree w eshould consider it as invalid at this stage. |