From: Michael Rasmussen via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Michael Rasmussen <mir@datanom.net>
Subject: [pve-devel] Fancy probably broken
Date: Sat, 20 Sep 2025 10:58:36 +0200 [thread overview]
Message-ID: <mailman.196.1758359170.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 7188 bytes --]
[-- Attachment #1.1.1: Type: text/plain, Size: 1018 bytes --]
Hi all,
Yesterdays upgrade of libwebkit2gtk presumably brakes fancy. Every HTML
email renders to dark black. Litehtml shows no such behaviour so it is
not claws but libwebkit2gtk that causes the problem.
libwebkit2gtk version in question:
- libwebkit2gtk-4.1-0:amd64 (2.48.6-1, 2.50.0-1)
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
https://keys.openpgp.org/vks/v1/by-fingerprint/A1306C5094B5E31B7721A3A66F4844C7CA7501AA
mir <at> datanom <dot> net
https://keys.openpgp.org/vks/v1/by-fingerprint/0C14CD9479667E848770C8F98417B6C5E1BB093F
mir <at> miras <dot> org
https://keys.openpgp.org/vks/v1/by-fingerprint/5F71405B571CB8EE2A414A4FC77C11E049A06E66
--------------------------------------------------------------
'During times of universal deceit, telling the truth becomes a
revolutionary act.' -George Orwell
Don't compare floating point numbers just for equality.
- The Elements of Programming Style (Kernighan & Plaugher)
[-- Attachment #1.1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-09-20 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 8:58 Michael Rasmussen via pve-devel [this message]
[not found] <20250920105836.3b5ec4f0@sleipner.datanom.net>
2025-09-20 9:00 ` Michael Rasmussen via pve-devel
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=mailman.196.1758359170.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=mir@datanom.net \
/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