All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Dimitrov <picmaster@mail.bg>
To: meta-freescale@yoctoproject.org,
	 Otavio Salvador <otavio@ossystems.com.br>,
	Prabhu Sundararaj <B36876@freescale.com>,
	Tiago.Velasque@congatec.com,  Gary Thomas <gary@mlbassoc.com>,
	Khem Raj <raj.khem@gmail.com>
Subject: Re: Chromium layout rendering issue
Date: Tue, 12 May 2015 22:41:55 +0300	[thread overview]
Message-ID: <55525783.40502@mail.bg> (raw)
In-Reply-To: <5551053A.1000601@mlbassoc.com>

Hi guys,

FYI, the layout issue is not observed when using Yocto Fido and FSL
kernel 3.10.53. I wasted almost 2 days of updating Chromium
dependencies, but lost interest and decided to entirely move to Fido.

I've discovered another issue introduced by the latest meta-browser
updates - Chromium fails to start due to missing files. This is now
fixed, and a patch was submitted to openembedded-devel ML. I can't
provide a link there, as my green-horn posts needs to be approved, but
here's a Github link to the patch:

https://github.com/picmaster/meta-browser/commit/d80d6f62b07aeaefaab965b2c885e78806ca4878

During the testing of my latest build, Chromium again froze for about
10s, so I'll keep an eye on it to see what triggers it, and share
if/when I have more info.

Kind regards,
Nikolay


  reply	other threads:[~2015-05-12 19:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  2:41 Chromium layout rendering issue Nikolay Dimitrov
2015-05-08 12:49 ` Otavio Salvador
2015-05-08 13:19   ` Tiago.Velasque
2015-05-08 13:33     ` Otavio Salvador
2015-05-12 14:10       ` Tiago.Velasque
2015-05-08 13:32   ` Nikolay Dimitrov
2015-05-10 11:45     ` Nikolay Dimitrov
2015-05-11 18:06       ` Prabhu S
2015-05-11 19:38         ` Gary Thomas
2015-05-12 19:41           ` Nikolay Dimitrov [this message]
2015-05-08 22:47   ` Gary Thomas
2015-05-08 22:52     ` Eric Nelson
2015-05-08 23:29       ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55525783.40502@mail.bg \
    --to=picmaster@mail.bg \
    --cc=B36876@freescale.com \
    --cc=Tiago.Velasque@congatec.com \
    --cc=gary@mlbassoc.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.