GNOME Bugzilla – Bug 528915
menubar and scrollbar visibility in new windows
Last modified: 2008-11-24 11:00:44 UTC
Reported on Launchpad: " In gnome-terminal's default profile I have set both the menubar and the scrollbar to invisible. If I create a new window with the context menu's "Open terminal" menuitem, then neither the menubar nor the scrollbar are shown in the new window, which is just fine. However, if I create a new window by dragging a tab to the root window, then both the menubar and the scrollbar are shown in the newly created window. ProblemType: Bug Architecture: i386 Date: Sat Apr 19 15:10:10 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/gnome-terminal Package: gnome-terminal 2.22.1-0ubuntu2 PackageArchitecture: i386 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash LC_PAPER=de_DE.UTF-8 SourcePackage: gnome-terminal Uname: Linux 2.6.24-16-generic i686" https://bugs.edge.launchpad.net/ubuntu/+source/gnome-terminal/+bug/219575
Created attachment 109562 [details] [review] show menubar and scrollbar in a window created by dragging a tab only when needed Patch by Gábor Szeder
From Launchpad: "If a new terminal window is created by dragging a tab to the root window, then both the menubar and the scrollbar are shown in the newly created window, even if they should be hidden according to the current profile. This happens because after this drag-drop-new window sequence notebook_page_added_callback() calls gtk_widget_show_all() on the newly created window widget, although the visibility of all its child widgets were explicitly set by gtk_widget_(show|hide)() according to the current profile. This fixes #208535 in Launchpad and #528915 in Gnome bugzilla. Signed-off-by: SZEDER Gábor <szeder@ira.uka.de> --- src/terminal-window.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)"
*** This bug has been marked as a duplicate of 513553 ***
*** Bug 545657 has been marked as a duplicate of this bug. ***
*** Bug 550227 has been marked as a duplicate of this bug. ***
*** Bug 562110 has been marked as a duplicate of this bug. ***