Double window controls in Chromium after enabling "Use System Title Bar and Borders"

Al steps are fixed except step 2, still double window controls when window is maximized.

Sorry tested it again, I was wrong. All steps are still valid. I was not maximized i guess

Yes, if I maximise then restore, this bug remains.

This bug is two issues in different components.

The first part (chromium draws its custom window controls when maximized in unity) was a problem with chromium and should be fixed in chromium r83173, in case you guys want to backport it. (It also has some other minor unity integration.)

The second part (unity "forgets" when a window has set gtk_window_set_decorated()) looks like a problem in unity and attempts at working around it in chromium haven't been successful. (I tried calling gtk_window_set_decorated(FALSE) when in the confused state and unity didn't respond.)

I've just discovered that this bug doesn't happen when chromium is launched in the maximized state with "Use System Title Bar and Borders" unchecked.

Steps:

1) Unset "Use System Title Bar and Borders";
2) Maximize Chromium;
3) Close Chromium;
4) Launch Chromium (it will open in the maximized state).

Result: Chromium will not show the double title-bar after maximized+unmaximized.

Tested with Chromium beta (14.0.835.109).

same problem with google-chrome 15
it's impossible to stay with settings/personal data/appearance set to "hide system bar" : the system bar keeps on coming back randomly (after maximize/minimize or suspend mode)
the setting in preferences dont change from its own : i have to switch system bar on and off again to get back the state i would like to keep

I have the following related problem, as mentioned elsewhere (and corrected here)
http://code.google.com/p/chromium/issues/detail?id=82050
What steps will reproduce the problem?
1. Open chromium
2. Make sure Chromium is not maximized (unmaximized, but not minimized)
3. Open Preferences
4. Select "Hide system title bar and use compact borders"
5. Note that title bar disappears, as expected
6. Maximize window
7. Un-Maximize

What is the expected result?
Title bar should not reappear.

What happens instead?
Title bar appears again, alongside the Chrome-provided window controls. Giving Chromium double window controls.

Sorry, also, I get this with the newly installed ubuntu 11.10, using chromium
14.0.835.202 (Developer Build 103287 Linux) Ubuntu 11.10

I use Ubuntu 11.10 and I see this issue as well. "Use system bar" fixes the issue, but I would prefer if "Hide system bar" worked as well.

Another issue here - close/minimize/maximize controls should be Unity themed (in case of "Hide system bar"), currently they are Chrome-themed and look too alien in Unity.

Same in Ubuntu 11.10 Unity 3D. Very annoying.

This doesn't happen anymore to me on precise, please check again and unmark this as invalid if you confirm that's fixed.

It still happens to me on Precise, so please don't mark it as being fixed yet.

PS. Although I use chrome, not chromium, but this shouldn't really make a difference at all. Unless the chromium was patched somehow in Ubuntu to fix the issue.

@Dawid Wróbel I can also reproduce the bug using chromium 18.0.1025.151 (Developer Build 130497 Linux) Ubuntu 12.04

Still happens with Chrome 22.0.1215.0 in Ubuntu 12.04

Still happens in 12.10.

Very simple testcase:

#include <gtk/gtk.h>

gboolean timeout(gpointer data) {
  gtk_window_unmaximize(GTK_WINDOW(data));
  return FALSE;
}

int main (int argc, char *argv[]) {
  GtkWidget *window;

  gtk_init(&argc, &argv);

  window = gtk_window_new(GTK_WINDOW_TOPLEVEL);
  g_signal_connect(window, "destroy", G_CALLBACK(gtk_main_quit), NULL);
  g_timeout_add(100, timeout, window);

  gtk_window_set_decorated(GTK_WINDOW(window), FALSE);
  gtk_window_maximize(GTK_WINDOW(window));

  gtk_widget_show(window);

  gtk_main();

  return 0;
}

The window should not have decorations, but it does.

Sorry folks, but as part of the bug clean up ahead of 16.04 LTS I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 LTS development cycle.

@Timothy: is this bug still affecting you with recent releases of chromium and unity?

Closing because of lack of feedback from original reporter. I cannot observe the issue on xenial with the latest chromium.