Bug 283235

Summary: kde window decoretor
Product: [I don't know] kde Reporter: sayeed <mamdudsayed>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: mamdudsayed
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: New crash information added by DrKonqi
New crash information added by DrKonqi

Description sayeed 2011-10-03 11:04:51 UTC
Application: kde4-window-decorator (0.0.1)
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.7.0
Operating System: Linux 2.6.39.4 i686
Distribution: Ubuntu 10.04.2 LTS

-- Information about the crash:
- What I was doing when the application crashed:
after install display driver doing reboot
- Unusual behavior I noticed:
keyboard hot key not working,not showing close/maximize button title bar
- Custom settings of the application:
no custom settings

The crash can be reproduced every time.

-- Backtrace:
Application: KDE Window Decorator (kde4-window-decorator), signal: Segmentation fault
[KCrash Handler]
#7  0x574b334e in ?? ()
#8  0xb647d987 in KDecorationUnstable::compositingActive (this=0x82715d8) at ../../../kwin/lib/kdecoration.cpp:406
#9  0xabf98f93 in Aurorae::AuroraeClient::init (this=0x82715d8) at ../../../../../kwin/clients/aurorae/src/aurorae.cpp:204
#10 0x0805a26e in KWD::Window::createDecoration (this=0x8246288) at ../../../kde/window-decorator-kde4/window.cpp:764
#11 0x0805deae in Window (this=0x8246288, parentId=25165858, clientId=172, frame=0, type=KWD::Window::Default, x=0, y=0, w=1, h=1) at ../../../kde/window-decorator-kde4/window.cpp:152
#12 0x08057146 in KWD::Decorator::enableDecorations (this=0x80fa150, timestamp=62908) at ../../../kde/window-decorator-kde4/decorator.cpp:212
#13 0x0805066d in main (argc=1, argv=0xbfc9a1e4) at ../../../kde/window-decorator-kde4/main.cpp:113

Reported using DrKonqi
Comment 1 sayeed 2011-10-03 11:09:52 UTC
Created attachment 64160 [details]
New crash information added by DrKonqi

kde4-window-decorator (0.0.1) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0

- What I was doing when the application crashed:after reboot pc

- Unusual behavior I noticed:

not open application kde window decorator

-- Backtrace (Reduced):
#8  0xb64bb987 in KDecorationUnstable::compositingActive (this=0x8ae7128) at ../../../kwin/lib/kdecoration.cpp:406
#9  0xabfd6f93 in Aurorae::AuroraeClient::init (this=0x8ae7128) at ../../../../../kwin/clients/aurorae/src/aurorae.cpp:204
#10 0x0805a26e in KWD::Window::createDecoration (this=0x8ae7760) at ../../../kde/window-decorator-kde4/window.cpp:764
#11 0x0805deae in Window (this=0x8ae7760, parentId=39845922, clientId=172, frame=0, type=KWD::Window::Default, x=0, y=0, w=1, h=1) at ../../../kde/window-decorator-kde4/window.cpp:152
#12 0x08057146 in KWD::Decorator::enableDecorations (this=0x895c150, timestamp=3278217) at ../../../kde/window-decorator-kde4/decorator.cpp:212
Comment 2 sayeed 2011-10-03 11:09:52 UTC
Created attachment 64161 [details]
New crash information added by DrKonqi

kde4-window-decorator (0.0.1) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0

- What I was doing when the application crashed:after reboot pc

- Unusual behavior I noticed:

not open application kde window decorator

-- Backtrace (Reduced):
#8  0xb64bb987 in KDecorationUnstable::compositingActive (this=0x8ae7128) at ../../../kwin/lib/kdecoration.cpp:406
#9  0xabfd6f93 in Aurorae::AuroraeClient::init (this=0x8ae7128) at ../../../../../kwin/clients/aurorae/src/aurorae.cpp:204
#10 0x0805a26e in KWD::Window::createDecoration (this=0x8ae7760) at ../../../kde/window-decorator-kde4/window.cpp:764
#11 0x0805deae in Window (this=0x8ae7760, parentId=39845922, clientId=172, frame=0, type=KWD::Window::Default, x=0, y=0, w=1, h=1) at ../../../kde/window-decorator-kde4/window.cpp:152
#12 0x08057146 in KWD::Decorator::enableDecorations (this=0x895c150, timestamp=3278217) at ../../../kde/window-decorator-kde4/decorator.cpp:212
Comment 3 Christoph Feck 2011-10-03 15:33:18 UTC

*** This bug has been marked as a duplicate of bug 232213 ***