Thanks. I use the SolydXK forum, and had posted the error there also. Only suggestion I had was to check that hplip was installed, which it is.
2) go to the cups config page and edit the config for the line that starts "LogLevel" to change from warn to debug
then post your error log to that forum.
Thanks. Hadn't thought of that. Unfortunately, it doesn't seem to make any difference. Looks as though the failure is happening before anything gets to cups.
3) Of course you could go back and re-configure in case you did not allow yourself to print?
easier to see at the cups page but also visible but harder to see in the file cupsd.conf which is a text file
on debian systems under /etc/cups needs root powers to edit
No problem there. Both the desktop and my laptop when I'm there are allowed access to all the network printers. And can print from other applications (such as LibreOffice or evince).
Another odd things is that whatever the problem, it seems to be Debian testing specific. I found another distro that is also based on Debian testing (can't remember the name off-hand), and it has exactly the same problem.
My laptop can print from SolydX in my own home network (I've got a Brother mono laser which is connected to my small home server). I've also discovered that Midori has the same problem when its in the network I described in my first post.
Looking through the Seamonkey crash reports (only recently found out that they produce a web report that makes a lot more sense than the raw reports leaving the machine), the crash always seems to be in libc-2.17. Arch is using libc-2.18, but I doubt I can install a later version of libc in SolydX without breaking lots of things.
What is really annoying is the problem seems to be quite specific to that particular network, and so far I've had no luck isolating the cause.