site  contact  subhomenews

Easy network printing with CUPS

January 12, 2018 — BarryK

I have been trying all day to setup printing over a small network, just two PCs running Easy 0.6.6, connected to an ethernet router (and to the Internet via wi-fi wan, to my mobile phone hotspot).

One PC, my "midi-tower", has a Brother HL-2040 laser printer connected via USB port. Local printing works fine. The other PC is my Mele "mini-pc", and I want to be able to print from it.

The problem is, I cannot get the "ipp" protocol to work. I have studied online documentation, and can get the client machine, my mini-pc, to see the remote printer, however when do an actual print, get the dreaded "Filter failed".

As stated, I have messed around all day, trying different things. Then, I found something that "just works", very simple. I would like to acknowledge "paulkerry" for this info:

Just a comment: there is a lot of outdated, vague, ambiguous and misleading documentation about CUPS online. For example, one "very official" site explained the format of the ipp protocol as:


...without explaining that only "hostname" and "printername" must be substituted, and the text "printers" must be left as-is. There wasn't even an example, nor was it properly explained how to find the printername.

Anyway, I did learn how to specify ipp properly, but got stuck at "Filter failed".

The method described by paulkerry works, so here is a little tutorial to explain how to set it up. Note, I plan to semi-automate this, by extending QuickSamba, which I plan to rename to EasyShare. Anyway, the tut...

1: Firewall

I ran the firewall setup on both client (my mini-pc) and server (my midi-tower) PCs, so that the CUPS port (631) is enabled. In this snapshot, I have also enabled Samba ports, but that isn't necessary for just printing with CUPS:


On the server-PC, just setup the local printer as you normally would, but tick some extra boxes...

2: Server PC

You need to have the cupsd daemon running and point the web browser at http://localhost:631. In Puppy/Quirky/Easy, you do this by running the "CUPS Printer Wizard":


A window will popup asking if you want to add a new printer, and you click "Yes", then you will get the CUPS web interface:

image on "Adding Printers and Classes", then the next window:

images each of those, 1, 2, 3 and 4. Do not miss "Change Settings". Probably "Allow remote administration" is optional, but I enabled it, as I was then able to bring up the CUPS web interface of the server-PC on my client-PC. Next window...

...well, anyone who has setup a local printer will be familiar with this. Continuing, as per usual, except an important checkbox to tick...

...the first two boxes are pre-filled. It is not essential, but useful, to fill "Location". And, you must tick "Share This Printer".

In the next window, you choose a driver...


And set some printer options...


That's it, the server-PC is setup. Before setting up the client, you will need to know the IP-address of the server. A few ways of doing that. Open a terminal and type "ifconfig", and you will see it -- in my case it is "":


In Puppy/Easy/Quirky, there is no need to edit the /etc/cups/cupsd.conf main configuration file, as it is pre-configured OK. Note, for this tutorial, I am running pristine EasyOS Pyro64 version 0.6.6.

Now for the client-PC...

3: Client PC

Over on my Mele mini-pc, setup is easy-peasy. I created file /etc/cups/client.conf...


...with content just one line, "ServerName <ip address of server>"

Finally, restart the cupsd daemon...


...and run "lpstat -t" to verify that the remote printer is found.

That's it, nothing more to do. If you ran an application and choose "Print...", the remote printer will be offered, in my case, my Brother HL-2040.

Also, the CUPS web interface of the server can be accessed from the client, by going to "" in the client web browser.

As stated, I have thoughts how this setup can be semi-automated, including automatic creation and update (if the ip-address changes) of /etc/cups/client.conf. Stay tuned.

Tags: linux, easy, quirky

Intel and AMD video conflict

December 30, 2017 — BarryK

I reported yesterday about the result of plugging in my AMD Radeon HD6870 card:


Booting Easy Pyro64 0.6.4 from USB-drive, get a desktop. Fine, but 'glxinfo' reported software rasterising. Also, exit from X to commandline results in a blank screen. Also, under certain conditions, that I have not yet narrowed down, there is a hang at bootup.

My midi-tower PC also has on-board Intel video. There is a file, /etc/modeprobe.d/i915.conf containing this:

options i915 modeset=1

And /etc/modeprobe.d/radeon.conf, both with this:

options radeon modeset=1

I simply removed the i915.conf file, rebooted, and that fixed the exit-from-X-to-commandline, also bootup-to-commandline-no-X., but then I restored i915.conf, and exit-from-X-to-commandline, also bootup-to-commandline-no-X, are still fixed. Hmmm. The UEFI-Setup is showing on-board video as disabled ...the UEFI must have done that automatically? I don't know. There's too much that I don't know here.

