Printing fails with "Unable to open print file"

未关闭
#53 6 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@michaelrsweet 已经在做这个了。

开始于 2025年5月7日。

评估

这个 Issue 还没有评估数据。

描述

Hello,

I have a number of machines where printing failed with error "Unable to open print file". As this error message is not especially meaningful, I edited the cups source code (backend/ipp.c) so that additionally the full path of the print file, the name of the process trying to open the print file and the effective UID and GID of that process were given.

So, I found that the print file was a temporary file in /tmp, belonging to user root and group lp, but only readable by root; that the process is named in the scheme (all printers are imported from remote by cups-browsed)

ipp://$RemoteHost:$RemotePort/printers/$Printer

which was running with effective UID of the user trying to print and effective GID lp.

Of. course, the print file could not be opened with these permissions.

But I had another machine where printing worked, with almost the same configuration, and found that there, the process named ipp://$RemoteHost:$RemotePort/printers/$Printer was running with effective UID 0.

So, I deinstalled and then reinstalled all cups packages, deleted all cups-related caches and spools I could find, and somehow after some tests I thought that the problem was solved, but now I have the same again: process with effective UID != 0 trying to open file exclusively accessible by root cannot open the file.

What can I do?

CUPS 2.4.2

Regards
Christoph

主要语言
C
星标
51
派生
21
平均合并
22 小时 49 分钟
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenPrinting/cups-browsed 的其他 Issue

查看 OpenPrinting/cups-browsed 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。