Bugzilla

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see dependencies of 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nighlty and see if that gives you the same issue?  (You could test release but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions.)

For what it's worth, I tested this with Nightly and with Firefox-127-as-a-flatpak, on Ubuntu (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see dependencies of bug 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nighlty and see if that gives you the same issue?  (You could test release but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions.)

For what it's worth, I tested this with Nightly and with Firefox-127-as-a-flatpak, on Ubuntu (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see the many dependencies of bug 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nighlty and see if that gives you the same issue?  (You could test release but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions.)

For what it's worth, I tested this with Nightly and with Firefox-127-as-a-flatpak, on Ubuntu (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see the many dependencies of bug 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nighlty and see if that gives you the same issue?  (You could test official Firefox 127 release, too, but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions, whereas multiple versions of 127 release will try to gracefully launch windows in your existing browsing session instead of actually starting up.)

For what it's worth, I tested this bug with Nightly and also with Firefox-127-as-a-flatpak, on Ubuntu 22.04 (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see the many dependencies of bug 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nighlty and see if that gives you the same issue?  (You could test official Firefox 127 release, too, but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions, whereas multiple versions of 127 release will try to gracefully launch windows in your existing browsing session instead of actually starting up.)

For what it's worth, I tested this bug with Nightly and also with Firefox-127-as-a-flatpak, on Ubuntu 22.04 (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me, in the resulting PDF.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see the many dependencies of bug 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nightly and see if that gives you the same issue?  (You could test official Firefox 127 release, too, but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions, whereas multiple versions of 127 release will try to gracefully launch windows in your existing browsing session instead of actually starting up.)

For what it's worth, I tested this bug with Nightly and also with Firefox-127-as-a-flatpak, on Ubuntu 22.04 (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me, in the resulting PDF.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)

You mentioned:
> Using Firefox 127 from https://flathub.org/apps/org.mozilla.firefox

We do occasionally run into flatpak-specific rendering issues -- see the many dependencies of bug 1278719.  I don't think this particular bug is a known issue, but it's possible there's some flatpak-specific weirdness here.  Would you mind testing the "official" .tar.bz2 distribution of Firefox Nightly and see if that gives you the same issue?  (You could test official Firefox 127 release, too, but it's better/easier to test the Nightly version (https://www.mozilla.org/en-US/firefox/channel/desktop/#nightly ), since it will launch & run independently from your regular flatpak-installation's Firefox sessions, whereas multiple versions of 127 release will try to "gracefully" launch windows in your existing browsing session which makes it harder to be sure which flavor you're actually running.)

For what it's worth, I tested this bug with Nightly and also with Firefox-127-as-a-flatpak, on Ubuntu 22.04 (my local environment), printing https://en.wikipedia.org/wiki/Molybdenum to "Save to PDF" with default settings, and haven't been able to reproduce any issue yet. (The text looks nice and is selectable for me, in the resulting PDF.)

(In reply to Francewhoa (Francois Carpentier) from comment #10)
> Yes and no. Yes the code of Firefox is the same. But Firefox's input and output to its OS dependencies often vary between Ubuntu and Debian. I mean during the creation of PDF file, the code of the libraries, other dependencies varies, and the versions for those dependencies varies too. For example, but not limited to, CUPS, GL, graphic acceleration, Mesa, WebGL, etc.

(This is true in general -- but specifically for Firefox's print-to-PDF pipeline, there shouldn't be much in the way of distro-specific behavior-differences; Firefox brings along its own PDF printer, and I don't think that part touches CUPS at all.  But yes, there does seem to be something specific to your system so far that's involved here; we'll try to get to the bottom of what that is.  Testing official-Nightly is a good first start towards ruling things out. Thanks!)