HPLIP

hplip-3.15.11 setup gets stuck

Bug #1521006 reported by Sergey Dovganyuk
56
This bug affects 11 people
Affects Status Importance Assigned to Milestone
HPLIP
Confirmed
Undecided
Unassigned

Bug Description

Experienced two, as I think, related issues:
1) When I run setup file hplip-3.15.11.run it gets stuck at this point

ENTER USER PASSWORD
-------------------
Please enter the sudoer (*******)'s password:
/

And these are the processes

$ ps a
...
19775 pts/1 S+ 0:00 sh ./hplip-3.15.11.run
19831 pts/1 S+ 0:00 /bin/bash ./hplip-install
19834 pts/1 S+ 0:02 python ./install.py -i
19952 pts/2 Ss+ 0:00 /usr/bin/sudo true
...

I see there is "sudo", but I have entered the sudo password already. Well I break setup and "sudo" it.

So far so good till I get to the issue 2

2) As expected I get this

"error: hp-plugin should not be run as root/superuser
error: hp-plugin command failed. Please run hp-plugin manually."

I continue the setup and get into GUI mode and after all I get

"Please run 'hp-plugin' as normal user to install plug-ins."

I run

$ hp-plugin

Accept license agreement and get stuck at this

Plug-in version: 3.15.11
Installed HPLIP version: 3.15.11
Number of files to install: 42

And my processes are

  779 pts/6 S+ 0:00 python /usr/bin/hp-plugin
  818 pts/6 S+ 0:00 sh -c sh /home/.../.hplip/hplip-3.15.11-plugin.run --keep --nox11 -- -u /usr/bin/python
  819 pts/6 S+ 0:00 sh /home/.../.hplip/hplip-3.15.11-plugin.run --keep --nox11 -- -u /usr/bin/python
  905 pts/6 S+ 0:00 /bin/bash ./hplip-plugin-install -v 3.15.11 -c 42 -u /usr/bin/python
  911 pts/6 S+ 0:00 /usr/bin/python ./plugin_install.py -v 3.15.11 -c 42 -u
  915 pts/4 Ss+ 0:00 /usr/bin/sudo /usr/bin/python installPlugin.py

And again I find sudo awaiting. I run sudo command manually

$ cd ~/.hplip/plugin_tmp/
$ /usr/bin/sudo /usr/bin/python installPlugin.py
Executing installPlugin.py

Success!
Break the stuck hp-plugin.
Continue with the step 1) and finish.

P.S.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

Actually run Kubuntu.

See original description
Tags: wily
Sergey Dovganyuk (dovganuk-sergey)
description: updated
Revision history for this message
thomasd (thomas-dingermaenner) wrote :

Please fix it - after hours of shouting about HP i read this thread... Now i can print and scan!
Thank you for sharing this hint!

Revision history for this message
Dejavu_Dmitry (dejavudmitry) wrote :

Also have this problem

Revision history for this message
Patrick (patrick-schweizer-ing) wrote :

I have the same problem.
@dovganuk-sergey your workaround worked for me. Thanks a lot for sharing!

Revision history for this message
Novice (aamecon-activity) wrote :

I had the similar problem (question 278898 on hplip)

Thanks to Sergey Dovganyuk it was solved!
Thank you very much for saving hours of time!

Revision history for this message
Bohdan Vasylenko (bohdan-vasilenko) wrote :

I specifically signed up in order to say thank you.

Щиро дякую

Flames_in_Paradise (ellisistfroh-deactivatedaccount)
Changed in hplip:
status: New → Confirmed
tags: added: wily
Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

The workaround from Sergey Dovganyuk worked here (Kubuntu 15.10/16.04æ) too:

$ cd ~/.hplip/plugin_tmp/
$ sudo python3 installPlugin.py

Thanks!

Revision history for this message
Flames_in_Paradise (ellisistfroh-deactivatedaccount) wrote :

My workaround-command was taken from comment #10 in bug #1486731 (hplip-3.15.7-plugin.run doesn't return, registerd on 22.10.2015)

Revision history for this message
Dennis (deki24) wrote :

There is no plugin_tmp folder in .hplip

Revision history for this message
Sergey Dovganyuk (dovganuk-sergey) wrote :

@Dennis
Before you going to find .hplip, look at "$ ps a" output and find "pts/4 Ss+ 0:00 /usr/bin/sudo /usr/bin/python installPlugin.py" there. Once you find the last you must have the first, Otherwise I guess you didn't follow all the steps described.

Revision history for this message
Sanjay Kumar (sanjay-kumar14) wrote :

Hello Dennis,

Please take the files from https://bugs.launchpad.net/hplip/+bug/1510950 and merge/replace them into /usr/share/hplip/base directory and let me know if this fixes the problem.

Thanks,
Sanjay

Revision history for this message
stefano malini (stefano-malini) wrote :

hi,
my hplip 3.15.11 installation process has gone in a little different way:

as mentioned by Sergey after i have seen that was blocked on

ENTER USER PASSWORD
-------------------
Please enter the sudoer (*******)'s password:
/

i stopped the process and ran the command using sudo and followed the gui instructions until this error message:

error: hp-systray cannot be run as root. Exiting

the processes were as below:

$ ps a
...
29877 pts/1 Sl+ 0:00 python /usr/bin/hp-systray
29878 pts/1 S+ 0:00 python /usr/bin/hp-systray
29879 pts/1 S+ 0:00 python /usr/bin/hp-systray

So, i ran

$ hp-systray

HP Linux Imaging and Printing System (ver. 3.15.11)
System Tray Status Service ver. 2.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

/usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK
  set_interactive(1)

HP Linux Imaging and Printing System (ver. 3.15.11)
HPLIP upgrade latest version ver. 1.0

Copyright (c) 2001-15 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

At this point it didn't exit to the prompt. I had to exit using ctrl+c.

After that i tried to print and scan and it runs.

hope that everything is really ok!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.