Chromium should watch the escale setting "Scale for menu and title bars" in Display Settings at runtime

Bug #1312112 reported by Ara Pulido on 2014-04-24
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Medium
Unassigned

Bug Description

Chromium scales correctly on start up based on the setting applied to "Scale for menu and title bars" in Display Settings.

However, ideally, Chromium should watch this setting also at runtime and scale if it gets modified, as the GTK applications currently do.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 34.0.1847.116-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 24 12:42:05 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:

DiskUsage:
 b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sda2 ext4 286G 13G 258G 5% /\nnone tmpfs 4,0K 0 4,0K 0% /sys/fs/cgroup\nudev devtmpfs 3,9G 4,0K 3,9G 1% /dev\ntmpfs tmpfs 785M 1,1M 784M 1% /run\nnone tmpfs 5,0M 0 5,0M 0% /run/lock\nnone tmpfs 3,9G 292K 3,9G 1% /run/shm\nnone tmpfs 100M 80K 100M 1% /run/user\n/dev/sda1 vfat 487M 3,4M 483M 1% /boot/efi\n'

 Inodes:
 b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda2 19M 259K 18M 2% /\nnone 982K 2 982K 1% /sys/fs/cgroup\nudev 979K 538 978K 1% /dev\ntmpfs 982K 538 981K 1% /run\nnone 982K 3 982K 1% /run/lock\nnone 982K 9 982K 1% /run/shm\nnone 982K 36 982K 1% /run/user\n/dev/sda1 0 0 0 - /boot/efi\n'
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2014-03-26 (29 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to trusty on 2014-04-07 (16 days ago)
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]

Ara Pulido (ara) wrote :
Changed in chromium-browser (Ubuntu):
importance: Undecided → High
importance: High → Medium
Launchpad Janitor (janitor) wrote :

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

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers