chromium scales huge when run from an lxc container

Bug #1326162 reported by Nick Moffitt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I followed stgraber's excellent tutorials in https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/ and got a container that has X11 and DRI and pulse access. It works really well!

But the odd thing is that chromium run from inside the container turns out enormous on my 1920x1080 display in a way that chromia run outside the container do not. I checked xrandr and xdpyinfo from both sides and nothing changed.

I asked stgraber about this, and he doesn't see it with the proprietary chrome builds. http://ubuntuforums.org/showthread.php?t=2225788&s=dd2819f676875c608dbac135d66ce9c9&p=13032314 shows someone seeing it within KDE. So it seems as though Unity/gnome set some sort of aura DPI environment up that I'm not getting yet in my LXC container.

I'd be happy with a workaround at the moment, but really I just hope I don't need to install dbus inside my lxc :)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.116-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jun 3 23:31:32 2014
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/
DetectedPlugins:

Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2014-05-29 (5 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
chromium-default: CHROMIUM_FLAGS=""
gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]

Revision history for this message
Nick Moffitt (nick-moffitt) wrote :
Revision history for this message
Paul White (paulw2u) wrote :

Is this still an issue now that Chromium 71.0 is the currently supported version?

Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]

Changed in chromium-browser (Ubuntu):
status: Incomplete → Expired
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.