Bug 80386 - mouse click on mc running in gnome-terminal causes freeze-up
mouse click on mc running in gnome-terminal causes freeze-up
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: vte (Show other bugs)
phoebe
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
:
: 80831 (view as bug list)
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2002-12-25 11:54 EST by Need Real Name
Modified: 2008-05-01 11:38 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-13 22:47:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2002-12-25 11:54:19 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
If I run mc in a gnome terminal and mouse-click within the terminal window (but
not on the window borders, menu bar, etc), then the terminal "freezes" --
doesn't respond to keyboard input.

Using the "terminal" -> "reset and clear" entry from the menu bar will
"unfreeze" the terminal.  Openning a new term window and killing the mc process
does not "unfreeze" the terminal.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Open a new gnome-terminal
2. Run mc
3.
    

Actual Results:  Term stops responding to keyboard input

Expected Results:  Should be able to click within a gnome-terminal running mc
and not experience a "freeze-up".

Additional info:
Comment 1 Bill Nottingham 2002-12-31 00:17:31 EST
Also happens with aumix. Probably libgpm related.
Comment 2 Bill Nottingham 2003-01-13 22:47:23 EST
Fixed in 0.10.9-1.
Comment 3 Nalin Dahyabhai 2003-01-13 23:28:08 EST
*** Bug 80831 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.