Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 174713 - newly-created tabs are often "frozen"
Summary: newly-created tabs are often "frozen"
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-terminal
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Behdad Esfahbod
QA Contact:
Whiteboard: bzcl34nup
Depends On:
Blocks: FC7Target
TreeView+ depends on / blocked
Reported: 2005-12-01 17:08 UTC by Zack Cerza
Modified: 2018-04-11 11:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-05-07 00:18:29 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
GNOME Bugzilla 125364 None None None Never

Description Zack Cerza 2005-12-01 17:08:25 UTC
Description of problem:
When a new tab is created, it is often "frozen" in that the contents of the
terminal is not updated until the user switches to a previously-working tab and
back again. Commands do work - typing 'exit<CR>' closes the frozen tab.

In one of my current terminal windows open now, 14 out of 17 tabs are frozen.

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

How reproducible:
Almost always.

Steps to Reproduce:
1. Open gnome-terminal
2. Create a new tab
3. Type stuff.
Actual results:
Nothing shows up.

Expected results:
The stuff you type shows up.

Additional info:

Comment 1 Dave Malcolm 2005-12-06 20:59:59 UTC
Seeing similar symptoms on i386

Seems to affect some tabs, but not others.  I've taken to opening tabs until I
get an unaffected tab, then going back and closing the tabs that are affected.

Comment 2 Dave Malcolm 2005-12-06 21:13:58 UTC
I also sometimes get an entirely blank black tab; switching tabs forwards and
back gets the tab redrawn, but such a tab is still affected by the bug.

Comment 3 Dave Malcolm 2005-12-06 22:43:09 UTC
Looks like a repaint/expose problem; if you drag a window over one of the tabs,
it repaints the stuff in the terminal tab that's changed.
e.g. type "ls"<ENTER> in one of the tabs; nothing appears to happen; no keypress
feedback, but drag a window in front to force repainting and you see the results
of your ls (and the entry of the command)

Comment 4 Ray Strode [halfline] 2006-01-11 19:55:39 UTC
Hey Dave, Zack,

Are you guys still seeing this?

Comment 5 Zack Cerza 2006-01-11 23:28:09 UTC
The last time I used the machine was Friday, and I was seeing it then.

Comment 6 Ray Strode [halfline] 2006-01-27 21:05:32 UTC
how about now?

Comment 7 Zack Cerza 2006-01-31 01:00:46 UTC


Comment 8 Matthias Clasen 2006-02-14 20:23:43 UTC
seems to be an upstream bug tracking this issue.
Given that it is an old issue, and rare, move to FC6Target

Comment 9 Zack Cerza 2006-02-14 21:12:05 UTC
Maybe it's 'rare' for i386 users... but I reproducibly have to create 15-20
unusable new tabs for each usable one on my x86_64 boxes. Ouch.

Explicitly adding the GNOME bug as a reference.

Comment 10 Matthias Clasen 2006-07-06 22:02:03 UTC
Add to FC6Destop tracker

Comment 11 Matthias Clasen 2006-08-24 02:54:38 UTC
Zack, are you still seeing this on x68_64 ? I have not been able to reproduce it
on i386

Comment 12 Zack Cerza 2006-08-24 14:48:40 UTC
Matthias, yes I am. I can show you today if you want.

Comment 13 Behdad Esfahbod 2006-08-24 15:32:06 UTC
You see this in devel?!

Comment 14 Zack Cerza 2006-08-24 15:45:25 UTC
Behdad, yes. I'm sorry.

I don't think I ever saw it in FC5, which I was using for a while on this
system, but I can reliably reproduce it in rawhide. I'll do it again right now.
There. :)

Comment 15 Matthias Clasen 2006-09-21 19:02:53 UTC
Hmm, I just opened 50 tabs on our x86_64 test machine, which has a pretty recent
rawhide, and not a single one froze.

Zack, you still see this ? 

Comment 16 Zack Cerza 2006-09-25 17:23:50 UTC
Yes, I'm still seeing it. A lot. :(

Comment 17 Erik van Pienbroek 2006-09-25 22:02:14 UTC
I'm also noticing this bug with my x86_64 machine running rawhide

Comment 18 sean 2006-11-17 23:01:24 UTC

Any new tab is frozen. Always.

This started for me after fc6.


Comment 19 sean 2006-12-06 22:51:43 UTC


as an old package fixes this.

Is this an upsteam issue? only on x86-64?

Comment 20 Matěj Cepl 2007-03-07 15:22:05 UTC
I can fully reproduce it on x86_64 RHEL-5-Gold, but when I switched off ATK,
things are suddenly OK (the idea with ATK is from bug 224611, which is quite

Comment 21 Erik van Pienbroek 2007-03-07 15:33:04 UTC
A while ago I was already having this problem. After a reinstall everything
worked fine for a while, but since a few weeks the problem has returned, though
it is a little bit different behaviour this time. The first time the problem was
newly created tabs are often frozen (as the title of this bugzilla entry says
:P), but this time the problem occurs a while after creating a new tab. The
scrollbar itself behaves fine, but the terminal itself isn't getting any screen
refreshes. Terminal I/O seems to work just fine, it's just the screen refreshes
that are broken.

Comment 22 Mladen Kuntner 2007-03-13 22:26:01 UTC
Just want to say me to.
On a updated rawhide with

I think i first saw that after fresh FT2 install.

Comment 23 Bug Zapper 2008-04-03 16:40:03 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:

We will be following the process here: to ensure this
doesn't happen again.

Comment 24 Bug Zapper 2008-05-07 00:18:27 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:

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