Ubuntu
gaim package

Black background in conversations after upgrade to 2.0beta3

Bug #52802 reported by Matt Zimmerman
4
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Low
Unassigned

Bug Description

After upgrading to the current gaim in Edgy (1:2.0.0+beta3-4ubuntu2), my conversation window has a black background, which makes the text unreadable (black on black). Will attach a screenshot.

Revision history for this message
Matt Zimmerman (mdz) wrote : Screenshot

Screenshot

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report. As the upstream bug tracker doesn't have such a bug - does this happen with other themes as well? Maybe that's our favourite pet bug, bug 34435?

Changed in gaim:
assignee: nobody → desktop-bugs
importance: Untriaged → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Gerr (jeremy-gunix) wrote :

I consulted with the people on #gaim and learned that using control-R resolves the problem.

Go to the preferences window where the black on black text box is shown (2.0b3 has this page at least) and click in the black box. Then use the control sequence. The next time an IM window is opened, the problem should be cleared up.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Daniel, it happened to gaim on my desktop too when I updated from 1.5 to 2.0beta1, for jabber, I've mentionned it on bug #28361. That's easy to fix from the preferences but should not happen on upgrade

Daniel Holbach (dholbach)
Changed in gaim:
status: Needs Info → Confirmed
Revision history for this message
Akkana Peck (akkzilla) wrote :

Still happening: I just hit this in a newly installed feisty (using existing preferences from an older gaim, of course). Fortunately this bug was the first google hit and ctrl-R fixed it (thanks, Gerr!)

Sebastien Bacher (seb128)
Changed in gaim:
assignee: desktop-bugs → nobody
importance: Medium → Low
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your report, do you get the same with pidgin in Intrepid or Jaunty?.

Changed in gaim:
status: Confirmed → Incomplete
Revision history for this message
Matt Zimmerman (mdz) wrote :

I have not seen this since the original occurrence. I followed the prescribed workaround which I assume is persistent

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Ok thanks you, Please open a new bug against Pidgin if you encounter the same issue with it.

Changed in gaim:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.