Dear Maintainer,

I use a rather quircky duck in my prompt as a separator and it suddenly stopped
working for one reason or the other. I first thought it had to do with my font,
so I did all the things you would think of:

  fc-list :family="CommitMono"
  sudo fc-cache -fv
  fc-cache -fv

I also grabbed a newer version of CommitMono, with these settings:

  {
     "alternates" : {
        "cv01" : false,
        "cv02" : false,
        "cv03" : false,
        "cv04" : false,
        "cv05" : false,
        "cv06" : false,
        "cv07" : false,
        "cv08" : false,
        "cv09" : false,
        "cv10" : false,
        "cv11" : false
     },
     "features" : {
        "ss01" : true,
        "ss02" : true,
        "ss03" : true,
        "ss04" : true,
        "ss05" : true
     },
     "italic" : false,
     "letterSpacing" : 0,
     "lineHeight" : 1,
     "weight" : 400
  }

To no avail.

When you have Commit Mono installed (or perhaps any other nerdfont) from
https://commitmono.com/ and open the Unicode menu (ctrl+shift+u on my system)
and you search by name (f2) for duck and select the first option, U+1f986, you
would see a nice little ducky.

With kitty 0.47.3-1 you no longer have that. It becomes a small red-ish dot.
I reverted back to kitty 0.47.0-3 and the duck re-appears.

I marked the bug as important, as I am a bit cautious as I don't want to bump
it to serious, although I am convinced it might be a serious bug.

Cheers,
Wesley

More emojis are breaking:

🦦 / 🔊 / 🫂 / 🪖

I think the bug has to become serious.

Hi Wesley,

Since this appears to be an issue with the upstream code and not the Debian
package, please consider to forward reports like this to the upstream bug
tracker instead of here.

For now, I have just done that for you.

It might be fixed in 0.47.4 as I see some font rendering commits
there (but did not test) -- I'll let upstream maintainer confirm this.

Thanks for reporting,
Nilesh

Hi Nilesh,

Thank you very much!
Debian specifically asks not to submit bugs upstream, see
https://www.debian.org/Bugs/Reporting

 > Don't file bugs upstream
 >
 > If you file a bug in Debian, don't send a copy to the upstream
 > software maintainers yourself to start with, as it is possible that
 > the bug exists only in Debian. If necessary, the maintainer of the
 > package will forward the bug upstream, or ask you to do so after
 > they've checked that it isn't Debian-specific.

I don't run kitty from source, so I'm not really inclined to submit bugs
upstream for a Debian package.

In addition to this, it isn't really a nice way for users to having to
understand which package requires you to submit upstream vs to Debian,
eg, zsh just forwards the bugs upstream. One would need to look into
salsa to see if custom patches are applied for Debian and exclude or
include those before building from source in order to confirm the bug is
indeed upstream.

Debian also doesn't always track upstreams versions, it may be behind,
filing bugs upstream may cause annoyances with upstream maintainers,
xscreensaver is the most notable example of this.

I therefor will continue to use reportbug to submit bugs against
packages in Debian, you as a package maintainer should also know there
is a bug in testing/unstable and not just upstream.

I hope you can understand my reasoning in this. Thanks again for filing
the bug upstream.

Cheers,
Wesley

Done: Maytham Alsudany <maytham@debian.org>
Version: 0.47.4-1
[...]

I've confirmed that this is fixed as of kitty 0.47.4, which has just
been uploaded.

No, it's not serious, as it is not a policy violation and does not
seriously impede you're ability to use kitty (you can still run
commands).

Done: Maytham Alsudany <maytham@debian.org>
Version: 0.47.4-1
[...]

I've confirmed that this is fixed as of kitty 0.47.4, which has just
been uploaded.

No, it's not serious, as it is not a policy violation and does not
seriously impede you're ability to use kitty (you can still run
commands).