Bug 84416
Summary: | Mouse does not select through gnome-terminal | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Jim Cornette <jim.cornette> |
Component: | vte | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WORKSFORME | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | phoebe | CC: | jim.cornette, mitr, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-02-21 23:25:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jim Cornette
2003-02-16 10:48:07 UTC
What version of vte do you have installed? I upgraded from psyche to the second version of phoebe. The same problem is present on both computers. You can select any function key, but you cannot click on an item to activate menus, launch files or change directories. Also, after exiting mc, the cursor seems to locate itself about 2 lines down the gnome-terminal screen. It doesn't exit to the prompt. If you change to the screen, while in mc, with the ctl-o combination works alright. The prompt is located in the proper position. mc works properly within xterm or within a normal login screen. The installed version of mc is 4.6.0-1 The installed version of gnome-terminal is 2.2.1-3 Q: What version of vte do you have installed? A: vte-0.10.12-1 Sorry! I installed vte-0.10.20-1 to see if any differences were noticed. The prompt was still messed up upon exiting the screen. mc was still no more than a bitmap. Clicking on any item still does not work. Any more ideas as to what could cause this action? The problem went away with an upgrade to phoebe3. Closing bug |