Bug 152792

Summary: loose the title bar of windows when using konqueror
Product: [Applications] konqueror Reporter: louis_m_c
Component: generalAssignee: Konqueror Developers <konq-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: frank78ac
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Mandriva RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description louis_m_c 2007-11-23 17:43:01 UTC
Version:           3.5.7 (using KDE KDE 3.5.7)
Installed from:    Mandriva RPMs
OS:                Linux

(no debugging symbols found)
Using host libthread_db library "/lib/i686/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)
[Thread debugging using libthread_db enabled]
[New Thread -1228613936 (LWP 30422)]
(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  0xb780ec30 in QWidget::~QWidget$base ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0xb78685f8 in QButton::~QButton$base ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0xb7f52911 in KCommonDecorationButton::~KCommonDecorationButton$base ()
   from /usr/lib/libkdecorations.so.1
#9  0xb7face15 in KWinPlastik::PlastikButton::~PlastikButton$delete ()
   from /usr/lib/kde3/kwin3_plastik.so
#10 0xb7f558c4 in KCommonDecoration::~KCommonDecoration$base ()
   from /usr/lib/libkdecorations.so.1
#11 0xb7faff58 in KWinPlastik::PlastikClient::~PlastikClient$delete ()
   from /usr/lib/kde3/kwin3_plastik.so
#12 0x0805bdc2 in ?? ()
#13 0x08052fb0 in ?? ()
#14 0x08050ab9 in QWidget::setUpdatesEnabled ()
#15 0xb77d6f5d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0xb7da7875 in KWinModule::windowRemoved () from /usr/lib/libkdecore.so.4
#17 0xb7dac450 in KWinModulePrivate::removeClient ()
   from /usr/lib/libkdecore.so.4
#18 0xb7d9c7ae in NETRootInfo::update () from /usr/lib/libkdecore.so.4
#19 0xb7d9cb2d in NETRootInfo::event () from /usr/lib/libkdecore.so.4
#20 0xb7dada92 in KWinModulePrivate::x11Event () from /usr/lib/libkdecore.so.4
#21 0xb7e765b8 in KApplication::x11EventFilter ()
   from /usr/lib/libkdecore.so.4
#22 0x08053a3a in ?? ()
#23 0xb770afe5 in QWidget::setUpdatesEnabled ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x08069f80 in ?? ()
#25 0xbfeda048 in ?? ()
#26 0x00400000 in ?? ()
#27 0xb7c0901c in QWidget::setUpdatesEnabled ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0xb7c0901c in QWidget::setUpdatesEnabled ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x08092110 in ?? ()
#30 0xbfed9f58 in ?? ()
#31 0xb7719afe in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
Backtrace stopped: frame did not save the PC
Comment 1 Frank Reininghaus 2008-11-13 21:50:35 UTC
The backtrace is the same as in bug 161184, which is in turn a duplicate of another bug. It appears to be a Compiz problem that should be fixed now. A workaround is not to use kde-window-decorator.

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