x2goprint(8)

📦
version 4.1.0.6 · 3 versions
, in alpine 3.24, debian trixie, fedora 43, fedora 44, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

💖 x2goprint — the X2Go Server Tool situation 💖

okay bestie, sit down, because we're talking about x2goprint, and it's genuinely giving backstage pass to your print jobs. It's part of the X2Go Server Tool family, and yeah, it lives in section 8 of the manual, so it's a sysadmin-flavoured little icon. 👑

✨ SYNOPSIS ✨

x2goprint <username> <session_id> <pdf_file> <title_file>

four arguments. no more, no less. she's picky like that. 💅

🌸 DESCRIPTION 🌸

So here's the tea. X2Go print jobs get rendered by the cups-x2go backend on your network's (central) CUPS server, and then they get copied over to the X2Go server that the X2Go print job was issued from. Cute, right? 🎀

On that X2Go server, cups-x2go drops two print job files — a PDF file and a title file — into the home directory of the POSIX system user ,,x2goprint'', where they just… sit there. Waiting. Rotting. No, jk, they await further processing by x2goprint. 🫶

Then the x2goprint command on the session's X2Go server — and yes, it's executed by the cups-x2go backend — prepares those job files for delivery to the X2Go client-side. It's literally the handoff. The relay. The main character passing the baton. 🏃♀️

lowkey important: x2goprint must run with root privileges and is executed by cups-x2go. not a suggestion, bestie. it's the rule. 🔥

🦋 ARGUMENTS 🦋

  • <username> — the owner of the incoming print jobs. That's who this whole thing is for. 💜
  • <session_id> — the unique identifier of the X2Go session that the processed print job is coming from. Every session's got her own little name tag. ⭐
  • <pdf_file> — the filename of the PDF file, exactly as dropped into ~x2goprint by cups-x2go. 🍓
  • <title_file> — the filename of the title file, also exactly as dropped into ~x2goprint by cups-x2go. 🌸

🔐 PERMISSIONS 🔐

X2Go uses the fuse-based SSH filesystem (SSHFS) for transferring print jobs from X2Go server to X2Go client. So if you want in on X2Go printing, you must be a member of the X2Go server's ,,fuse'' POSIX group. No group, no printing. It's giving velvet rope. 🙈

🌈 X2GO CLUSTER MODE 🌈

Okay so, scenario one: X2Go server and CUPS server are the same machine? Slay. No further setup for X2Go printing is necessary. Just vibes. ✨

Scenario two: X2Go server and CUPS server are hosted on separate machines? Then bestie, you need a special setup of sudo and SSH on the X2Go server(s) and the central CUPS server. Not optional. It's the whole plot. 😭

Refer to https://wiki.x2go.org/installing_x2go_printing_debian_ubuntu for further information — that's the wiki, go read it, it ate. 👑

💀 RETURN VALUES 💀

By x2goprint, nothing is reported on stdout or stderr. Silent. Mysterious. Iconic. 🤫

  • If x2goprint has run successfully, an exitcode of 0 is returned. 🎉
  • If the script has either been called by a non-root user or with the wrong number of command line arguments, a non-zero exitcode is returned. 🚨
fr fr, check your exit codes. she will not tell you what went wrong. she will simply leave. 💅

🎀 AUTHOR 🎀

This manual has been written by Mike Gabriel <mike.gabriel@das-netzwerkteam.de> for the X2Go project (https://www.x2go.org). tysm Mike, the lore is immaculate. 🫶

and that's the whole page bestie!! 💖 this was Version 4.1.0.6, dated Aug 2023, from the x2goprint(8) manual — periodt, no cap, go forth and print. 🖨️✨🌈

📦 where this page comes from