Patchutils now lives here. That is all.
Archive for the 'Techie stuff' Category
The idea is to make it work a bit more like the Printing screen in the GNOME Settings application. To make any changes you need to click Unlock first, and this fetches all the permissions you need in order to make any changes.
It’s nearly two years since I wrote about session printing, in which the user doesn’t need to modify a locally running CUPS instance in order to print to a network printer. The main advantage of having printing running entirely in the user session is that no special privileges are needed. After all, all you need to do is send the document over the network.
So what’s the current state of play?
Wanted to write this up in case someone else is scratching their head with the same issue.
Some routers are able to use both 2.4 GHz and 5 GHz frequencies, allowing devices to appear as though they are on the same network regardless of which they use. These actually provide two different wireless networks, with different SSIDs, and bridge between the two.
This works fine for most things, but today I realised that it’s the cause of a printer problem I’d been having. The printer was using the 2.4 GHz network while my laptop was using the 5 GHz one. When I tried to print, the mDNS name of the printer was needed so a multicast query was sent… but the printer didn’t respond.
The reason is the printer never received the query. The mDNS multicast address is 188.8.131.52, which is for multicast to the local subnet only. My router interprets this to mean that packets sent on the 2.4 GHz network will not reach the 5 GHz network.
I’ve been working on a Google Cloud Print GTK+ print module.
Google Cloud Print is a web service provided by Google that allows people to share their printers. In addition to being able to print to printers shared that way, there is a cloud equivalent of “Print to file” in the form of “Save to Google Drive”.
Here is a screenshot of the print dialog (from gedit) with this module included:
The cloudprint module uses gnome-online-accounts to obtain the OAuth 2.0 access token for the Google account, which is why the Google goa backend needs an additional scope.
Currently it can discover available printers, get simple details about them such as display name and status, and submit jobs without any special options. I plan to add options-setting based on the capabilities advertised by the printer.