Ah great catch! Sorry to have caused you extra troubleshooting effort.
I’ll upload the fix to unstable asap, upload it to bullseye-backports once
it reaches testing in a few days, then I’ll work to get it into the next
bullseye release!

Stephen

On Aug 23, 2021 at 9:21:38 PM, Graham Clark <grcl...@gmail.com> wrote:

> Package: termshark
> Version: 2.2.0-1+b5
> Severity: important
> X-Debbugs-Cc: grcl...@gmail.com
>
> Dear Maintainer,
>
> There is an open issue against termshark on github that I believe is
> down to a small packaging omission on Debian. Here's a link to the
> bug: https://github.com/gcla/termshark/issues/114
>
> The symptom reported by users is that when termshark starts, most or
> all of the terminal is black and no information is visible. Termshark
> 2.2 can be "themed" and should have compiled-in to the binary a
> default set of themes. If no user-theme is provided, termshark loads
> the built-in default. Due to a small omission in the debian packaging
> rules for termshark, the default themes are not made available at
> compile-time and so termshark is unable to resolve many theme
> settings. Since this is not expected to fail, the defaults are
> unhelpful and result in large areas of the terminal screen showing up
> blank.
>
> I believe this problem can be fixed by adding this line to
> debian/rules:
>
> export DH_GOLANG_INSTALL_EXTRA := assets/themes
>
> Thanks!
> Graham
>
> -- System Information:
> Debian Release: 11.0
>  APT prefers testing
>  APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.8.0-59-generic (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: unable to detect
>
> Versions of packages termshark depends on:
> ii  libc6             2.31-13
> ii  tshark            3.4.7-1
> ii  wireshark-common  3.4.7-1
>
> termshark recommends no packages.
>
> termshark suggests no packages.
>
> -- no debconf information
>
>

Reply via email to