Bug 719918 - text view can not be read
Summary: text view can not be read
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: xchat-gnome
Version: 15
Hardware: i686
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-08 12:07 UTC by Arif Tri Waluyo
Modified: 2014-03-17 03:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-12 16:31:09 UTC
Type: ---

Attachments (Terms of Use)
xchat-gnome (517.64 KB, image/png)
2011-07-08 12:07 UTC, Arif Tri Waluyo 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Arif Tri Waluyo 2011-07-08 12:07:50 UTC 
Created attachment 511926 [details]
xchat-gnome

Description of problem:
text view can not be read.

Version-Release number of selected component (if applicable):
Installed Packages
Name        : xchat-gnome
Arch        : i686
Version     : 0.26.2
Release     : 2.git40c5bf988.fc15
Size        : 6.0 M
Repo        : installed
From repo   : updates-testing
Summary     : GNOME front-end to xchat
URL         : http://live.gnome.org/Xchat-Gnome
License     : GPLv2+
Description : xchat-gnome is a new frontend for the popular X-Chat IRC client.
            : GNOME's philosophy in terms of user interfaces has been
            : progressing towards presenting the user with few options, yet sane
            : defaults. While many of the normal X-Chat options will be
            : preserved inside GConf, only the most common settings will be
            : included in the main user interface. .


How reproducible:
always

Steps to Reproduce:
1.Run xchat-gnome
Comment 1 Bill Nottingham 2011-07-11 17:58:43 UTC 
Does it work if you turn off background transparency?
Comment 2 Arif Tri Waluyo 2011-07-12 03:13:03 UTC 
After I delete all the configurations in home folder. All returned to normal. It looks like these bugs can be closed.
Note You need to log in before you can comment on or make changes to this bug.