From: Solomon Tan <wjsota@gmail.com>
To: Yordan Karadzhov <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: Kernelshark v2 all-black plots area
Date: Wed, 20 Apr 2022 23:17:20 +0800 [thread overview]
Message-ID: <YmAkAE+5wy2mLncD@ArchDesktop> (raw)
In-Reply-To: <146d751e-eb40-52f8-fbd1-3dc2627d03f9@gmail.com>
On Wed, Apr 20, 2022 at 11:06:49AM +0300, Yordan Karadzhov wrote:
> Hi Solomon,
>
> There are few things you can do.
> The way KernelShark build finds the font file is by running the following command in a shell:
>
> fc-list FreeSans |grep FreeSans.ttf | cut -d':' -f 1 -z
>
> So run the same command in a terminal and try to figure out why it fails.
> If it fails because the 'FreeSans.ttf' does not exist, you can manually provide a path to some other font file to be used.
It failed because FreeSans was installed in my system as otf instead of ttf hahaha.
>
> cd kernel-shark/build
> ./cmake_clean.sh
> cmake -DTT_FONT_FILE=/path/to/some/font/YourFont.ttf ..
Thank you! This command worked. I just specified the path to the otf
file instead of the ttf file, and it worked like a charm. kernel-shark
is installed and working well!
I actually faced another issue as well - which was that the compilation
appeared to be successful but kernelshark was not made at all because
FreeSans was missing. So the black plot I got was from the one I
installed from the package manager. But now I have kernelshark installed
from your github so all is good now :).
I would like to propose some changes to the CMakefile in light of my
experience. I will send them in reply to this email shortly. For your
consideration, please :).
Thank you!
Cheers,
Solomon
>
> Please let me know if this works.
> Thanks!
> Yordan
>
>
> On 20.04.22 г. 3:38 ч., Solomon Tan wrote:
> > On Tue, Feb 09, 2021 at 03:06:14PM +0200, Yordan Karadzhov (VMware) wrote:
> >
> > Hi Yordan!
> >
> > I have the same issue of an all-black plots area.
> >
> > > Ciao Dario,
> > >
> > > There is a bug in one of the patches from the last patch-set I sent. This
> > > bug was reported by Tzvetomir. My guess is that you are hitting the same
> > > issue. If this is the case you must also have an error message saying
> > > "Unable to find FreeSans font".
> >
> > I have the same error message. I tried installing the `gnu-free-fonts`
> > package on Arch, but it does not get rid of the error.
> > >
> > > You can manually do the fix suggested by Tzvetomir (see his reply to [PATCH
> > > 15/24] kernel-shark: Update KsDualMarker and KsGLWidget) or just get a
> > > corrected (rebased) version of the code from
> > > https://github.com/yordan-karadzhov/kernel-shark-v2.beta
> >
> > I tried installing from your github repo, but the same error still
> > shows. I have all other dependencies installed. FreeSans is the only
> > complaint from the cmake .. command. Is there another potential fix I
> > could try?
> >
> > >
> > > Please let me know if this fixes your issue.
> > > Thank you very much for testing and reporting!
> > >
> > > Best
> > > Yordan
> >
> > Thank you!
> > Cheers,
> > Solomon
next prev parent reply other threads:[~2022-04-20 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 10:48 Kernelshark v2 all-black plots area Dario Faggioli
2021-02-09 13:06 ` Yordan Karadzhov (VMware)
2021-02-09 16:13 ` Dario Faggioli
2021-02-10 11:21 ` Yordan Karadzhov (VMware)
2021-02-10 14:51 ` Dario Faggioli
2021-02-10 15:47 ` Yordan Karadzhov (VMware)
2021-02-10 16:15 ` Dario Faggioli
2021-02-10 16:23 ` Steven Rostedt
2022-04-20 0:38 ` Solomon Tan
2022-04-20 8:06 ` Yordan Karadzhov
2022-04-20 15:17 ` Solomon Tan [this message]
2022-04-20 15:38 ` [PATCH 1/2] kernel-shark: Make FreeSans a compulsory component Solomon Tan
2022-04-20 15:38 ` [PATCH 2/2] kernel-shark: Allow FreeSans otf in addition to ttf Solomon Tan
2022-04-21 12:16 ` Yordan Karadzhov
2022-04-21 12:04 ` [PATCH 1/2] kernel-shark: Make FreeSans a compulsory component Yordan Karadzhov
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=YmAkAE+5wy2mLncD@ArchDesktop \
--to=wjsota@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=y.karadz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).