Crash when opening proxy settings in new Material Design settings page
Reported by
blufyr3...@gmail.com,
Oct 1 2016
|
||||
Issue descriptionChrome Version: 53.0.2785.143 (64-bit) Is this the most recent version: OS + version: Ubuntu GNOME 16.04.1 + latest updates from 9/30/16 5:20pm CPU architecture (32-bit / 64-bit): Intel® Core™2 Quad CPU Q9505 @ 2.83GHz × 4 Graphics hardware: Intel® Q45/Q43 RAM Installed: SAMSUNG 2GB 2Rx8 PC3 - (M378B5673FH0-CH9) Approximate Available: 1.7 GB Window manager: X11 URLs (if relevant): chrome://settings Behavior in Windows Chrome (if you have access to it): What steps will reproduce the problem? (1) Enable material design settings in chrome://flags#enable-md-settings (2) Scroll down and click 'advanced' (3) Scroll down and click 'CHANGE PROXY SETTINGS' What is the expected result? The gnome network manager opens. What happens instead? Chrome freezes (not the whole system) and crashes the gnome shell UI, thereafter the interface (window navbars, dock, status bar, etc.) reloads and the network control panel opens. Chrome does not report an incorrect shutdown has occurred (in bubble or banner). ----- Gnome Shell Crash Dump ----- ExecutablePath: /usr/bin/gnome-shell Package: gnome-shell 3.18.5-0ubuntu0.1 Title: gnome-shell crashed with signal 5 in _XReply() ApportVersion: 2.21.1-0ubuntu2.1 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 16.04 InstallationMedia: Ubuntu-GNOME 16.04.1 LTS 'Xenial Xerus' - Release amd64 (20160720) ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
,
Oct 13 2016
,
Oct 14 2016
blufyr3530@: do these commands give you the same results as clicking the "CHANGE PROXY SETTINGS" button in chrome://md-settings? gnome-network-properties gnome-control-center network fwiw: I'm using xmonad on 14.04 so I just get sent to chrome://linux-proxy-config I'll try with Gnome3 soon.
,
Oct 14 2016
works for me with "Gnome flashback (compiz)"
,
Oct 14 2016
,
Oct 14 2016
Running the command 'gnome-control-center network' runs without a crash for me. Although, the command outputs the following before opening the network control pannel: ** (gnome-control-center:10522): WARNING **: Ignoring launcher gufw (missing desktop file) ** (gnome-control-center:10522): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) ** (gnome-control-center:10522): WARNING **: Ignoring launcher language-selector (missing desktop file) ** (gnome-control-center:10522): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) (gnome-control-center:10522): Gtk-WARNING **: GtkGrid 0x1cb5170 reported min size 250 and natural size 249 in get_preferred_width(); natural size must be >= min size (gnome-control-center:10522): Gtk-WARNING **: GtkGrid 0x1cb5170 reported min size 250 and natural size 249 in get_preferred_width(); natural size must be >= min size (gnome-control-center:10522): Gtk-WARNING **: GtkGrid 0x1cb5170 reported min size 250 and natural size 249 in get_preferred_width_for_height(); natural size must be >= min size The command 'gnome-network-properties' doesn't exist. I am on using gtk 3.
,
Oct 14 2016
Clicking 'CHANGE PROXY SETTINGS' on chrome version 54.0.2840.59 works for me now. It seems, this is no longer an issue.
,
Oct 14 2016
yeah, it was probably something funky about how you were running chrome. clicking that button (more or less) just does the same thing as the "gnome-control-center network" command. thanks for the report! |
||||
►
Sign in to add a comment |
||||
Comment 1 by kavvaru@chromium.org
, Oct 3 2016Labels: Proj-MaterialDesign-WebUI