HP All-in-One Printer No Longer Scanning

**Budgie2** · 09-Sep-2019, 03:27

Used to use HP ColorLaserjet 2840 to scan using Skanlite on Leap 15.2. It is a network device connected through the Lan and it worked, although there were odd niggles. It never worked for hplip installation but worked as a manual network install using the fixed ip of the printer.

Now I have updated to Tumbleweed and have problems. Hplip still fails with a crash. In spite of all the available hplip packages available the Tumbleweed package still will not work with this printer, a python fault if I remember correctly but I have an unsolved thread on this from before Tumbleweed.

However I can install the printer using a network installation as previously but now Skanlite does not work at all. I suspect a firewall problem and would appreciate some help please in diagnosing and solving please.

Budgie2

**hcvv** · 09-Sep-2019, 04:09

You say you configured the printer anew. What does YaST > Hardware > Scanner say?

**Budgie2** · 09-Sep-2019, 06:14

Hi Henk and thanks for your reply.

All my previous printer installations and this present installation with this printer have been done using Yast>Printer install and by using the Connection Wizard using TCP Port (AppSocket/JetDirect) and inserting the fixed IP address of this printer using manual insertion of IP address. I have never succeeded in finding this printer by search button and hplip crashes when I try and use it. It has been a problem since I purchased the printer many years ago but this method worked for me. As far as I recall I never tried to install the scanner part of this printer, it just worked until I changed to Tumbleweed when the scanner no longer worked.

With the introduction of Tumbleweed (at least I have only just seen it,) there is now a separate button for Scanner and the printer driver for HP Color Laserjet 2840 all in one is available so this is what I have been trying.

I have stopped the Firewall temporarily hoping this would do the trick but alas, using Yast>Scanner I get:-

No scanner was detected and no active scanner or driver exists.

so perhaps not a firewall issue?

**hcvv** · 09-Sep-2019, 06:45

Originally Posted by Budgie2

using Yast>Scanner I get:-

Thanks. I just asked because to me that is the most obvious thing to do and you did not mention it.

**Knurpht** · 09-Sep-2019, 06:59

hp-setup should not crash, I manage several TW machines and it works fine on all of them. Which makes me wonder about:
- how you update
- how you run hp-setup
- how the printer is connected, i.e. wired? wireless?
- like always: what does it say when it crashes
- your repos ( zypper lr -d )

**Budgie2** · 09-Sep-2019, 08:28

Hi and thanks for the reply. First my repos:-

Code:

alastair@install:~> zypper lr -d
# | Alias                            | Name                       | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                  | Service
--+----------------------------------+----------------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------------------+--------
1 | download.opensuse.org-non-oss    | Main Repository (NON-OSS)  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/                |        
2 | download.opensuse.org-oss        | Main Repository (OSS)      | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/                    |        
3 | download.opensuse.org-tumbleweed | Main Update Repository     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                      |        
4 | libdvdcss                        | libdvdcss                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/openSUSE_Tumbleweed/                  |        
5 | openSUSE-20190810-0              | openSUSE-20190810-0        | No      | ----      | ----    |   99     | rpm-md | cd:/?devices=/dev/disk/by-id/ata-IBM_SATA_DEVICE_81Y3681_M86E1KM4319 |        
6 | packman                          | packman                    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed/                    |        
7 | repo-debug                       | openSUSE-Tumbleweed-Debug  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/              |        
8 | repo-source                      | openSUSE-Tumbleweed-Source | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/             |        
alastair@install:~>

I update using the KDE prompt which used to ask for

Code:

sudo zypper dup

but for the last three or four updates there has been an update button.

The printer is connected by RJ45/copper lan through switch to my computer. No wifi in this link.

I run hp-setup using the Yast>Hardware>Printer>Add> and the prompt is:- No matching driver found. Change the string or try 'Find More'.

I then select the hp-setup button which brings up Device Discovery and select the Button "Network/Ethernet/Wireless network (direct connection or JetDirect)" and 'Next' button.

I do this with firewall stopped but I can also and ususally do it using manual method by entering the IP fixed address. Both approaches find the correct printer and I then get the crash warning window. I cannot cut and paste but it says:-

We are sorry, python3.7 closed unexpectedly.
You cannot report this error, because python3.7does not provide a bug reporting address.

.

If I select Developer Information Tab from the crash warning window. I get:-

Code:

