Ubuntu
chromium-browser package

recent saucy update lost its chrome

Bug #1223251 reported by John Lenton on 2013-09-10

30

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	chromium-browser (Ubuntu)	Fix Released	High	Chad Miller

Bug Description

The latest chromium update is broken.

It has no chrome: no location bar, no bookmarks, you can't open new tabs by hand. It starts multiple copies of itself (and fails to grab the profile lock, and fails to realise it, and only complains about not being able to log in to the account sync thing) and you end up with multiple chromium icons in the launcher. Focus is all over the place.

It is now slightly less usable than firefox.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: chromium-browser 29.0.1547.65-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: Linux 3.11.0-4-generic i686
ApportVersion: 2.12.1-0ubuntu3
Architecture: i386
Date: Tue Sep 10 10:00:29 2013
Desktop-Session:
DESKTOP_SESSION = ubuntu
XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
MOZ_PLUGIN_PATH = None
LD_LIBRARY_PATH = None
InstallationDate: Installed on 2010-10-09 (1066 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1)
MarkForUpload: True
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to saucy on 2013-06-11 (90 days ago)
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser --password-store=gnome %U\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser --password-store=gnome %U\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b'metacity\n'/apps/metacity/general/compositing_manager = b'true\n'/desktop/gnome/interface/icon_theme = b'ubuntu-mono-dark\n'/desktop/gnome/interface/gtk_theme = b'Ambiance\n'

Tags:

Revision history for this message

John Lenton (chipaca) wrote on 2013-09-10:

#1

ChromiumPrefs.txt Edit (55.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (6.5 KiB, text/plain; charset="utf-8")
DetectedPlugins.txt Edit (1.8 KiB, text/plain; charset="utf-8")
DiskUsage.txt Edit (1.1 KiB, text/plain; charset="utf-8")
InstalledPlugins.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (106 bytes, text/plain; charset="utf-8")
RelatedPackageVersions.txt Edit (807 bytes, text/plain; charset="utf-8")
RelatedPackagesPolicy.txt Edit (3.6 KiB, text/plain; charset="utf-8")

Revision history for this message

John Lenton (chipaca) wrote on 2013-09-10:

#2

Despite Ctrl+T not opening a tab, Ctrl+N opens a new window, and this new window does have all the chrome on it. This new window is also picked up by the launcher as being chromium, so if I then close the other chromeless window(s) I have only one chromium icon in the launcher. I can then go into settings and sign in and all is well.

If I close it, I still get the chromeless thing back.

Sebastien Bacher (seb128) on 2013-09-10

summary:	- latest chromium update is a bucket of unquantifiable fail + recent saucy update lost its chrome
Changed in chromium-browser (Ubuntu):
assignee:	nobody → Chad Miller (cmiller)
importance:	Undecided → High
status:	New → Confirmed

Revision history for this message

Chad Miller (cmiller) wrote on 2013-09-10:

#3

John, I can't reproduce this. Does it happen when run from a terminal? How about with parameter "--temp-profile"?

Revision history for this message

Chad Miller (cmiller) wrote on 2013-09-10:

#4

John, and, by "chrome", you mean the tab bar, and back/forward/reload/location bar? Not the window manager decoration.

Revision history for this message

Chad Miller (cmiller) wrote on 2013-09-10:

#5

I managed to reproduce once by closing every tab one by one, until the window closed, then launching anew.

Changed in chromium-browser (Ubuntu):
status:	Confirmed → In Progress

Revision history for this message

John Lenton (chipaca) wrote on 2013-09-10: Re: [Bug 1223251] Re: recent saucy update lost its chrome

#6

It happens when running from a terminal, yes. Didn't try with
--temp-profile, but did try with starting in a guest session (it looks
the same). By “chrome” I mean the tab bar, the
back/forward/reload/location/preferences bar, the bookmarks bar.

Glad you could reproduce it :-)

On Tue, Sep 10, 2013 at 2:37 PM, Chad Miller <email address hidden> wrote:
> John, I can't reproduce this. Does it happen when run from a terminal?
> How about with parameter "--temp-profile"?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1223251
>
> Title:
> recent saucy update lost its chrome
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1223251/+subscriptions

Revision history for this message

Loïc Minier (lool) wrote on 2013-09-11:

#7

Doesn't happen with --temp-profile.

Revision history for this message

Stuart Langridge (sil) wrote on 2013-09-11:

#8

This is happening to me too: opening with a temporary profile (from the Launcher icon) does not exhibit the problem, but opening an incognito window does. Sometimes my main Chromium profile also shows the problem; if I quit the browser and re-open it the problem fixes itself for that session.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-09-11:

#9

This bug was fixed in the package chromium-browser - 29.0.1547.65-0ubuntu2

---------------
chromium-browser (29.0.1547.65-0ubuntu2) saucy; urgency=low

  * debian/control: Make chromium-browser-l10n Replaces chromium-browser so
    that new translations that were added in v28 packaging are now in the
    correct -l10n package. (LP: #1222488)
  * debian/rules: Remove unused duplicate-exclusion patterns. Again.
  * debian/control: Make codecs packages no longer Depend on chromium-browser,
    so that "extras" metapackages can pull them in without enormous browser.
    (LP: #1208518)
  * debian/tests/control: Don't use needs-build flag as we don't need it
    presently. Also, disable autopkgtest "smoketest" failure until its
    misbehavior on some environments can be diagnosed from log files.
  * debian/patches/4-chromeless-window-launch-option.patch: Add missing
    construction initializer. (LP: #1223251)
-- Chad MILLER <email address hidden> Tue, 10 Sep 2013 14:51:03 -0400

Changed in chromium-browser (Ubuntu):
status:	In Progress → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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