Bug 53527

Summary: resizing konsole leaves black bars on frame
Product: [Applications] konsole Reporter: Eggert Ehmke <eggert>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED FIXED    
Severity: normal CC: larson
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Eggert Ehmke 2003-01-28 18:20:40 UTC 
Version:            (using KDE KDE 3.1)
Installed from:    SuSE RPMs
OS:          Linux

This is  a fresh installed KDE 3.1 system with default display options, installed from SuSE 8.1 rpm's. When resizing the konsole from small to larger horizontally, in the lower frame there stay vertical lines. They disapear the next time the display is refreshed. Screenshots can be provided.
Comment 1 Waldo Bastian 2003-01-28 18:35:28 UTC 
Subject:  New: resizing konsole leaves black bars on frame

Which widget-style are you using?
Comment 2 Eggert Ehmke 2003-01-28 19:21:19 UTC 
Subject: Re:  resizing konsole leaves black bars on frame

> ------- You are receiving this mail because: ------- 
> You reported the bug, or are watching the reporter. 
>       
> http://bugs.kde.org/show_bug.cgi?id=53527      
 
> ------- Additional Comments From bastian@kde.org  2003-01-28 18:35 -------

> Subject:  New: resizing konsole leaves black bars on frame 
>  
> Which widget-style are you using? 
>  
Qt-CDE, but it happens with other styles too 
 
Eggert
Comment 3 Waldo Bastian 2003-01-29 12:48:47 UTC 
Subject: KDE_3_1_BRANCH: kdelibs/kdeui

CVS commit by waba: 

CCMAIL: 53527-done@bugs.kde.org
Backport fix for BR38274, BR38643, BR50920 and BR53527


  M +1 -1      ktoolbar.cpp   1.325.2.2


--- kdelibs/kdeui/ktoolbar.cpp  #1.325.2.1:1.325.2.2
@@ -1619,5 +1619,5 @@ void KToolBar::slotRepaint()
     QApplication::sendPostedEvents( this, QEvent::LayoutHint );
     setUpdatesEnabled( TRUE );
-    repaint( FALSE );
+    repaint( TRUE );
 }
Comment 4 Stephan Kulow 2003-05-21 15:04:29 UTC 
*** Bug 58735 has been marked as a duplicate of this bug. ***