Bug 574878 - Terminal plugin prevent the shortcut for closing bottom pane to work
Summary: Terminal plugin prevent the shortcut for closing bottom pane to work
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit-plugins
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Rakesh Pandit
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-18 18:34 UTC by Peter Janakiev
Modified: 2010-12-03 17:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 17:06:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Peter Janakiev 2010-03-18 18:34:36 UTC
Description of problem:
Shortcut to Open/Close bottom panel does not work when the terminal plugin is opened in the panel

Version-Release number of selected component (if applicable):
gedit-plugins-2.28.0-1.fc12.i686

How reproducible:
always

Steps to Reproduce:
1. start Gedit with terminal plugin enabled,
2. make the bottom panel visible (Ctrl+f9 by default) and switch to the terminal tab
3. press Ctrl+f9
  
Actual results:
ascii encoded symbol is displayed on the terminal

Expected results:
close the bottom pane of Gedit and focus the editing area

Additional info:
To close the pane with the terminal in it first the focus has to be taken away from the embedded terminal (using the mouse or Control TAB and then press control + f9 which is additional key stroke or mouse movement and slows down the cycle of editing text/running terminal commands which can be irritating

Comment 1 Rakesh Pandit 2010-05-17 06:09:24 UTC
I have started to look into it. Getting touch with upstream and check whether it is expected behaviour or not. I can reproduce it in all stable releases till now.

https://bugzilla.gnome.org/show_bug.cgi?id=618841

Comment 2 Rakesh Pandit 2010-05-17 08:39:43 UTC
https://bugzilla.gnome.org/show_bug.cgi?id=610978 Ugg I missed the already existing upstream bug report.

Anyway, lets wait a while for upstream fix.

Comment 3 Rakesh Pandit 2010-05-19 08:46:04 UTC
Just for note it is present in 2.31.1

Comment 4 Rakesh Pandit 2010-05-28 08:40:17 UTC
No response form upstream. Pinged again, will wait for a week more.

Comment 5 Bug Zapper 2010-11-03 19:15:51 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2010-12-03 17:06:42 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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