Solved (SOLVED) Printer queue won’t clear

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

Ro berto

Regular Contributor
Hello all,

I'm still having issues with my printer which is connected to the router through USB (previous post), so I decided to format my PC and reinstall Windows from scratch to see if it was a Windows problem.

Unfortunately I'm still having issues with the printer queue.

When the queue is empty and I send something to print, it's printed without issue.

The problem is that the queue won't clear and if later I want to print something, the printer won't print it because there is still a pending document in the queue. (see attached pic)
Capture.PNG


Don't know if this will help or if it is related, but in the past when the printer would not respond, I would send the "service restart_u2ec" command that would fix it (see here), and now I'm getting this "u2ec: Error unlocking 29: 9 Bad file descriptor" errors in the system log:

Code:
Jul 30 16:11:41 kernel: usb 3-1.4: new high-speed USB device number 12 using ehci-platform
Jul 30 16:11:41 kernel: usblp 3-1.4:1.1: usblp0: USB Bidirectional printer dev 12 if 1 alt 0 proto 2 vid 0x03F0 pid 0x8911
Jul 30 16:22:49 dropbear[20573]: Child connection from 192.168.1.10:45354
Jul 30 16:22:49 dropbear[20573]: Password auth succeeded for 'rhrl' from 192.168.1.10:45354
Jul 30 16:22:49 rc_service: service 20575:notify_rc restart_u2ec
Jul 30 16:22:49 custom_script: Running /jffs/scripts/service-event (args: restart u2ec)
Jul 30 16:22:50 dropbear[20573]: Exit (rhrl) from <192.168.1.10:45354>: Exited normally
Jul 30 16:23:19 u2ec: Error unlocking 29: 9 Bad file descriptor
Jul 30 16:23:42 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:23:58 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:24:59 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:28:14 dropbear[21232]: Child connection from 192.168.1.10:45380
Jul 30 16:28:14 dropbear[21232]: Password auth succeeded for 'rhrl' from 192.168.1.10:45380
Jul 30 16:28:14 rc_service: service 21235:notify_rc restart_u2ec
Jul 30 16:28:14 custom_script: Running /jffs/scripts/service-event (args: restart u2ec)
Jul 30 16:28:15 dropbear[21232]: Exit (rhrl) from <192.168.1.10:45380>: Exited normally
Jul 30 16:29:24 u2ec: Error unlocking 29: 9 Bad file descriptor
Jul 30 16:29:34 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:31:11 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:31:44 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:33:57 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:34:57 u2ec: Error unlocking 34: 9 Bad file descriptor
Jul 30 16:35:51 u2ec: Error unlocking 34: 9 Bad file descriptor

Has anyone experienced this similar problem?

Any help is more than appreciated.

Router: RT-AC86U running Firmware Version: 384.18
 

Ro berto

Regular Contributor
How do I check that? I think it's a USB virtual port (see following pic)

Capture.PNG


I didn't do the TCP/IP thing, I went to ASUS webpage (this one) and downloaded this file.

That's how I did it in the past and I didn't have the current issue, don't know if it is related to the latest firmware :/

Thanks
 

itpp20

Regular Contributor
Ah, I never use such connections, always (tcpip) raw or lpr, try lpr (and enable lpr byte count). That has always worked, bugged firmware or not ;)
 

Ro berto

Regular Contributor
Apparently the drivers from Windows are not the best, after installing HP's drivers, the queue clears :)

Sorry Eric again for doubting of the marvelous Merlin firmware, I don't deserve this firmware, I will slash my back with a belt and report back.
 
Last edited:

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top