[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#968787: No printer can be installed in cups



Hello Karsten,
I am no involved in the packaging cups but I tried to
reproduce your cups issue inside a minimal VM.

Unfortunately I did not get the message
"Gesamte Anfrage zu gross" / "Request Entity Too Large".

Therefore it seems you need to supply some more informations like
- with which user you are authenticating against cups?
- have you done some cups configuration changes?
- the relevant parts of /var/log/cups/error_log and
    /var/log/cups/access_log

Kind regards,
Bernhard
# Buster amd64 qemu VM 2020-08-21


apt update
apt dist-upgrade


apt install systemd-coredump sddm xserver-xorg mc task-kde-desktop task-german-kde-desktop firefox-esr-l10n-de task-print-server
apt build-dep cups


reboot


mkdir /home/benutzer/source/cups/orig -p
cd    /home/benutzer/source/cups/orig
apt source cups
cd


########


# login

# firefox

http://localhost:631

Administration
Add Printer

# Add Printer page is shown, no error message "Gesamte Anfrage zu gross"


########


benutzer@debian:~/source/cups/orig/cups-2.2.10$ grep "Gesamte Anfrage zu gross" . -Rn -B1
./locale/cups_de.po-4701-msgid "Request Entity Too Large"
./locale/cups_de.po:4702:msgstr "Gesamte Anfrage zu gross"

benutzer@debian:~/source/cups/orig/cups-2.2.10$ grep "Request Entity Too Large" . -Rn
./cups/http-support.c:1529:        s = _("Request Entity Too Large");

benutzer@debian:~/source/cups/orig/cups-2.2.10$ cat -n ./cups/http-support.c | grep 1529 -C1
  1528      case HTTP_STATUS_REQUEST_TOO_LARGE :
  1529          s = _("Request Entity Too Large");
  1530          break;

benutzer@debian:~/source/cups/orig/cups-2.2.10$ grep HTTP_STATUS_REQUEST_TOO_LARGE . -Rn
./cups/request.c:1154:    case HTTP_STATUS_REQUEST_TOO_LARGE :
./cups/http.h:271:  HTTP_STATUS_REQUEST_TOO_LARGE,      /* Request entity too large */
./cups/http.h:327:#    define HTTP_REQUEST_TOO_LARGE    HTTP_STATUS_REQUEST_TOO_LARGE
./cups/http-support.c:1528:    case HTTP_STATUS_REQUEST_TOO_LARGE :
...
./scheduler/client.c:1364:              if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1541:              if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1578:            if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1789:              if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1807:              if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1843:            if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1929:            if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1969:                if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./scheduler/client.c:1987:              if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE,
./scheduler/client.c:2038:              if (!cupsdSendError(con, HTTP_STATUS_REQUEST_TOO_LARGE, CUPSD_AUTH_NONE))
./doc/help/cupspm.html:6150:        <tr><th>HTTP_STATUS_REQUEST_TOO_LARGE </th>        <td class="description">Request entity too large</td></tr>

Reply to: