We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

Problem with showing PDF from local disk

  • 2 respostas
  • 0 têm este problema
  • 3 visualizações
  • Última resposta por mr.ms

mr.ms
mr.ms
more options

I have a problem with PDF showing.

If I take PDF generated by the lilypond and I open it from link like https://gitlab.com/lilypond/lilypond/uploads/f51162c65d5194db6dd3b4fb86fa4e42/bug.pdf, PDF looks well. If I open same PDF from disk by using link like file:///tmp/bug.pdf , PDF looks different (wrong). Some ledger lines missing.

I am running firefox 117.0 (64 bit) for Arch linux.

I have a problem with PDF showing. If I take PDF generated by the lilypond and I open it from link like https://gitlab.com/lilypond/lilypond/uploads/f51162c65d5194db6dd3b4fb86fa4e42/bug.pdf, PDF looks well. If I open same PDF from disk by using link like file:///tmp/bug.pdf , PDF looks different (wrong). Some ledger lines missing. I am running firefox 117.0 (64 bit) for Arch linux.
Capturas de ecrã anexadas

Solução escolhida

I can't reproduce this on Ubuntu 23.04.

Does it still happen in Troubleshoot Mode?

Ler esta resposta no contexto 👍 0

Todas as respostas (2)

zeroknight
zeroknight
more options

Solução escolhida

I can't reproduce this on Ubuntu 23.04.

Does it still happen in Troubleshoot Mode?

mr.ms
mr.ms Proprietário da pergunta
more options

zeroknight said
I can't reproduce this on Ubuntu 23.04. Does it still happen in Troubleshoot Mode?

Thanks for reply.

According to your tip, I did some more experiments. And it looks like the problem disappears after restarting of Firefox to Troubleshoot Mode and I do not see it again after disabling Troubleshoot Mode.

So, it looks like some "ghost bug".