From: Jacob MacDonald <jaccarmac@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 54033@debbugs.gnu.org
Subject: bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark.
Date: Fri, 4 Mar 2022 12:19:09 -0600 [thread overview]
Message-ID: <CACy6W0CAGA4Ru4ShhYnnivV0R77NXU52em=rKxHeQ4k8yYhH2A@mail.gmail.com> (raw)
In-Reply-To: <0faceea8-a28d-49a6-8f36-0cc0c5c70655@www.fastmail.com>
On Fri, Mar 4, 2022 at 7:19 AM Leo Famulari <leo@famulari.name> wrote:
> I think we'll have to fix this bug the old-fashioned way: ... debugging
I tried a little stracing, which didn't illuminate anything.
The results of my attempt at diffing are described above; I intend to
try modifying the build steps, but if there's any advice for debugging
Python builds I'll gladly accept it.
The changes to the Python build system between the working commit and
the broken merge seem moderate, but I've only skimmed them. I haven't
dived into changes to dependencies yet.
When I installed the working version as described above, my desktop
shortcut stayed broken until I relogged or started it from a fresh
terminal. This seems like an environment issue to me, but the desktop
files didn't change in relevant ways.
> reporting it upstream
Given the similarity in the breakage over versions, it seems unlike an
upstream bug to me. The only similar issue I can find is the font one,
and the fonts are properly installed in the broken tree.
next prev parent reply other threads:[~2022-03-04 18:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 7:05 bug#54033: Calibre's ebook-viewer only shows white-on-white or dark-on-dark Jacob MacDonald
2022-02-17 23:41 ` Leo Famulari
2022-02-20 3:39 ` Jacob MacDonald
2022-02-20 4:33 ` Leo Famulari
[not found] ` <CACy6W0Aj8CAnc47p_R5rHw2d3vNaFEoKaxhRRJRXyhVQekcR7w@mail.gmail.com>
2022-02-20 5:05 ` bug#54033: Fwd: " Jacob MacDonald
[not found] ` <18be745d-10bf-4be9-bef3-c88cc88d9554@www.fastmail.com>
2022-02-20 5:05 ` Jacob MacDonald
[not found] ` <CACy6W0AaVRTrrduJPi_ZCWyoMK8KoKDbEyVWEFQ2xtgZxRMgQg@mail.gmail.com>
2022-02-20 5:05 ` Jacob MacDonald
2022-02-21 3:46 ` Jacob MacDonald
2022-02-21 6:00 ` Jacob MacDonald
2022-02-22 4:51 ` Jacob MacDonald
2022-03-04 4:07 ` Jacob MacDonald
2022-03-04 13:19 ` Leo Famulari
2022-03-04 18:19 ` Jacob MacDonald [this message]
2022-03-04 14:07 ` Guillaume Le Vaillant
2022-03-04 20:27 ` bdju via Bug reports for GNU Guix
2022-03-08 14:52 ` Guillaume Le Vaillant
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACy6W0CAGA4Ru4ShhYnnivV0R77NXU52em=rKxHeQ4k8yYhH2A@mail.gmail.com' \
--to=jaccarmac@gmail.com \
--cc=54033@debbugs.gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).