Tab bar is not displayed when there is only one page open in a window

Bug #1099828 reported by Sébastien Maccagnoni-Munch
336
This bug affects 67 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Unknown
Unknown
WebApps: unity-chromium-extensions
Fix Released
High
Alexandre Abreu
chromium-browser (Ubuntu)
Fix Released
High
Chad Miller

Bug Description

On Ubuntu 12.10 with Chromium version 23.0.1271.97, the tab bar is not shown when there is only one tab open.

On Ubuntu 12.04 with the same Chromium version, the problem does not appear.
On Windows with Chrome with the same version number, the problem does not appear.

You can see a screenshot of the bug here : http://img849.imageshack.us/img849/7515/chromewp.png

Revision history for this message
Tyler Stacey (tylerastacey) wrote :

Confirming that I am experiencing the same issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
description: updated
description: updated
Revision history for this message
Kim Laroux (withered-angel) wrote :

Same problem here with Kubuntu 12.10 and Chromium 23.0.1271.97-0ubuntu0.12.10.1

Very annoying, as I now have to click on two buttons to open a new tab. Also, drag-drop text into the empty tab bar does not open a new tab and search for the dragged text if no tabs are shown. It's as if the whole tab bar is not really there, but is replaced by an empty space to have a place for the window buttons. If you use the system's titlebar, you can see that the tab bar does indeed disappears, confirming this theory.

Using system title bar and border:
http://postimage.org/image/yz0y1ad5j/

Without system title bar and borders:
http://postimage.org/image/wganmv21j/

When using system decorations, it actually makes sense. The tab bar simply hides when it contains a single bar. Though it's still a bad idea, because it removes the powerful tools to easily search and open a new tab.

When not using system decorations, it's really confusing. In fact, it defeats the ideas behind the "new feature" because the tab "bar" never really disappears. It's transformed into a useless bar which contains nothing more than the window buttons (minimize, maximize and close). So in practice, when a single tab is present, the tab disappears and so does the tools related to tabs: no more "new tab" button, no more dropping links or text on the bar to open as new tab. It's really confusing because the bar is still there. It's just empty and useless.

Revision history for this message
Rudolfs Caune (djbacons) wrote :

I have same problem. Really annoying.
Version 23.0.1271.97 Ubuntu 12.10 (23.0.1271.97-0ubuntu0.12.10.1)

Revision history for this message
Sabarudin Widjaja (swidj) wrote :

Same problem here, and being frustrated that nothing can be done about it. I'm using Version 23.0.1271.97 Ubuntu 12.10 (23.0.1271.97-0ubuntu0.12.10.1) , just few hours ago got updated. I thought something wrong with my settings, but not. and much worst not all settings can be changed from wrench/preferences.

Revision history for this message
inneas (inneas) wrote :

Same problem here, really annoying. Any workaround?

I think this problem has come with an update because I'm using Ubuntu 12.10 since month and I recognized this problem only a few days ago (and I'm sure I would have recognized it if it had been there before.)

Revision history for this message
Saesneg (david-deans) wrote :

I am having the same problem here. I am using Chromium 23.0.1271.97-0ubuntu0.12.10.1, with Lubuntu 12.10.

Workaround at the moment seems to be using two tabs at once, which you will have to open with either ctrl-t or a ctril-left click, or through a menu.

It's otherwise properly broken.

Revision history for this message
Pavel Zhukov (cray0000) wrote :

Confirming.
23.0.1271.97-0ubuntu0.12.10.1

Revision history for this message
Stuart Stein (mr-stuart) wrote :

Confirmed on latest Chrome on Ubuntu with LXDE

This is incredibly annoying. Are we sure it's a bug though and not just new expected behaviour ?

Revision history for this message
Sébastien Maccagnoni-Munch (tiramiseb) wrote :

> Are we sure it's a bug though and not just new expected behaviour ?

If it was an expected behaviour, I think Chrome on Windows and Chromium on Ubuntu 12.04, with the same version number, would have it too.

It seems it only affects Ubuntu 12.10.

Revision history for this message
Zack Hixon (zack-hixon) wrote :

I didn't have this problem with the prior version of Chromium, with the same situation as David Deans. I also can't change certain settings in the settings menu, for instance what pages open when I open Chromium. This doesn't happen with the latest Chrome on Windows XP, so it's definitely not intended.

Revision history for this message
Kim Laroux (withered-angel) wrote :

I just verified, and I too cannot change some settings.

I can set the page that load at startup, this works as intended.

I cannot change the page that loads in new tabs. When I set it, it shows the correct URL in the settings, but opening a new tab does not load the URL. Restarting chromium makes the URL disappears from the settings.

I cannot change theme. Going to the chrome store and clicking "Choose Theme" downloads the theme, but does not apply it. The button gets stuck showing "Checking..."

Could all this be related? All of these features worked perfectly before the upgrade to version 23.