Application: python3.7 (python3.7), signal: Aborted
 Using host libthread_db library "/lib64/libthread_db.so.1".
 [Current thread is 1 (Thread 0x7f78526ba680 (LWP 30156))]
 

 Thread 5 (Thread 0x7f7841dd6700 (LWP 30161)):
 #0  0x00007f7852818e05 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
 #1  0x00007f7842cfea5b in ?? () from /usr/lib64/dri/r600_dri.so
 #2  0x00007f7842cfe907 in ?? () from /usr/lib64/dri/r600_dri.so
 #3  0x00007f7852812faa in start_thread () from /lib64/libpthread.so.0
 #4  0x00007f7852c7873f in clone () from /lib64/libc.so.6
 

 Thread 4 (Thread 0x7f7842718700 (LWP 30160)):
 #0  0x00007f7852818e05 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
 #1  0x00007f7842cfea5b in ?? () from /usr/lib64/dri/r600_dri.so
 #2  0x00007f7842cfe907 in ?? () from /usr/lib64/dri/r600_dri.so
 #3  0x00007f7852812faa in start_thread () from /lib64/libpthread.so.0
 #4  0x00007f7852c7873f in clone () from /lib64/libc.so.6
 

 Thread 3 (Thread 0x7f7849634700 (LWP 30158)):
 #0  0x00007f7852c6980c in read () from /lib64/libc.so.6
 #1  0x00007f784e8e570f in ?? () from /usr/lib64/libglib-2.0.so.0
 #2  0x00007f784e931c8e in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
 #3  0x00007f784e933342 in ?? () from /usr/lib64/libglib-2.0.so.0
 #4  0x00007f784e93346f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
 #5  0x00007f784f6109ab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
 #6  0x00007f784f5b920b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
 #7  0x00007f784f3f1f91 in QThread::exec() () from /usr/lib64/libQt5Core.so.5
 #8  0x00007f784bc954f6 in ?? () from /usr/lib64/libQt5DBus.so.5
 #9  0x00007f784f3f3112 in ?? () from /usr/lib64/libQt5Core.so.5
 #10 0x00007f7852812faa in start_thread () from /lib64/libpthread.so.0
 #11 0x00007f7852c7873f in clone () from /lib64/libc.so.6
 

 Thread 2 (Thread 0x7f784bb4e700 (LWP 30157)):
 #0  0x00007f7852c6dcbf in poll () from /lib64/libc.so.6
 #1  0x00007f784e5aa742 in ?? () from /usr/lib64/libxcb.so.1
 #2  0x00007f784e5ab3fa in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
 #3  0x00007f784bdd0f18 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
 #4  0x00007f784f3f3112 in ?? () from /usr/lib64/libQt5Core.so.5
 #5  0x00007f7852812faa in start_thread () from /lib64/libpthread.so.0
 #6  0x00007f7852c7873f in clone () from /lib64/libc.so.6
 

 Thread 1 (Thread 0x7f78526ba680 (LWP 30156)):
 [KCrash Handler]
 #5  0x00007f7852bb6dd1 in raise () from /lib64/libc.so.6
 #6  0x00007f7852ba0549 in abort () from /lib64/libc.so.6
 #7  0x00007f784f3baa59 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib64/libQt5Core.so.5
 #8  0x00007f784e332f46 in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtCore.so
 #9  0x00007f784e33a7fd in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtCore.so
 #10 0x00007f784f5e55dc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQt5Core.so.5
 #11 0x00007f78500df392 in QAbstractButton::clicked(bool) () from /usr/lib64/libQt5Widgets.so.5
 #12 0x00007f78500df5aa in ?? () from /usr/lib64/libQt5Widgets.so.5
 #13 0x00007f78500e094f in ?? () from /usr/lib64/libQt5Widgets.so.5
 #14 0x00007f78500e0b15 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQt5Widgets.so.5
 #15 0x00007f7850745acb in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtWidgets.so
 #16 0x00007f785002cd06 in QWidget::event(QEvent*) () from /usr/lib64/libQt5Widgets.so.5
 #17 0x00007f7850746c8b in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtWidgets.so
 #18 0x00007f784ffeac42 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
 #19 0x00007f784fff4113 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
 #20 0x00007f78508a8516 in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtWidgets.so
 #21 0x00007f784f5ba5b2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
 #22 0x00007f784fff3203 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool, bool) () from /usr/lib64/libQt5Widgets.so.5
 #23 0x00007f78500489c9 in ?? () from /usr/lib64/libQt5Widgets.so.5
 #24 0x00007f785004ba24 in ?? () from /usr/lib64/libQt5Widgets.so.5
 #25 0x00007f784ffeac42 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
 #26 0x00007f784fff3ec0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQt5Widgets.so.5
 #27 0x00007f78508a8516 in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtWidgets.so
 #28 0x00007f784f5ba5b2 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/libQt5Core.so.5
 #29 0x00007f784f9bc4b8 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /usr/lib64/libQt5Gui.so.5
 #30 0x00007f784f9bdd3b in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib64/libQt5Gui.so.5
 #31 0x00007f784f996acb in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Gui.so.5
 #32 0x00007f784bdd1e4a in ?? () from /usr/lib64/libQt5XcbQpa.so.5
 #33 0x00007f784e931683 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
 #34 0x00007f784e933430 in ?? () from /usr/lib64/libglib-2.0.so.0
 #35 0x00007f784e93346f in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
 #36 0x00007f784f610991 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
 #37 0x00007f784f5b920b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5
 #38 0x00007f784f5c0d82 in QCoreApplication::exec() () from /usr/lib64/libQt5Core.so.5
 #39 0x00007f78508a108a in ?? () from /usr/lib64/python3.7/site-packages/PyQt5/QtWidgets.so
 #40 0x00007f785295ef61 in _PyMethodDef_RawFastCallKeywords () from /usr/lib64/libpython3.7m.so.1.0
 #41 0x00007f785295f093 in _PyCFunction_FastCallKeywords () from /usr/lib64/libpython3.7m.so.1.0
 #42 0x00007f7852982a13 in ?? () from /usr/lib64/libpython3.7m.so.1.0
 #43 0x00007f78529b5542 in _PyEval_EvalFrameDefault () from /usr/lib64/libpython3.7m.so.1.0
 #44 0x00007f7852964421 in _PyEval_EvalCodeWithName () from /usr/lib64/libpython3.7m.so.1.0
 #45 0x00007f7852965279 in PyEval_EvalCodeEx () from /usr/lib64/libpython3.7m.so.1.0
 #46 0x00007f785296529b in PyEval_EvalCode () from /usr/lib64/libpython3.7m.so.1.0
 #47 0x00007f7852a2c063 in ?? () from /usr/lib64/libpython3.7m.so.1.0
 #48 0x00007f7852a2fc17 in PyRun_FileExFlags () from /usr/lib64/libpython3.7m.so.1.0
 #49 0x00007f7852a35e2a in PyRun_SimpleFileExFlags () from /usr/lib64/libpython3.7m.so.1.0
 #50 0x00007f7852a37e6c in ?? () from /usr/lib64/libpython3.7m.so.1.0
 #51 0x00007f7852a3801c in _Py_UnixMain () from /usr/lib64/libpython3.7m.so.1.0
 #52 0x00007f7852ba1bcb in __libc_start_main () from /lib64/libc.so.6
 #53 0x00005606af97108a in _start ()
 [Inferior 1 (process 30156) detached]