This needs more testing, and rerwin's thoughts on this are also very helpful:

I will append to this post as I discover more.

Tags: easy, quirky, linux

Problems with JWM window manager

December 28, 2017 — BarryK

I have been using JWM 2.3.7 in recent builds of Quirky and Easy, however, have encountered rather a lot of bugs. The most recent report was choosing the "Move" option from the right-click menu in a window title-bar crashing JWM -- which brings down all of X.

So, I have been compiling and testing the latest from github, but this has not been smooth sailing, as I have reported to the Puppy Forum:

So, with revision 1675, ~/.jwmrc needs new <Mouse> tags, else is broken. It looks like Joe will fix that, so it defaults to working without those tags.

I keep thinking that I liked the old revision 976... it was pretty rock solid. I hunted through the Pup Forum for any reports of bugs with 976...

666philb reported 976 fixed a bug:

Ah, I recall someone mentioned this one... Hesse James reported 976 cannot properly display additional vertical trays:

For the JWMDesk app, radky commented about an icon-sizing problem with vertical panels in 976:

Incidentally, radky is continuing to support older versions of JWM in his JWMDesk.

Tags: easy, quirky, linux

Precord updated to 9.0.3

December 25, 2017 — BarryK

Precord, an audio recorder and player, has been in all my Easy, Quirky, and earlier pups, for many years.

The author, mcewanw, has a thread on the Puppy Forum:

I have just upgraded from version 8.1.4 to 9.0.3, and fixed a couple of small things, so my PET is 9.0.3-1.

It is not a good practice to have a hidden file in /etc, so I have changed /etc/precord/.precordrc to /etc/precord/precordrc.

Ditto, ~/.precord/.precordrc is now ~/.precord/precordrc

JWM does not display the icon, mini-record.xpm in the menu. It used to, but version 2.3.7 doesn't.

The reason is, it is actually a png file.

I have removed it from the PET, that is, removed /usr/share/mini-icons/mini-record.xpm, as woofQ (used to build Easy and Quirky) now has mini-record.xpm, an actual XPM image.

That's at rootfs-skeleton/usr/local/lib/X11/mini-icons/mini-record.xpm in woofQ

My modified PET:

One thing, the XPM image doesn't look quite as nice as the PNG.

Tags: easy, quirky, linux

Fatdog64 720-final released

December 21, 2017 — BarryK

Fatdog is a fork of Puppy Linux, and I have always found it exciting to watch its progression. Reason, there are often very clever innovations. The developers are 'kirk' and 'jamesbond', and more recently 'fatdog', 'sfr', 'step' and others.

Fatdog forked from Puppy Linux many years go, using the Unleashed build system, before Puppy went over to the Woof build system. Here is a Puppy family-tree: doesn't actually show dates, but Fatdog forked from Puppy 4.0, I forget how many years ago that was. The developers took Unleashed off in a new direction, and more recently they are able to build the packages of Fatdog from source, see forum post:

They did use Woof, before branching entirely to their own build system, with complete compile-from-source, see timeline:

Development is still happening very intensely, and version 720 of Fatdog64 has just been released, see announcement on the Puppy Forum:


Here is the Fatdog homepage:

I will also download it, to examine some of the things listed in the release notes -- with our puplets, we cross-pollinate, and I will likely find some new ideas for Easy and Quirky.

Tags: linux

Puppy Linux Xenialpup 7.5 released

December 07, 2017 — BarryK

At last, another official Puppy Linux release! My goodness, if you look at Distrowatch, the last official release announcement was 01micko's Slacko 6.3 in November 2015:

It gave the impression that nothing was happening on the Puppy-front, however, a visit to the Puppy Forum shows, as always, feverish activity. Lots of people developing and testing, and many custom releases. However, no one put their hand up for their release to be the next official pup. Until now.

Philip Broughton, '666philb' on the forum, has coordinated this pup, and we were getting feedback that this should be the next official pup. So, Philip decided to go for it.

Here is the announcement:

Release notes:



Join discussion in the Puppy Forum here:



Great news. This pup is of course, built with woof-CE.

Tags: linux

Kernel 4.13.9 compiled in Pyro64

October 24, 2017 — BarryK

In Quirky Pyro64 to be more precise.

The build scripts and patches are uploaded here:

I hit a very strange bug. When the build script ran "make menuconfig", the terminal crashed. No error messages, it just aborted. I recompiled ncurses, the terminal still crashed.

Very odd. The urxvt terminal emulator is working fine, using it everyday in Pyro64. I googled of course, found the same crash reported a few times, but no definite fix.

So, changed the script to run "make gconfig", the GTK config, and that worked fine.

Tags: linux