Red Hat Bugzilla – Bug 84416
Mouse does not select through gnome-terminal
Last modified: 2015-01-07 19:03:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030211
Description of problem:
I cannot use the mouse to slect functions through gnome-terminal. It resembles
more of a bitmap. No functions work through the mouse.
The function keys work fine.
I also checked out mc through xterm. mc works fine through xterm. It also works
fine during text mode.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.type mc to launch midnight commander
3.try clicking on the files or buttons, with the mouse. Three clicks inverts the
colors, still no functions.
Actual Results: No actions were able to be initialized, when clicked upon.
Function keys worked fine.
Expected Results: Expected the file or folder to be selected. Double clicking
expected opening of directories.
with straight Phoebe. The problem is there.
After upgrading to gnome-terminal-2.2.1-3, the bug was still present.
After upgrading to mc-4.6.0-1, the bug is still haunting the program.
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?
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.