Mailing List Archive: Request for verification - Chrome new window moved to other screens is black

Request for verification - Chrome new window moved to other screens is black

Dec 26, 2014, 5:53 AM

Post #1 of 3 (1301 views)

Hi quiet list,
This is a request for anyone using Chrome, any version in portage -
I've tried stable, beta and unstable - to see if you see this problem.
It's easy to reproduce on my system.

The system I've got:

1) Gentoo 64-bit, mostly stable
2) Two NVidia 8400 GS VGAs driving 3 monitors using nvidia-drivers
3) KDE with 6 desktops + 3 screens/desktop

First, demonstrate no basic problems: open Chrome and move it around
to different screens on any desktop. Chrome should work fine as it
does here.

Second, demonstrate the problem. In the Chrome menu in the upper right
- 3 horizontal lines - choose New Window. Chrome pops up and looks
good. Move it to another screen and see if it turns black. It does on
my system.

The Chrome folks are looking for some verification in a bug report
I made here:

https://code.google.com/p/chromium/issues/detail?id=443189

If you see the problem maybe you can add some info to the bug
report. If you do not but have some ideas about how I might
reconfigure something like X to fix this I'd appreciate hearing your
ideas. I'm attaching my xorg.conf file if someone wants to review that
for possible fix-ups I might try.

Thanks,
Mark

Re: Request for verification - Chrome new window moved to other screens is black [ In reply to ]

frank.peters at comcast

Dec 26, 2014, 8:42 AM

Post #2 of 3 (1256 views)

Permalink

On Fri, 26 Dec 2014 05:53:14 -0800
Mark Knecht <markknecht@gmail.com> wrote:

>
> This is a request for anyone using Chrome, any version in portage -
>

I can't help with verification as I don't use Chrome. Occasionally
I'll use Iron browser, which is a specially configured version of Chrome,
but my system has no multiple monitors and does not use KDE so comparisons
would probably be useless.

My only advice would be to try and get some logging/debugging output from
somewhere.

You may want to start Chrome from a virtual terminal (rather than clicking
on an icon) in X and then examine the output that will show up in the
terminal window. Debugging output either from Chrome itself or from one of
its supporting libraries will usually be printed.

Are there command-line options to Chrome that would provide debugging
output? Maybe other command-line options would be appropriate in
pinpointing the source of the problems. You may want to examine the
Chrome command-line options in detail to see if anything could help.

Does Google provide a debugging build of Chrome? If so then you my want
to use it.

Frank Peters

Re: Request for verification - Chrome new window moved to other screens is black [ In reply to ]

frank.peters at comcast

Dec 26, 2014, 8:51 AM

Post #3 of 3 (1272 views)

Permalink

On Fri, 26 Dec 2014 11:42:19 -0500
Frank Peters <frank.peters@comcast.net> wrote:

>
> Are there command-line options to Chrome that would provide debugging
> output?
>

After doing a quick check, I find that these switches may be helpful:

Force logging to be enabled. Logging is disabled by default in release
builds.
--enable-logging

Sets the minimum log level. Valid values are from 0 to 3:
INFO = 0, WARNING = 1, LOG_ERROR = 2, LOG_FATAL = 3.
--log-level

Mailing List Archive

Mailing List Archive

Attached Files: