--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: cups: CUPS cant access library files because they have different names
- From: Anthony Gaudino <anthonygaudino45@gmail.com>
- Date: Mon, 26 Jul 2021 11:32:41 +0100
- Message-id: <162729556171.531002.13912107979652593638.reportbug@anthony>
Package: cups
Version: 2.3.3op2-3+deb11u1
Severity: important
X-Debbugs-Cc: anthonygaudino45@gmail.com
Dear Maintainer,
When I try to print anything with CUPS I had the following 2 errors on
the CUPS log:
```
E [23/Jul/2021:17:37:03 +0100] [Job 27] libcups.so load failure
E [23/Jul/2021:17:37:03 +0100] [Job 27] Unable to open raster stream - : Broken pipe
```
The printer would not print anything.
After investigating, I found out that CUPS is trying to access
`/usr/lib/x86_64-linux-gnu/libcups.so` and `/usr/lib/x86_64-linux-gnu/libcupsimage.so`
but Debian has these files named as `libcups.so.2` and
`libcupsimage.so.2` instead.
I solved the problem for myself by just copying those files and saving
with the names CUPS was looking for.
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages cups depends on:
ii cups-client 2.3.3op2-3+deb11u1
ii cups-common 2.3.3op2-3+deb11u1
ii cups-core-drivers 2.3.3op2-3+deb11u1
ii cups-daemon 2.3.3op2-3+deb11u1
ii cups-filters 1.28.7-1
ii cups-ppdc 2.3.3op2-3+deb11u1
ii cups-server-common 2.3.3op2-3+deb11u1
ii debconf [debconf-2.0] 1.5.77
ii ghostscript 9.53.3~dfsg-7
ii libavahi-client3 0.8-5
ii libavahi-common3 0.8-5
ii libc6 2.31-13
ii libcups2 2.3.3op2-3+deb11u1
ii libgcc-s1 10.2.1-6
ii libstdc++6 10.2.1-6
ii libusb-1.0-0 2:1.0.24-3
ii poppler-utils 20.09.0-3.1
ii procps 2:3.3.17-5
Versions of packages cups recommends:
ii avahi-daemon 0.8-5
ii colord 1.4.5-3
Versions of packages cups suggests:
pn cups-bsd <none>
pn cups-pdf <none>
pn foomatic-db-compressed-ppds | foomatic-db <none>
pn smbclient <none>
ii udev 247.3-6
-- debconf information:
cupsys/raw-print: true
cupsys/backend: lpd, socket, usb, snmp, dnssd
--- End Message ---
--- Begin Message ---
- To: 991517-done@bugs.debian.org
- Subject: Re: Bug#991517: cups: CUPS cant access library files because they have different names
- From: Brian Potkin <claremont102@gmail.com>
- Date: Sun, 9 Jan 2022 20:28:41 +0000
- Message-id: <09012022200321.654d22043105@desktop.copernicus.org.uk>
- In-reply-to: <162729556171.531002.13912107979652593638.reportbug@anthony>
- References: <162729556171.531002.13912107979652593638.reportbug@anthony>
On Mon 26 Jul 2021 at 11:32:41 +0100, Anthony Gaudino wrote:
> Package: cups
> Version: 2.3.3op2-3+deb11u1
> Severity: important
> X-Debbugs-Cc: anthonygaudino45@gmail.com
>
> Dear Maintainer,
>
> When I try to print anything with CUPS I had the following 2 errors on
> the CUPS log:
>
> ```
> E [23/Jul/2021:17:37:03 +0100] [Job 27] libcups.so load failure
> E [23/Jul/2021:17:37:03 +0100] [Job 27] Unable to open raster stream - : Broken pipe
> ```
>
> The printer would not print anything.
>
> After investigating, I found out that CUPS is trying to access
> `/usr/lib/x86_64-linux-gnu/libcups.so` and `/usr/lib/x86_64-linux-gnu/libcupsimage.so`
> but Debian has these files named as `libcups.so.2` and
> `libcupsimage.so.2` instead.
>
> I solved the problem for myself by just copying those files and saving
> with the names CUPS was looking for.
Dear Debian User,
Further information on your issue was requested some time ago but there
hasn't been any response from you. Use of our limited, volunteer
supported resources is best served by not keeping open inactive bugs any
longer than desirable, especially in cases where the package concerned
is older than the current stable Debian version. Consequently, the
report is now being closed.
Regards,
Brian.
--- End Message ---