Librewolf browser can't print/save webpages as pdf

In my home laptop librewolf print-save as pdf only save nearly blank pages. In the laptop i have at work that is also a FreeBSD install, this works fine. Am i missing some package from the FreeBSD repo in my home laptop? This is done with any webpage i am trying to print/save as pdf.
 
I don't have this problem, if that's any help. I guess check which packages are on the work laptop relating to pdfs (and maybe cups or whatever you use to print) and see if they're all on the home laptop.
Also, the obvious, make sure that they're the same version of FreeBSD and of librewolf.
 
Update: just installed waterfox on the home laptop that had the problem and it is working to print webpages as pdf. In Librewolf forums.freebsd.org can be printed but no other sites. It must be a Librewolf issue, maybe a configuration option or something.
 
I also had this problem, I thought it was because I hardened the user.js, but not, I can't remember well but try to disable your firewall (pf for me) and test. I managed to block access to printers with a poorly made pf.conf...
 
I also had this problem, I thought it was because I hardened the user.js, but not, I can't remember well but try to disable your firewall (pf for me) and test. I managed to block access to printers with a poorly made pf.conf...
In Librewolf options i have an exception for https://forums.freebsd.org to be able to use cookies and site data, and its the only site i can print as pdf. So it must be something about security/privacy options.
 
In Librewolf options i have an exception for https://forums.freebsd.org to be able to use cookies and site data, and its the only site i can print as pdf. So it must be something about security/privacy options.
Wouldn't you have a self made user.js ? I haven't noticed the problem with the default setup (config.js or something like this), but I can kill the option with user.js keys. I'll have a look.
 
cupsd seems to require libavahi, and i refuse to install any software by this UNIX-ruining Lennart Poettering. (avahi, pulseaudio, systemd)
What am I reading? I must say I don't like Pulseaudio for looking like an industrial grift to overcomplicate audio dependencies on consumer computers. Nobody needs a thing of it. Just amplify the data to sound according to its format...
 
What am I reading? I must say I don't like Pulseaudio for looking like an industrial grift to overcomplicate audio dependencies on consumer computers. Nobody needs a thing of it. Just amplify the data to sound according to its format...
Did anyone try to build CUPS from ports with AVAHI=off ?
I guess libavahi-client.so will still be a required dependency, maybe not...?
 
Did anyone try to build CUPS from ports with AVAHI=off ?
I guess libavahi-client.so will still be a required dependency, maybe not...?
Using it in a 'distro' because it's enabled by default. No idea what it's for. The printing works with a foomatic driver. Until now, I managed to avoid the cups webinterface for everything except when installing a new printer. Then I have to get its hard written serial number that has to be selected on the webpage.
What happens if I don't include avahi?
 
Using it in a 'distro' because it's enabled by default. No idea what it's for but it's old. The printing works with a foomatic driver. Until now, I managed to avoid the cups webinterface for everything except when installing a new printer. Then I have to get its hard written serial number that has to be selected on the webpage, or read it from another computer.
What happens if I don't include avahi?
 
What am I reading? I must say I don't like Pulseaudio for looking like an industrial grift to overcomplicate audio dependencies on consumer computers. Nobody needs a thing of it. Just amplify the data to sound according to its format...
In other news..

>We are building cryptographically verifiable integrity into Linux systems



It's a slippery slope 😬
 
Did anyone try to build CUPS from ports with AVAHI=off ?
I guess libavahi-client.so will still be a required dependency, maybe not...?
Cupsd has it as lib dependency, so that's probably not going to work. What do you want to run that needs libavahi-client.so?
In other news..

>We are building cryptographically verifiable integrity into Linux systems



It's a slippery slope 😬
I read something about a hardware polling system but I think it's still too high-level to own all channels.
An audit system that only points at problems would already have value. Take IME. That's a shadow computer on your PC mainboard that communicates with devices independently from the installed OS. I have a Ryzen 7 system that accesses its own physical disks outside of the OS. It already starts doing things while you're still in the BIOS/UEFI setup wuthout a kernel running.
This can be interpreted as a out-of-the-box compromised system and flagged as a threat in public sale. I hope my ISP isn't wet too and passing non-TCP data to Intel or something, or there's a kill-switch listening for a signal...
 
Cupsd has it as lib dependency, so that's probably not going to work. What do you want to run that needs libavahi-client.so?

I read something about a hardware polling system but I think it's still too high-level to own all channels.
An audit system that only points at problems would already have value. Take IME. That's a shadow computer on your PC mainboard that communicates with devices independently from the installed OS. I have a Ryzen 7 system that accesses its own physical disks outside of the OS. It already starts doing things while you're still in the BIOS/UEFI setup wuthout a kernel running.
This can be interpreted as a out-of-the-box compromised system and flagged as a threat in public sale. I hope my ISP isn't wet too and passing non-TCP data to Intel or something, or there's a kill-switch listening for a signal...
Hardware and software problems should be identified and corrected to their source. No need for an OS to act as its hardware that runs onto is compromised. IME should be disabled by microcode/firmware. Or better avoided altogether if possible. I think its hard for Intel to mingle with millions of computers without being noticed, but black box OS (through cryptographically signing-i think with mandatory systemd by the way)? Much easier. Every update, software piece, new interface has unintended (or malintended) consequences. If a cryptographically signed Linux gets mass adopted, apps may demand that you run one of these or you are suspect of being a pirate/hacker. Look at systemd. Shilled its way through major distros and installed dependencies in so many packages. Software has expectations to compile/install/run, and if you are not fullfilling them you get rejected.

Of course if someone wants to make a huge bloated opressive init system or a cryptographically signed Linux its his free will to do so, but lobbying to get it to mass adoption is looked down upon.

Thats why Linus told Poettering that software should be fine with an old kernel dependency, because updates that are a real need and updates to deliberately deprecate and break interfaces for your market share/political gain is a totally different thing. You get the point.

PS: sometimes an OS does not need to become more popular.
 
Back
Top