Problems with Deskjet 2630 y Ubuntu 18.04

Hi,
Can you please share the log file for the printer.
please follow the below instruction to generate the log file.
1: open a terminal and run the command "sudo hp-logcapture"
2: open another terminal and give a document print.
3: come to the previous terminal and quit the log cature.
This will generate the logs tar file.

Thanks,
Badal Kumar

Thanks for the quick answer.

When I tried the command at the first point the answer is this

sudo hp-logcapture
[sudo] contraseña para jalonso:
Traceback (most recent call last):
  File "/usr/bin/hp-logcapture", line 35, in <module>
    from base import utils,tui,module, os_utils
  File "/usr/share/hplip/base/module.py", line 30, in <module>
    from . import tui, utils, device
  File "/usr/share/hplip/base/device.py", line 41, in <module>
    from . import status
  File "/usr/share/hplip/base/status.py", line 32, in <module>
    import cupsext
ImportError: No module named cupsext

In the second terminal I have written "lp prueba.txt" and the answer is

lp prueba.txt
la id solicitada es DeskJet_2600-777 (1 archivo(s))

In the desktop an emergent window said that the printing have started but it didn't work.
I don't know if there is a logs tar file.

Thanks
Jose Luis Alonso

Hi,

Install HPLIP ".run" file once again properly.
Then you will not see the error "ImportError: No module named cupsext".
After that you do the below steps to generate logs.

$ sudo hp-logcapture
-Archiving system logs (i.e. syslog, message, error_log). Press
(y=yes*, n=no, q=quit):

Press "yes" here
Then it will prompt to do a (print/scan/fax) (do it in some other terminal).
Then comeback to this terminal , it will ask to press "yes" once again if you are done with printing/scanning.
Do that, then logs will be generated as a ".tar" file.

Regards,
Srinivas Teja.

I have followed your instructions and I have created a new bug report with the log .tar file at

https://bugs.launchpad.net/hplip/+bug/1797125

Regards,

Jose Luis.

Ok, I wait for the solution.

thanks.

Finally, the problem was with ghostscript.

I've found the solution at

https://askubuntu.com/questions/924915/broken-ghostscript-configuration

_______________

Here's what worked for me:

sudo rmdir /usr/share/ghostscript/9.25/iccprofiles
sudo apt-get install --reinstall libgs9-common

Something had left an empty directory at /usr/share/ghostscript/9.25/iccprofiles. It appears that libgs9-common creates a symlink from /usr/share/ghostscript/9.25/iccprofiles to /usr/share/color/icc/ghostscript, but silently fails to create it if there's already something in the filesystem.

___________

Thanks for all

Jose Luis.

Finally, the problem was with ghostscript.

I've found the solution at

https://askubuntu.com/questions/924915/broken-ghostscript-configuration

_______________

Here's what worked for me:

sudo rmdir /usr/share/ghostscript/9.25/iccprofiles
sudo apt-get install --reinstall libgs9-common

Something had left an empty directory at
/usr/share/ghostscript/9.25/iccprofiles. It appears that libgs9-common
creates a symlink from /usr/share/ghostscript/9.25/iccprofiles to
/usr/share/color/icc/ghostscript, but silently fails to create it if
there's already something in the filesystem.

___________

Thanks for all

Jose Luis.