[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 58034] New: kmail race condition: a messagebox seems to have
From:       holger-kde () holgis ! net
Date:       2003-05-02 19:59:05
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=58034     
           Summary: kmail race condition: a messagebox seems to have eaten
                    moudeup event
           Product: kmail
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kmail@kde.org
        ReportedBy: holger-kde@holgis.net


Version:            (using KDE KDE 3.1.1)
Installed from:    Gentoo Packages

Hi,

this sounds quite strange, i know, but this is what i did:

i had kmail running, the version from the kroupware people.

i wrote a mail to somebody, and sent it. then i clicked on the scrollbar button on \
the right of the upper right window of kmail, the messages window to scroll down some \
messages. i held down the mouse, and then a message box appeared, which told me that \
the mail i tried to send was not accepted by my mail server, because it didnīt relay \
messages and the pop-before-smtp timeout was timed out... the strange thing was, that \
the messages window kept scrolling down all the time, even after i clicked ok in the \
message box. then i clicked on the "scroll down arrow" again and released it, and \
then the window stopped scrolling.

the messages window should stop scrolling, when the mouse is released again, no \
matter who eats the missing button up event...

it seems like this is some kind of race condition, and i donīt know if it is \
reproducable at all, and i donīt know if it is only the case in kmail, or if it can \
happen in all kde- or qt-programs, but i wanted to file this bug report, before i \
forget about it again ;-)

thanks, Holger


[prev in list] [next in list] [prev in thread] [next in thread]