The following reply was made to PR user/6323; it has been noted by GNATS.

From: Thomas Pfaff <[email protected]>
To: [email protected]
Cc:  
Subject: Re: user/6323: cwm(1) menus pops up when clicking inside windows at 
certain places.
Date: Sun, 11 Apr 2010 19:28:59 +0200

 On Wed, 24 Feb 2010 15:56:47 +0100
 Thomas Pfaff <[email protected]> wrote:
 
 > >Number:         6323
 > >Category:       user
 > >Synopsis:       cwm(1) menu pops up when clicking inside windows at certain 
 > >places.
 > >Confidential:   yes
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    bugs
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   unknown
 > >Arrival-Date:   Wed Feb 24 15:10:02 GMT 2010
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     
 > >Release:        
 > >Organization:
 > >Environment:
 >      System      : OpenBSD 4.7
 >      Details     : OpenBSD 4.7-beta (GENERIC.MP) #34: Mon Feb  1 15:28:11 
 > CET 2010
 >                       
 > [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 > 
 >      Architecture: OpenBSD.amd64
 >      Machine     : amd64
 > >Description:
 >         When clicking at certain places inside a window, the menu_cmd and
 >         menu_unhide menu will pop up.  This should only happen when clicking
 >         in the root window.
 > >How-To-Repeat:
 >      See http://www.tp76.info/menu_unhide for example applications that are
 >         marked in the position where the menu will pop up.
 > >Fix:
 >      Don't know.
 > 
 > 
 > dmesg:
 > OpenBSD 4.7-beta (GENERIC.MP) #34: Mon Feb  1 15:28:11 CET 2010
 >     [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 
 I updated the system to a newer snapshot and this problem no longer exist.
 
   $ sysctl kern.version
   kern.version=OpenBSD 4.7-current (GENERIC.MP) #133: Tue Mar 23 21:32:16 MDT 
2010
       [email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 
 I don't know what fixed it but it doesn't seem to have anything to do with
 changes made to cwm.  A cwm checkout of an older version (January) did not
 have this problem either.  Something else made this problem go away.
 
 Is anyone else still seeing this problem?

Reply via email to