Printing fails with "Unable to open print file"
@michaelrsweet ya está trabajando en esto.
Desde el 7/5/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
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
- Lenguaje dominante
- C
- Estrellas
- 51
- Forks
- 21
- Merge medio
- 22 h 49 min
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de OpenPrinting/cups-browsed
-
Dificultad 3/5 1-2 días Aptitud para principiantes 67/100
OpenPrinting/cups-browsed#82 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
OpenPrinting/cups-browsed#77 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
OpenPrinting/cups-browsed#76 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 50/100
OpenPrinting/cups-browsed#75 ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 38/100
OpenPrinting/cups-browsed#71 ·
Todos los issues de OpenPrinting/cups-browsed
Issues similares
-
`sha256()` returns a wrong hash when libsql-ffi is built with gcc 11 or laterPosiblemente ocupada @colinhacks la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
tursodatabase/libsql#2333 ·
Los mantenedores suelen responder en 11 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
OpenPrinting/cups#1826 ·
Los mantenedores suelen responder en 1 día
-
Backport to 3.0 advertises a suffix that does not existPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
389ds/389-ds-base#8152 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
RetroAchievements/rcheevos#580 · 1 comentario ·
Los mantenedores suelen responder en 5 días