Revision history for this message
letmedeletemyaaccount (letmedeletemyaaccount) wrote :

Linux Mint 14 - Nadia 64bit, Xfce 4.10
Chromium 23.0.1271.97

Same problem here, quite annoying.

Revision history for this message
Tobias Bieniek (tobias-bieniek) wrote :

confirmed on Ubuntu 12.10 32bit with Chromium 23.0.1271.97

inneas (inneas)
information type: Public → Public Security
information type: Public Security → Public
Revision history for this message
Daryl Hurst (daryl-hurst) wrote :

Confirmed on Linux Mint Nadia 64 bit, Cinnamon.
Chromium 23.0.1271.97.

Thought I was going mad and had inadvertently changed some setting.

Fix it please this cannot possibly be an intended feature. Also where are updates documented???

Revision history for this message
Gustavo Barizon (barizon) wrote :

Confirmed on Chromium version 23.0.1271.97 Ubuntu 12.10 (23.0.1271.97-0ubuntu0.12.10.1) 64-bit

Revision history for this message
Chip Bennett (chipbennett) wrote :

I'll add to the chorus. Confirmed on:
Version 23.0.1271.97 Ubuntu 12.10 (23.0.1271.97-0ubuntu0.12.10.1)

I just updated today from Kubuntu Precise to Kubuntu Quantal. This bug did NOT appear in the version of Chromium in Precise:
chromium-browser (23.0.1271.97-0ubuntu0.12.04.1)

So, this is apparently an Ubuntu Quantal-specific issue - and an annoying one, at that.

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

I believe this is caused by Ubuntu's 4-chromeless-window-launch-option.patch (see bug 1028538). Chad, can you please take a look at this?

Changed in chromium-browser (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
assignee: nobody → Chad Miller (cmiller)
Revision history for this message
Dmitry Shachnev (mitya57) wrote :
Changed in unity-chromium-extension:
status: New → Fix Committed
Revision history for this message
dennygoot@gmail.com (dennygoot) wrote :

I have this bug on Xubuntu 12.10 64 bit edition as well.

Revision history for this message
CaptainMark (imark-skinner) wrote :

Confirmed on Mint 14 64bit Cinnamon Ed.

Has anyone checked the same Chromium version on a non-Ubuntu derivative, I doubt this is an upstream bug

Revision history for this message
Sébastien Maccagnoni-Munch (tiramiseb) wrote :

CaptainMark : please look 2 messages above yours : the bug has been spotted (in ubuntu patches) and corrected.

We just need to wait for the next upgrade :)

Revision history for this message
Domain Administrator (493poc-ycm05-d18eca) wrote :

Thank you for sorting this. Any ETA on when the fix will be in the repositories?

Was the issue a modification for the Unity GUI that had 'leaked' into all the alternate GUIs? If so can we be sure this a one-off or a systemic issue?

Revision history for this message
Sébastien Maccagnoni-Munch (tiramiseb) wrote :

> Any ETA on when the fix will be in the repositories?

As a "simple user", I am also very interested in this information :D

> Was the issue a modification for the Unity GUI that had 'leaked' into all the alternate GUIs?

Yes, as long as these "alternate GUIs" are using Ubuntu 12.10 packages (Kubuntu 12.10, Xubuntu 12.10, etc).

> can we be sure this a one-off or a systemic issue?

The bug seems pretty clear and simple :

They wanted to hide the tabs bar in "chromeless mode" when there is only one tab, but in the code they added a test which only checks if there is only one tab, not caring about the window "mode". The new patch adds a test to check if the window is in "chromeless mode", so the bar will not be hidden for classic chromium windows.

So, I'm confident it is a one-off issue.

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

For those who want to test the fix, updated packages are available in Chad's experimental PPA (ppa:cmiller/chromium-browser-stable-daily).

Revision history for this message
Kim Laroux (withered-angel) wrote :

I can confirm that this bug is fixed in 24.0.1312.56-0ubuntu0.12.10.1~cm0quantal1

But the chrome://settings/ page is blank. It seems broken. So I can't reset my startup settings to a single tab to see if it works from a fresh start.

Annoying.

Revision history for this message
Craig Crawford (craigcrawford1988) wrote :

This bug is fixed in 24.0.1312.56-0ubuntu0.12.10.1~cm0quantal1, however as above, the settings page is blank.

Revision history for this message
Paweł Kowalik (pkowalik) wrote :

Confirming. Bug fixed in 24.0.1312.56-0ubuntu0.12.10.1~cm0quantal1 and now the settings tab is completely clear. Every time the settings tabs is opened, the console logs:

Uncaught TypeError: Cannot set property 'onchange' of null", source: chrome://settings-frame/options_bundle.js (5788)

Clearing cache and all settings which includes profile wiping does not solve the problem.

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Filed the settings-not-working bug as bug 1106876, hope it will be fixed in the final Chromium 24 package.

