Public bug reported: 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] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "chromium from inside lxc on the left, outside on the right, using a temporary profile" https://bugs.launchpad.net/bugs/1326162/+attachment/4125045/+files/eliminations-wallboard-galvanizing-Rodriguez.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1326162 Title: chromium scales huge when run from an lxc container Status in “chromium-browser” package in Ubuntu: New 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] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1326162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
