Bug 165688 - KDE Window decorator crashes
Summary: KDE Window decorator crashes
Status: RESOLVED NOT A BUG
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-04 08:33 UTC by Mark van Beek
Modified: 2009-02-06 04:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
crash backtrace (3.75 KB, text/plain)
2008-07-04 08:34 UTC, Mark van Beek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mark van Beek 2008-07-04 08:33:12 UTC
Version:            (using KDE 4.0.83)
Installed from:    SuSE RPMs
OS:                Linux

Not much to add, lost the window decorations so now I can't move/handle my windows anymore.

FYI. I use Compiz 0.74.

ps. I couldn't find the right application name in the list(KDE window decorator was given in the crash handler). If someone can set it right, it would be great (and I will know what to chose next time).
Comment 1 Mark van Beek 2008-07-04 08:34:01 UTC
Created attachment 25823 [details]
crash backtrace
Comment 2 lucas 2008-07-04 10:35:02 UTC
"no debugging symbols found" means that the backtrace is not useful. If you can reproduce the crash, you should install the debug enabled packages before providing again the backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

However as you are using Compiz and not KWin you should submit the bug to them instead.
Comment 3 Mark van Beek 2008-07-04 11:15:15 UTC
Ok Lucas, I'll have a look at your link and the debugging packages. One question: If according to you it's due to Compiz, why does the crash handler report 'KDE window decorator'? Will this also become more clear if I'll install the debug packages?
Comment 4 lucas 2008-07-04 11:52:15 UTC
The exact cause will be present in the backtrace. As for the "KDE Window Manager" I'm not 100% sure but I think that's because of KDE loading Compiz when you login.

Does it crash on start up or when after a certain amount of time?
What happens if you start Compiz manually in the console, is the crash the same?
Comment 5 Mark van Beek 2008-07-04 12:21:16 UTC
Last night it started up and ran ok. This morning (didn't turn it off or logged out) it crashed.
Not at home, so can't try to start it manually now...
Comment 6 lucas 2008-07-04 12:25:42 UTC
Reopening just on the off-chance that it's a session bug or whatever.
Comment 7 Lubos Lunak 2008-07-04 13:36:45 UTC
It is called 'KDE window decorator' because that's how Compiz calls one of its components. It still remains a Compiz bug though, please report to them.

Comment 8 Mark van Beek 2008-07-04 14:06:24 UTC
Ok, I'll try to gather more (de)bug info and submit to Compiz(-Fusion).

Thanks
Comment 9 James Shiflett 2009-02-05 23:07:31 UTC
I'm presently using PCLOS.

When I had this problem, every time I logged into my profile, I kept getting Kwin crash errors. And every time I tried to open "window Decorations" in Control Center, I would get kde-window-decorator crashes. I was able to backtrack it, and I got this output:

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(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 -1236535600 (LWP 3454)]
(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)
[KCrash handler]
#6  0xb73bdaae in QImage::isNull () from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb7440575 in QImage::copy () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb61aadfd in LunaMet::LunaMetHandler::loadPixmap ()
   from /usr/lib/kde3/kwin3_lunamet.so
#9  0xb61ae210 in LunaMet::LunaMetHandler::createPixmaps ()
   from /usr/lib/kde3/kwin3_lunamet.so
#10 0xb61aa506 in LunaMet::LunaMetHandler::LunaMetHandler ()
   from /usr/lib/kde3/kwin3_lunamet.so
#11 0xb61aa69d in create_factory () from /usr/lib/kde3/kwin3_lunamet.so
#12 0xb62666e2 in KDecorationPlugins::loadPlugin ()
   from /usr/lib/libkdecorations.so.1
#13 0xb62c253e in KWinInternal::PluginMgr::PluginMgr ()
   from /usr/lib/libkdeinit_kwin.so
#14 0xb62ec760 in KWinInternal::Workspace::Workspace ()
   from /usr/lib/libkdeinit_kwin.so
#15 0xb62ecbe8 in KWinInternal::Application::Application ()
   from /usr/lib/libkdeinit_kwin.so
#16 0xb62ed0b0 in kdemain () from /usr/lib/libkdeinit_kwin.so
#17 0xb7f79784 in kdeinitmain () from /usr/lib/kde3/kwin.so
#18 0x0804e4c5 in ?? ()
#19 0x0804edf2 in ?? ()
#20 0x0804f1ad in ?? ()
#21 0x08050378 in ?? ()
#22 0xb6e6475c in __libc_start_main () from /lib/i686/libc.so.6
#23 0x0804b811 in ?? ()


OK... So that's mostly a lot of stuff that I have NO WAY of understanding...

:-)

However, I DID notice the part about the "lunaMetHandler", and I realized that the last kde decoration that I tried was "Luna Metal"... so I went into Synaptic package manager, and completely removed the package called "kdemoreartwork-lunamet", and the next time I logged into my profile, the problem had went away, and when I tried to open up Window Decorations, it would then open, and it had defaulted back to the "KDE2" window decoration.

So I'm guessing that there was a problem between Compiz-Fusion and that particular kde window decoration.

Note: in order to "Backtrack" the error, I had to first install"kdbg" in Synaptic. That was further complicated by the fact that I had system slowdown problems, due to a corrupted filesystem... which of course, I had to fix by forcing a file check...

I sure do like linux, but MAN it can get pretty complicated sometimes.

Anyway, I hope this helps.
Comment 10 lucas 2009-02-06 04:19:33 UTC
kde-window-decorator is a Compiz project, please report the crash to them.