Created attachment 173949 [details] screenshot Hello, after update chrome from 51 to the 52.0.2743.116, my chrome browser window looks weird. See attached screenshot. Messages from terminal: [3534:411147264:0822/153347:ERROR:linux_util.cc(122)] Not implemented reached in std::string base::GetLinuxDistro() [3534:411131904:0822/153347:ERROR:battery_status_manager_default.cc(25)] Not implemented reached in virtual bool device::(anonymous namespace)::BatteryStatusManagerDefault::StartListeningBatteryChange() [3534:411131904:0822/153347:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153347:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153348:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153349:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153349:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile [3534:411131904:0822/153350:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153350:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153351:ERROR:image_skia_operations.cc(69)] ImageSkiaRep size mismatch in MaskedImageSource [3534:411131904:0822/153351:ERROR:battery_status_manager_default.cc(29)] Not implemented reached in virtual void device::(anonymous namespace)::BatteryStatusManagerDefault::StopListeningBatteryChange()
Sorry, just a "Me too" comment. But indicating that importance is not "Affect Only Me". The contents of options file is as below. PULSEAUDIO is additionally activated, but might not affects. # This file is auto-generated by 'make config'. # Options for chromium-47.0.2526.73 _OPTIONS_READ=chromium-47.0.2526.73 _FILE_COMPLETE_OPTIONS_LIST=CODECS DEBUG DRIVER GCONF KERBEROS PULSEAUDIO TEST OPTIONS_FILE_SET+=CODECS OPTIONS_FILE_UNSET+=DEBUG OPTIONS_FILE_UNSET+=DRIVER OPTIONS_FILE_SET+=GCONF OPTIONS_FILE_SET+=KERBEROS OPTIONS_FILE_SET+=PULSEAUDIO OPTIONS_FILE_UNSET+=TEST
*** Bug 212494 has been marked as a duplicate of this bug. ***
Additional investigation - chrome has broken graphics only on my Intel i915 integrated graphics (Core i5 Toshiba Z30 notebook). On my home server with Nvidia 210 card + nvidia-driver-340 from package, same chrome version run fine. Also: when I run chrome from home server remotely on the X on my notebook - also crippled. And when I run chrome from my notebook remotely on the X on my home server - yes, this is fine. Both FreeBSD 11.0-RELEASE. So maybe it's something with graphics card driver....
Another "me too", installed from packages. I can confirm that all of my packages are fully up-to-date.
*** Bug 213351 has been marked as a duplicate of this bug. ***
This problem appears to be related to some left-over file. I created a new user and started chrome as that user, and the problem didn't occur. As stated in PR 213351, I had already removed ~/.cache/chromium and ~/.config/chromium directories and restarted, but the problem persisted.
Restest on my 11.0-RELEASE-p1 - created new user "test" with adduser. Then: $ su - test $ DISPLAY=localhost:0 chrome Still crippled. Maybe, the left-over file is not in /home, but somewhere in /usr (artifact left after the package upgrades?).
I also have hit this bug, but for me it was connected to buggy VESA X11 video driver. It can be repeated in 100% cases that chromium can not correcly draw its window unless you set display resolution some way (I use systemsettings from KDE -- just set fonts DPI to 96, and voila!)
I haven't seen this bug because I was working in out/${TARGET} directory. After installation the bug occurs. Which means the "make install" target hasn't done the job well. Fixed in my current branch, soon it would be commited, I believe.
(In reply to clutton from comment #9) I'm testing your work via poudriere, so I hope to commit it very soon. Thanks Clutton :)
I can confirm this. I had Xft.dpi set to 144 in .Xdefaults. Setting DPI to anything _other_ than 96 seems to break chromium. 1) ~/.Xdefaults with Xft.dpi:96 ; % chromium ==> chromium works fine 2) ~/.Xdefaults with Xft.dpi:96 ; % chromium --force-device-scale-factor=2 ==> chromium broken 3) ~/.Xdefaults with Xft.dpi:144 ; % chromium ==> chromium broken mfg Tobias
(In reply to Tobias C. Berner from comment #11) it seems from a quick testing, that anything above Xft.dpi: 124 cripples chrome for me (so "anything other than 96" from before was wrong :) ). mfg Tobias
(In reply to Carlos J. Puga Medina from comment #10) I was wondering, is there any progress on getting this committed to the ports tree? Or anything that can be done to help?
(In reply to Gavin Atkinson from comment #13) It's almost ready done. Clutton is still investigating why lld is unusable on i386. ATM you can install it from our GH repo: https://github.com/gliaskos/freebsd-chromium
I just built and installed the github version. I have no sound. I am on x64 with 11.0-RELEASE-p1.
(In reply to bcomputerguy from comment #15) There is something about sound (ALSA vs PULSEAUDIO) in this thread: https://forums.freebsd.org/threads/57366/
(In reply to Petr Fischer from comment #16) I am actually a poster in that thread. I though the patches were already added to this github version but it seems not.
Solved in version chromium-54.0.2840.100 (official package). Thanks!
MARKED AS SPAM