After upgrade to Ubuntu 13.04 printing to my Samsung SCX-3405W stop working.
Using: suld-driver-4.01.17-1, cups-1.6.2-1ubuntu5
Printing from cups fails with message "filter failed". Looking in to the /var/log/cups/error_log:
...
Started filter /usr/lib/cups/filter/pdftopdf (PID 3698)
D [08/May/2013:10:56:55 +0200] [Job 157] Started filter /usr/lib/cups/filter/pdftops (PID 3699)
D [08/May/2013:10:56:55 +0200] [Job 157] Started filter /usr/lib/cups/filter/pstospl (PID 3700)
D [08/May/2013:10:56:55 +0200] [Job 157] Started backend /usr/lib/cups/backend/socket (PID 3701)
D [08/May/2013:10:56:55 +0200] [Job 157] Restarted by "tau".
D [08/May/2013:10:56:55 +0200] [Job 157] PID 3700 (/usr/lib/cups/filter/pstospl) stopped with status 127 (File too large)
D [08/May/2013:10:56:55 +0200] [Job 157] Hint: Try setting the LogLevel to "debug" to find out more.
D [08/May/2013:10:56:55 +0200] [Job 157] Tiskarna: error while loading shared libraries: libscmssc.so: cannot open shared object file: No such file or directory
...
Further investigating the problem:
# ldd /usr/lib/cups/filter/pstospl
linux-vdso.so.1 => (0x00007fff265fd000)
libscmssc.so => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7223bee000)
libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x00007f722398d000)
...
# ldd /usr/lib/cups/filter/libscmssc.so
linux-vdso.so.1 => (0x00007fff345a4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0a14f70000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0a14c6b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0a14a54000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0a146
The scmssc library is not on the library path of the filter. Workaround: make link to the library from the global library dir:
# ln -sv /usr/lib/cups/filter/libscmssc.so /usr/lib
run ldd again and check the library is found. Print!
Probably the library path is configurable in the CUPS or Printer config files but I didn't want to give more time to the problem once I found the workaround.
UPDATE(2013-05-09): problem solved: update to newer suld-driver-4.01.17 package
Using: suld-driver-4.01.17-1, cups-1.6.2-1ubuntu5
Printing from cups fails with message "filter failed". Looking in to the /var/log/cups/error_log:
...
Started filter /usr/lib/cups/filter/pdftopdf (PID 3698)
D [08/May/2013:10:56:55 +0200] [Job 157] Started filter /usr/lib/cups/filter/pdftops (PID 3699)
D [08/May/2013:10:56:55 +0200] [Job 157] Started filter /usr/lib/cups/filter/pstospl (PID 3700)
D [08/May/2013:10:56:55 +0200] [Job 157] Started backend /usr/lib/cups/backend/socket (PID 3701)
D [08/May/2013:10:56:55 +0200] [Job 157] Restarted by "tau".
D [08/May/2013:10:56:55 +0200] [Job 157] PID 3700 (/usr/lib/cups/filter/pstospl) stopped with status 127 (File too large)
D [08/May/2013:10:56:55 +0200] [Job 157] Hint: Try setting the LogLevel to "debug" to find out more.
D [08/May/2013:10:56:55 +0200] [Job 157] Tiskarna: error while loading shared libraries: libscmssc.so: cannot open shared object file: No such file or directory
...
Further investigating the problem:
# ldd /usr/lib/cups/filter/pstospl
linux-vdso.so.1 => (0x00007fff265fd000)
libscmssc.so => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7223bee000)
libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x00007f722398d000)
...
# ldd /usr/lib/cups/filter/libscmssc.so
linux-vdso.so.1 => (0x00007fff345a4000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f0a14f70000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0a14c6b000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f0a14a54000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0a146
The scmssc library is not on the library path of the filter. Workaround: make link to the library from the global library dir:
# ln -sv /usr/lib/cups/filter/libscmssc.so /usr/lib
run ldd again and check the library is found. Print!
Probably the library path is configurable in the CUPS or Printer config files but I didn't want to give more time to the problem once I found the workaround.
UPDATE(2013-05-09): problem solved: update to newer suld-driver-4.01.17 package