Bug 100420 - gnome-terminal open tab twice, all black?
Summary: gnome-terminal open tab twice, all black?
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: vte   
(Show other bugs)
Version: 4.0
Hardware: All Linux
Target Milestone: ---
: ---
Assignee: Tomáš Bžatek
QA Contact:
Keywords: Regression, Reopened
: 110109 134466 (view as bug list)
Depends On:
Blocks: CambridgeTarget
TreeView+ depends on / blocked
Reported: 2003-07-22 09:18 UTC by Warren Togami
Modified: 2015-03-03 22:27 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 16:13:59 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
redraw vte screen when unobscured visibility event is caught (709 bytes, patch)
2004-10-27 19:30 UTC, Jon Nettleton
no flags Details | Diff

Description Warren Togami 2003-07-22 09:18:39 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703

Description of problem:
First noticed this minor quirk in Severn beta 9.0.93.

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

How reproducible:

Steps to Reproduce:
1. Open gnome-terminal with default settings.
2. CTRL-SHIFT-t once.
3. CTRL-SHIFT-t again.

Actual Results:  
Black fills the window except for the prompt.

Expected Results:  
Should be all white like the previous tab.

Comment 1 Havoc Pennington 2003-08-07 21:37:18 UTC
Predict this is a vte issue, gnome-terminal hasn't really changed.

Comment 2 George Karabin 2003-09-06 15:50:54 UTC
FWIW, I can't reproduce this on today's Rawhide. I haven't looked for the bug
before, though, so I can't say if it's been fixed, or if it's just something
that works on my machine.

Comment 3 Alexandre Oliva 2003-09-06 19:11:22 UTC
I still get the problem with gnome-terminal-2.3.2-1 and vte-0.11.10-2 (both in
rawhide and Severn updates).

Comment 4 Miloš Komarčević 2003-09-18 22:29:35 UTC
I'm still seeing this with gnome-terminal- and vte-0.11.10-4

Comment 5 Joe Orton 2003-10-07 13:25:12 UTC
Moi aussi. Sometimes it takes more than two Ctrl-T's to get the black screen.


Comment 6 Bart Martens 2004-02-16 22:06:27 UTC
The problem is known upstream, see:

Comment 7 Bart Martens 2004-02-16 22:14:38 UTC
I suggest to mark bug #110109 as a duplicate of *this* bug.

Comment 8 Alexandre Oliva 2004-02-16 23:42:05 UTC
*** Bug 110109 has been marked as a duplicate of this bug. ***

Comment 9 Albert Strasheim 2004-04-07 14:33:42 UTC
The black background is displayed when opening the third, fourth, etc.
tab, but not for the first two

Closing all but the first tab and creating a new tab (i.e. a new
second tab) still gives a white background, but opening a third tab
again gives a black background.

Switching from a tab with a black background to another tab and back
again fixes the background (i.e. makes it white).

Comment 10 Warren Togami 2004-04-14 04:02:33 UTC
seems to be fixed for me in latest rawhide with these versions.  Can
anyone else confirm?

Comment 11 Alexandre Oliva 2004-04-15 01:40:46 UTC
I still get it with yesterday's rawhide (>= than yours):

Comment 12 Ray Strode [halfline] 2004-10-04 16:26:34 UTC
*** Bug 134466 has been marked as a duplicate of this bug. ***

Comment 13 Jon Nettleton 2004-10-27 19:30:16 UTC
Created attachment 105863 [details]
redraw vte screen when unobscured visibility event is caught

Comment 14 Jon Nettleton 2004-10-27 19:32:44 UTC
forgot to paste my comments sorry.

This issue seems to be caused by a race condition between the
visibility event and the configure-event.  The terminal knows it is
visible, and the vte_terminal_configure_toplevel callback is attached,
but the configure-event never happens.  My most elegant solution has
been to run vte_invalidate_all on the terminal when the visibility
event is caught and it's state is UNOBSCURED.

Comment 15 Panu Matilainen 2004-10-28 11:57:02 UTC
Patch seems to have the desired effect. Thanks Jon, this has been
bugging me too for quite a while...

Comment 16 Warren Togami 2004-11-01 04:36:54 UTC
Please add this patch to vte too.

Comment 18 Ray Strode [halfline] 2004-11-05 03:47:26 UTC
Patch added to rawhide.

Comment 19 Adrian 2005-03-07 15:54:38 UTC
The bug is still in FedoraCore3, which provides vte-0.11.11-6. There
is no standard update (in "updates-released" repository) available for
yum. So, the usual update command:

  yum update

doesn't solve the bug.

The vte version available in the "development" repository
(vte-0.11.11-15) seems to solve the problem. I've installed it with:

  rpm --import /usr/share/rhn/RPM-GPG-KEY-fedora-test
  yum --enablerepo=development update vte

It would be useful to have the solution available in the
"updates-released" repository for an easier update. Any possibility to
be donne?

[In Gnome Bugzilla, Olav recommends to upgrade to vte 0.11.12:
http://bugzilla.gnome.org/show_bug.cgi?id=169207 ]

Comment 20 Zack Cerza 2006-08-21 20:33:21 UTC
Everyone's favorite bug is back again.

On the creation of the first tab, the terminal is all white (no prompt or
anything). On the creation of the second tab, the terminal is all black. Both
new tabs are unresponsive. Switching to a different tab and back again will
force an update, but it still does not respond interactively.


Comment 21 Warren Togami 2006-08-21 21:28:00 UTC
I don't see this problem with vte-0.13.6-1.fc6.i386.

Comment 22 Zack Cerza 2006-08-21 21:30:45 UTC
Are you on i386 or x86_64? Also, try turning on accessibility. It may just
happen more often if you do.

Comment 23 Warren Togami 2006-08-21 21:38:10 UTC
i386 here.  How do I turn on accessibility?

Comment 24 Zack Cerza 2006-08-21 21:47:11 UTC
You can turn on accessibility via this super-quick menu shortcut:

System->Preferences->Accessibility->Assistive Technology Support->Enable
assistive technologies

For me, the various incarnations of this bug have always occurred far more often
on x86_64 than on i386.

Comment 25 Warren Togami 2006-08-29 04:59:32 UTC
I'm seeing this on i386 FC6 without Accessibility enabled.  I am guessing this
has some timing basis as it doesn't always happen.

Comment 26 Kyrre Ness Sjøbæk 2007-05-30 15:25:28 UTC
Hmm.. I'm not seeng this on FC5, never has (or FC6). But i see it regularly on
RHEL (WS 4? i think so).

Comment 27 petrosyan 2007-12-17 18:22:41 UTC
FC5 and FC6 are not supported anymore. Can anyone reproduce this bug on F7 or F8?

Comment 28 Kyrre Ness Sjøbæk 2007-12-18 14:39:24 UTC
I have never seen it on newer FC, but I do think it does occur on RHEL, as
stated in #26. Somebody should probably test that (The RHEL I have access to is
an hour away from here (to acess the console of the machines directly, without
SSH), and it is quite heavily modified...)

Comment 29 petrosyan 2008-02-28 20:10:18 UTC
reassigning to RHEL 4

Comment 30 Jiri Pallich 2012-06-20 16:13:59 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.