Using fglrx, chromium tabs not displaying titles

Bug #1222718 reported by Paweł Szafer
266
This bug affects 53 people
Affects Status Importance Assigned to Milestone
Chromium Browser
Unknown
Unknown
fglrx
New
Undecided
Unassigned
chromium-browser (Ubuntu)
Fix Released
Undecided
Chad Miller
fglrx-installer (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hello,

My problem is that Chrome/Chromium (have both installed) are not displaying page titles rendering many pages.
Actually, because of bug of keybindings in Gnome 3.9 I can't create screenshot, but with most pages I have favicon displayed and not any text like page title.

It doesn't matter if GPU rendering is enabled or disabled.

Revision history for this message
Saikrishna Arcot (saiarcot895) wrote :

What version (and PPA, if applicable) do you have?

Revision history for this message
Paweł Szafer (pszafer) wrote :

29.0.1547.65 Ubuntu 13.10 (29.0.1547.65-0ubuntu1)

I really don't know how to check PPA, but I think it is Saucy standard PPA, since I haven't activated any custom PPA related to chromium-browser, after dist-upgrade to Saucy.

Chrome browser version
29.0.1547.32 beta

Revision history for this message
Saikrishna Arcot (saiarcot895) wrote :

I failed to see that this occurs on both Chrome and Chromium. Based on this, it is either a Chromium problem or something is wrong on your computer.

Can you try uninstalling one of them (perhaps Chrome, since it's older) and checking to see if the tab titles display correctly?

Revision history for this message
Paweł Szafer (pszafer) wrote :

Hello
I've decided to reinstall Ubuntu, to Ubuntu Gnome 13.10 beta.
After that problem with tabs titles has gone.

But apparently after first start of Chromium after boot, there are no tabs menu, just gtk menu with close, minimize, maximize.
I will report it in other bug, so different problems won't be mixed, ok?

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
Revision history for this message
Paul Sarraffe (psarraf) wrote :

This appears related to https://code.google.com/p/chromium/issues/detail?id=123104 which was first reported in April 2012. I did not see this problem with Xubuntu 13.04 64-bit, but I do see it in Xubuntu 13.10 64-bit. Perhaps this is the reason that Firefox is still the default web browser for Ubuntu 13.10.

Revision history for this message
Otus (jan-varho) wrote :

This started for me when I upgraded from raring to saucy. Tabs have favicons but no titles.

Revision history for this message
RThinker (yegor-rog) wrote :

Same for me. Most of tabs in chromium have no titles, just favicons.

Revision history for this message
Valera Lewontyev (feedbee) wrote :

The same problem in Google Chrome after update to Ubuntu 13.10

Revision history for this message
Krystian Paszek (ravenravenpl) wrote :

I also experience this bug. Xubuntu 13.10 64-bit with latest google-chrome-stable (30.0.1599.101).

Revision history for this message
Otus (jan-varho) wrote :

According to the linked chromium bug, this is related to fglrx, so adding it.

Revision history for this message
seattle vic (victorino) wrote :

Same here; 13.10, 64 bit, chromium stable. However, I have the exact same configuration loaded on two laptops. The 5 year old laptop (ASUS) does not show this problem, but the new ASUS with the GTX 770 has this issue.

Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
assignee: nobody → Chad Miller (cmiller)
Revision history for this message
Chad Miller (cmiller) wrote :

Let's make sure we have this nailed down to the correct place.

IF you see this problem, and if you open a terminal and run
ubuntu-drivers list
and do NOT see "fglrx" in the list, please add a comment with what you DO see AND ATTACH the file /var/log/Xorg.0.log .

I'll tag this as NeedInfo for Ubuntu chromium-browser, and if we see a consensus, I'll move it to Ubuntu fglrx or reopen as chromium-browser . Checking back in 7 days.

Changed in chromium-browser (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
belgianguy (wietse-jorissen) wrote :

Using fglrx here. 31.0.1650.26 beta on 13.10, 64 bit. It doesn't happen all the time, but still often.

Revision history for this message
Leonid Kuzmin (zuker) wrote :

Using fglrx on laptop with hybrid graphics, bug happens only if discrete GPU is active.

Revision history for this message
Falko Schmidt (kaethorn) wrote :

Running VirtualBox 4.2.18 with an Ubuntu 13.10 guest.

# ubuntu-drivers list
virtualbox-guest-dkms

Chad Miller (cmiller)
Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto Milone (albertomilone) wrote :

@Jammy: any ideas about this problem?

Chad Miller (cmiller)
summary: - Tabs not displaying titles
+ Using fglrx, chromium tabs not displaying titles
Revision history for this message
James Tunnicliffe (dooferlad) wrote :

Note the Chromium bug (https://code.google.com/p/chromium/issues/detail?id=123104) has comments from non-ATI users as well - comments #18 and #50 both are for Intel graphics and comment #56 is for VIA Chrome9. Comment #12 here is from an nVidia user. This is not isolated to fglrx.

Given the comments about different driver versions (normally closed vs open) it seems possible that Chrome's 3D acceleration whitelist is worth investigating. For people *not* suffering, chrome://flags/#ignore-gpu-blacklist may be worth playing with to see if they can recreate the issue with open drivers.

I don't have 13.10 installed at the moment or I would give this a go :-|

Revision history for this message
pdknsk (pdknsk) wrote :

Forcing acceleration makes no difference with open source drivers.

Revision history for this message
Andy (amo999) wrote :

Happening to me too, Google Chrome. Version 30.0.1599.114
I'm running Ubuntu 13.10, 64-bit.

Tabs keep losing their content (titles), but they can come back too.

$ ubuntu-drivers list
fglrx-updates
fglrx

Running on :-
AMD E-450 APU with Radeon(tm) HD Graphics × 2
VESA: WRESTLER

If anyone needs any further info... shout up.

Revision history for this message
Johan (johanhp) wrote :

Same here after upgrade from 13.04 to 13.10.

Chromium version 29.0.1547.65 Ubuntu 13.10 (29.0.1547.65-0ubuntu2)

$ ubuntu-drivers list
bcmwl-kernel-source
fglrx-updates
fglrx

Revision history for this message
Andy (amo999) wrote :

Returning back to the open-source xserver-xorg-video-ati driver removes the problem issue for me.
Screenshot attached of drivers page (if of any use!)

Revision history for this message
Paweł Szafer (pszafer) wrote :

Could this problem with Eclipse https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1239607 also be related to fglrx bug?

Revision history for this message
Xavier Martin (zeflasher+launchpad) wrote :

I also have this occuring

ubuntu-drivers list gives me
nvidia-325
nvidia-331
nvidia-319-updates

Kubuntu x64 13.10
Google Chrome Version 30.0.1599.114

Revision history for this message
Xavier Martin (zeflasher+launchpad) wrote :

And the log file.

Revision history for this message
Jeff Balderson (jbalders) wrote :

This issue isn't isolated to fglrx. See #16 and #18.

# ubuntu-drivers list
virtualbox-guest-dkms

Revision history for this message
Andy Addington (w-a-addington) wrote :

andygmorris's solution worked for me as well, using the open-source xserver-xorg-video-ati

ubuntu-drivers list
fglrx-updates
fglrx

Google Chrome 30.0.1599.114 worked fine using any driver listed above

Chromium 29.0.1547.65 Ubuntu 13.10 would not always display titles in the Tabs and the WebSocket connection I use on a local server seemed to crash.

Revision history for this message
Chad Miller (cmiller) wrote :

It's not unique to fglrx, but it doesn't happen on some video drivers and does on a few. I'm setting the bug-reports on drivers to "New" until we learn more about what upstream is doing and can confirm some hypotheses. I'm sorry for the noise.

Changed in fglrx-installer (Ubuntu):
status: Confirmed → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in fglrx-installer (Ubuntu):
status: New → Confirmed
Revision history for this message
Matt Giuca (mgiuca) wrote :

Update from Chromium's side: I have a workaround for this issue (tracking on this bug http://crbug.com/123104). I am hoping we can get the fix out with Chromium 31, but I can't make any promises at this stage (since we are very late in the Chromium 31 release process). But it will definitely be fixed for Chromium 32.

Note that I have not been able to address the root issue. I'm assuming there's a new bug in Cairo but I don't know what is causing this -- it is something to do with the subtle fade effect on the right side of the tab text. My quick-and-dirty workaround for Chromium 31 simply disables the fade effect, and my full fix for Chromium 32 switches to a different text rendering engine for tab titles.

Revision history for this message
Matt Giuca (mgiuca) wrote :

I am happy to report that the workaround has been merged into Chromium 31. Tabs should display titles again from Chromium 31 onwards -- please report on http://crbug.com/123104 if there are still problems after 31.

As a side effect, users upgrading to Chromium 31 will have a missing fade effect on the right side of the tab (http://crbug.com/315915), but this should be fixed when Chromium 32 comes out.

Changed in chromium-browser (Ubuntu):
status: Incomplete → Fix Committed
Revision history for this message
Chad Miller (cmiller) wrote :

Setting status Ubuntu packaging of chromium-browser to In Progress, as it's not landed in Ubuntu source yet.

Changed in fglrx-installer (Ubuntu):
status: Confirmed → Invalid
Changed in chromium-browser (Ubuntu):
status: Fix Committed → In Progress
Revision history for this message
Andy (amo999) wrote :

Chad, Matt, and anyone else that helped fix this, thank you.

Look forward to seeing Chromium 31 in Ubuntu 13.10 soon ;-)
And then, hopefully, the same patch will follow some time into Google Chrome?

Revision history for this message
Matt Giuca (mgiuca) wrote :

@Chad: Ah, sorry I jumped the gun.

@Andy: This will be in Google Chrome 31 as well, which will be released very soon.

Revision history for this message
Falko Schmidt (kaethorn) wrote :

It's resolved for me with Chrome version 31.0.1650.48 in VirtualBox.

Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
status: In Progress → Fix Committed
Olivier Tilloy (osomon)
Changed in chromium-browser (Ubuntu):
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.