David King (amigadave)
Changed in unity-chromium-extension:
importance: Undecided → High
assignee: nobody → David King (amigadave)
assignee: David King (amigadave) → nobody
assignee: nobody → Alexandre Abreu (abreu-alexandre)
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.1 KiB)

This bug was fixed in the package chromium-browser - 24.0.1312.56-0ubuntu0.12.10.3

---------------
chromium-browser (24.0.1312.56-0ubuntu0.12.10.3) quantal-security; urgency=low

  * Add comment-markers to debian/patches/series file to make patch import
    easier.
  * debian/chromium-browser.install
    - Install remoting locales
  * debian/patches/gyp-config-root.patch
    - Added. Avoids compilation bug on (at least) ARM.
  * debian/patches/arm-neon.patch
    - Added function to determine NEON functionality in ARM at runtime for
      WebRt library in WebKit.
  * Disable lintian warnings about outdated autoconf files in source tree.
  * New upstream version 24.0.1312.56: (LP: #1099075)
    - CVE-2013-0839: Use-after-free in canvas font handling.
    - CVE-2013-0840: Missing URL validation when opening new windows.
    - CVE-2013-0841: Unchecked array index in content blocking.
    - CVE-2013-0842: Problems with NULL characters embedded in paths.
  * New upstream version 24.0.1312.52:
    - CVE-2012-5145: Use-after-free in SVG layout. Credit to Atte Kettunen of
      OUSPG.
    - CVE-2012-5146: Same origin policy bypass with malformed URL. Credit to
      Erling A Ellingsen and Subodh Iyengar, both of Facebook.
    - CVE-2012-5147: Use-after-free in DOM handling. Credit to José A. Vázquez.
    - CVE-2012-5148: Missing filename sanitization in hyphenation support.
      Credit to Google Chrome Security Team (Justin Schuh).
    - CVE-2012-5149: Integer overflow in audio IPC handling. Credit to Google
      Chrome Security Team (Chris Evans).
    - CVE-2012-5150: Use-after-free when seeking video. Credit to Google Chrome
      Security Team (Inferno).
    - CVE-2012-5151: Integer overflow in PDF JavaScript. Credit to Mateusz
      Jurczyk, with contribution from Gynvael Coldwind, both of Google Security
      Team.
    - CVE-2012-5152: Out-of-bounds read when seeking video. Credit to Google
      Chrome Security Team (Inferno).
    - CVE-2012-5153: Out-of-bounds stack access in v8. Credit to Andreas
      Rossberg of the Chromium development community.
    - CVE-2012-5156: Use-after-free in PDF fields. Credit to Mateusz Jurczyk,
      with contribution from Gynvael Coldwind, both of Google Security Team.
    - CVE-2012-5157: Out-of-bounds reads in PDF image handling. Credit to
      Mateusz Jurczyk, with contribution from Gynvael Coldwind, both of Google
      Security Team.
    - CVE-2013-0828: Bad cast in PDF root handling. Credit to Mateusz Jurczyk,
      with contribution from Gynvael Coldwind, both of Google Security Team.
    - CVE-2013-0829: Corruption of database metadata leading to incorrect file
      access. Credit to Google Chrome Security Team (Jüri Aedla).
    - CVE-2013-0830: Missing NUL termination in IPC. Credit to Google Chrome
      Security Team (Justin Schuh).
    - CVE-2013-0831: Possible path traversal from extension process. Credit to
      Google Chrome Security Team (Tom Sepez).
    - CVE-2013-0832: Use-after-free with printing. Credit to Google Chrome
      Security Team (Cris Neckar).
    - CVE-2013-0833: Out-of-bounds read with printing. Credit to Google Chrome
      Security Team (Cris Neckar).
    - CVE-2013-08...

Read more...

Changed in chromium-browser (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Kim Laroux (withered-angel) wrote :

I'm now running 24.0.1312.56-0ubuntu0.12.10.3 which has the "fix".

But I just noticed that the test that was added did not take into account pop-up windows. This means that the tab bar is now forced to be displayed in pop-up windows. This messes up the title bar. You now have an empty tab displayed behind the title text.

Attached is a screenshot of the problem. You can see that the title bar is not as it's supposed to be for a pop-up window.

Revision history for this message
Alexandre Abreu (abreu-alexandre) wrote :

Kim Laroux (withered-angel):

thanks for your comment, there is indeed a glitch with popup windows. I pushed a fix (pending for merge review) that will put things back to normal asap,

Revision history for this message
Domain Administrator (493poc-ycm05-d18eca) wrote :

I am still ducking out of the nagging update notices in Kubuntu 12.10.

What are the advantages of not running the stock Chromium package? Do they outweigh the increased risk of bugs and bug fix bugs?

Not being critical, I'm ever gratful to the fixers for their devotion to duty. It is just that this takes their creative time away ...

Changed in unity-chromium-extension:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.