fixed in hardy
right ?
** Changed in: gnome-terminal (Ubuntu)
Status: New => Fix Released
--
gnome-terminal unresponsive behavior in maximized or full screen mode
https://bugs.launchpad.net/bugs/159191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
This problem still exists in Ubuntu 8.04 beta. Again, it only happens
with the default visual appearance extras (compiz, I guess) but not
metacity. This has been an issue for almost 4 months without any
official acknowledgment. What gives? What additional details would be
helpful?
--
gnome-termin
same problem here with gutsy
--
gnome-terminal unresponsive behavior in maximized or full screen mode
https://bugs.launchpad.net/bugs/159191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gnome-terminal in ubuntu.
--
desktop-bugs m
I have the same problem. No response maximized.
I'm using Gutsy
Single display :)
--
gnome-terminal unresponsive behavior in maximized or full screen mode
https://bugs.launchpad.net/bugs/159191
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug co
I use a Dell D620 notebook, intel 945GM display controller, with default
drivers. I don't use multiple displays.
--
gnome-terminal unresponsive behavior in maximized or full screen mode
https://bugs.launchpad.net/bugs/159191
You received this bug notification because you are a member of Ubuntu
De
novaki wrote:
> I have the same problem. This only appeared in gutsy (feisty + compiz
> was ok). It's a really annoying bug, i have to press alt-TAB twice after
> pressing ctrl-T.
>
I've stopped using compiz entirely as a result of this (and other compiz
related bugs). Out of curiosity, do you u
I have the same problem. This only appeared in gutsy (feisty + compiz
was ok). It's a really annoying bug, i have to press alt-TAB twice after
pressing ctrl-T.
--
gnome-terminal unresponsive behavior in maximized or full screen mode
https://bugs.launchpad.net/bugs/159191
You received this bug not