New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 752384 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: May 2018
Cc:
█ divya.pa...@techmahindra.com
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

File browser opens to whitescreen

Reported by ad...@dcousens.com, Aug 4 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.96 Chrome/58.0.3029.96 Safari/537.36

Steps to reproduce the problem:
1. Open Chromium
2. Ctrl-O
3. White screen

What is the expected behavior?
A GTK file browser

What went wrong?
The file browser fails to open correctly.

Did this work before? Yes 58.

Chrome version: 60.0.3112.90  Channel: n/a
OS Version: 4.12.3-1-ARCH
Flash Version: 

stdout
```
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
```

While temporarily using Firefox, which I know uses the GTK3 file browser too,  this is not an issue there.
The above warning is now displayed.

Comment 1 by ad...@dcousens.com, Aug 4 2017 

Related to my Xresources DPI settings.

Changing `Xft.autohint: 1` resolved my issue.
Does not happen in FF.

Comment 2 by brajkumar@chromium.org, Aug 7 2017

Cc: brajkumar@chromium.org
Labels: Needs-Triage-M60 Needs-Feedback
Reporter@ As per comment #1 could you please confirm is this issue got fixed?

Comment 3 by ad...@dcousens.com, Sep 14 2017 

Re-introduced with version 61.0.3163.79.

The Xresources change above does NOT resolve the issue now.
Project Member

Comment 4 by sheriffbot@chromium.org, Sep 14 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by ad...@dcousens.com, Sep 14 2017 

If I reduce my desktop DPI down to 72 (from 180), but then use `--force-device-scale-factor=2`,  it can be seen the FileBrowser does not respect the scale factor,  and remains at the other DPI.

https://i.imgur.com/aughWqG.png
dpifail.png
100 KB View Download

Comment 6 by ad...@dcousens.com, Sep 30 2017 

My steps to resolve the issue at this time is to open Chromium in a lower DPI X environment,  open the File Browser,  then return back to my 180 DPI environment,  and the File Browser works as expected.
If `~/.config` is somehow reset,  then you need to repeat the process.

Comment 7 by divya.pa...@techmahindra.com, Nov 6 2017

Cc: divya.pa...@techmahindra.com
Labels: Needs-Feedback Triaged-ET
Unable to reproduce this issue on chromium 61.0.3163.100 using Ubuntu 14.04 with steps mentioned below:
1. Open Chromium
2. Press Ctrl-O
3. File browser opens
@reporter: Can you please upgrade the chromium to 61.0.3163.100 and provide your observation

Thanks!

Comment 8 by ad...@dcousens.com, Nov 7 2017 

Cannot reproduce.
Project Member

Comment 9 by sheriffbot@chromium.org, Nov 7 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "divya.padigela@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 10 by sindhu.chelamcherla@chromium.org, May 29 2018

Status: WontFix (was: Unconfirmed)
As per comment#8 closing this issue as it is no longer reproducible.

Thanks!
►

Sign in to add a comment