unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Marinus Savoritias <marinus.savoritias@disroot.org>
To: 43293@debbugs.gnu.org
Subject: bug#43293: Icecat is missing glyphs after the last update
Date: Fri, 18 Sep 2020 18:13:51 +0200	[thread overview]
Message-ID: <e066be7e-8a50-1a89-0e5e-f6db412fe193@disroot.org> (raw)
In-Reply-To: <337bf480-23a6-14c1-1ca5-4d4db099344b@disroot.org>

I tried to remove icecat including cache and config and everything and 
install again. The problem is still there though. No numbers anywhere.

Marinus Savoritias

On 9/13/20 12:55 PM, Marinus Savoritias wrote:
> So it seems like two of the problems fixed themselves.
> I still cant see any number in the browser though.
> In their place there is just a blank space.
> 
> Marinus Savoritias
> 
> On 9/9/20 3:10 PM, Marinus Savoritias wrote:
>> I forgot to add that the issue seems specific to icecat. Qutebrowser 
>> works fine.
>>
>> Marinus Savoritias
>>
>> On 9/9/20 3:08 PM, Marinus Savoritias wrote:
>>> The numbers and some of the letters are missing from the last release.
>>> If I open the guix home page in the Download button the numbers are 
>>> not shown for example. Also the star is missing from the bookmark 
>>> button on the top.
>>>
>>> Guix git commit:
>>>    guix 057d584
>>>      repository URL: https://git.savannah.gnu.org/git/guix.git
>>>      branch: master
>>>      commit: 057d584b981d9a3293be03ee863d40a61c8aae74
>>>
>>> With Icecat: 68.12.0-guix0-preview1
>>>
>>> Marinus Savoritias
>>>
>>>
>>>
>>
>>
>>
> 
> 
> 




  reply	other threads:[~2020-09-18 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 13:08 bug#43293: Icecat is missing glyphs after the last update Marinus Savoritias
2020-09-09 13:10 ` Marinus Savoritias
2020-09-13 10:55   ` Marinus Savoritias
2020-09-18 16:13     ` Marinus Savoritias [this message]
2020-09-22 17:45 ` Marinus Savoritias

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=e066be7e-8a50-1a89-0e5e-f6db412fe193@disroot.org \
    --to=marinus.savoritias@disroot.org \
    --cc=43293@debbugs.gnu.org \
    /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).