I hope this means more to me than to you but I have tried this on all previous openSUSE versions with earlier hplip installations and even with the Tumblewed version it still does not work so I revert to the 'manual' method which works but not alas for the Scanner. I should add that the hp-setup works fine with all the other HP printers I have here and I should also add that the HP firmware is as up-to-date as I can find from HP.

**Budgie2** · 09-Sep-2019, 08:34

Originally Posted by hcvv

Thanks. I just asked because to me that is the most obvious thing to do and you did not mention it.

And your further help is?

**hcvv** · 09-Sep-2019, 08:42

Originally Posted by Budgie2

but for the last three or four updates there has been an update button.

.

???
AFAIK, zypper dup is the ONLY way to do it.

**Knurpht** · 09-Sep-2019, 09:37

Originally Posted by hcvv

???
AFAIK, zypper dup is the ONLY way to do it.

Both the plasmoid pk-updater and the GNOME pk-indicator now support 'zypper dup'. Tested the plasma one a couple of times ( who cares, I can rollback btrfs if it doesn't work ), comparing results from pk-updater with dup ( after a rollback ), and it sort of works. Yet, where zypper reports 'These packages will not be updated' for f.e. packages that are being used from Packman, both applets display those as updates available after the dup session. But, the real danger, i.e. partial TW updates is gone.