Bug 730690 - search and replace broken in gedit
Summary: search and replace broken in gedit
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gedit
Version: 4.9
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-15 11:37 UTC by redhat@mrc-epid.cam.ac.uk
Modified: 2012-06-20 13:25 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:25:55 UTC


Attachments (Terms of Use)

Description redhat@mrc-epid.cam.ac.uk 2011-08-15 11:37:51 UTC
Description of problem:

Whe you try and serach or replace in gedit 2.8.1 an error message is generated

"Could not find the required widgets inside "/usr/share/ged-t-2/glade/replace.glade2". Please reinstall gedit.

The following console messages are produced

(gedit:10991): libglade-WARNING **: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory

(gedit:10991): libglade-WARNING **: unknown widget class 'GnomeEntry'

(gedit:10991): libglade-WARNING **: unknown widget class 'GnomeEntry'

(gedit:10991): Gtk-WARNING **: Ignoring the separator setting


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

2.8.1

How reproducible:

100%

Steps to Reproduce:
1. run gedit
2. click on Search or Replace or press CTRL-F or CTRL-R
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jiri Pallich 2012-06-20 13:25:55 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.


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