Print to PDF not working (StyledEdit)

Software Native
1

Hello, I’m having trouble using Print To File in StyledEdit. I’ll do File > Print and in the Print setup window I’ll select the “Save as PDF” printer, and then when I print, the destination file chooser dialog freezes up and quits redrawing right.

Logs:

KERN: runtime_loader: Cannot open file /boot/home/config/non-packaged/add-ons/Print/transport/Print To File (needed by <NULL>): No such file or directory
KERN: runtime_loader: Cannot open file /boot/home/config/add-ons/Print/transport/Print To File (needed by <NULL>): No such file or directory
KERN: runtime_loader: Cannot open file /boot/system/non-packaged/add-ons/Print/transport/Print To File (needed by <NULL>): No such file or directory

I’ll refer to each of these log lines as A, B, and C, respectively.
Regarding A, /boot/home/config/non-packaged/add-ons/Print/ does exist, but is empty – it ends there.
Regarding B, the folder /boot/home/config/add-ons/ doesn’t exist at all.
Regarding C, /boot/system/non-packaged/add-ons/Print/ does exist, but is empty – it ends there.

BUT, note that ‘/boot/system/add-ons/Print/transport/Print To File’ does exist!
In /boot/system/non-packaged/add-ons, I added ./Print/transport and inside added the link ‘Print To File’ which points to it. This is what was being looked for in C.
However, it still fails in the same way, although with different logs.
Logs:

KERN: runtime_loader: Cannot open file /boot/home/config/non-packaged/add-ons/Print/transport/Print To File (needed by <NULL>): No such file or directory
KERN: runtime_loader: Cannot open file /boot/home/config/add-ons/Print/transport/Print To File (needed by <NULL>): No such file or directory

Maybe after all the system was finding the Print To File file. It probably checks ‘/boot/system/add-ons/Print/transport/Print To File’ last (or after, anyway).

Anyway, any help getting this to work would be appreciated!

2

non-packaged not beeing found is harmless. This is a mechanism with which you can overwrite the packaged files (in this case drivers)

It will use the non-packaged version first, and the packaged one after that.

EDIT:
to clarify one additional thing the line for /boot/home/config is also harmless. This is an additional place a packaged library can be installed too. but normally they are in /system

You can use the command “listimage” on the commandline to see which images are loaded for which application (this includes the print to file driver)

I don’t think your log lines are related to your problem.

This, plus the information of what haiku revisision you are using should be enough to file a ticket with.

Regards

1 Like