[sorry my mistake not copying the support list the first time]
On Mon, Jan 04, 2021 at 08:35:39PM -0500, Doug McGarrett wrote:
> On 1/4/21 5:35 PM, Daniel Morris wrote:
> > Hi Doug,
> > On Mon, Jan 04, 2021 at 04:00:42PM -0500, Doug McGarrett wrote:
> > > Have two printers--HP and Epson--which were both working. Was looking at
> > > a pdf in Okular, and tried to print it using the little printer icon in the
> > > panel. It
> > > showed four items in the print queue, which I can't account for, but I think
> > > I got rid of them with the options available. Would not print. Tried the
> > > other
> > > printer, same routine, won't print. Now tried printing with each printer
> > > from
> > > a text in Kate. Neither printer will print. No error message. The Epson has
> > > a
> > > scanner function, and that still works.
> > Maybe there are jobs stuck in the queues or something's gone wobbly with
> > a filter.
> > $ lpq -a
> > will show all the print queues and maybe give you a hint
> > and as it sounds like you've already found you can cancel individual
> > and bulk jobs using the 'cancel' command
> > But the easiest way is usually to connect to your own machine and look
> > at what CUPS thinks is going on. Just launch a browser and connect to
> > port 631 on your machine by entering this into the address bar:
> > localhost:631
> > You might be prompted to login with the root password to that page.
> > Usually you can navigate at the top of the page to "Printers" and "Jobs"
> > to work out what's going on.
> > I guess you'll probably have two print queues setup, one for the Epson &
> > one for the HP. In the "Printers" tab see what the "Status" field says.
> > If you click on the name of the print queue, you'll have two drop-downs
> > for "Maintenance" & "Administration". Sometimes you might just need to
> > "Resume" a printer (under Maintenance) if it had a temporary fault, such
> > as out of paper, jammed or a door open etc. I think the default config
> > waits for an admin to intervene if there's a fault - logical in a
> > big/corporate setup but quite irritating when the printer is sat at the
> > other end of your desk and you can see it ran out of paper and now have
> > to launch a browser and login and tell CUPS to tell the printer to
> > resume.
> > Resist making changes under Administration at this stage, if both
> > printers worked before then it's a bit odd that the two have stopped
> > together, but not unknown (typically file permissions or broken
> > filters). If your printers are hooked up via ethernet and your
> > network/router has re-assigned their addresses (DHCP) then that can
> > cause this kind of breakage. As can forgetting that you (or someone
> > else) unplugged/re-routed the USB/Ethernet cables when tidying the desk
> > before Christmas.
> > Daniel
> In cups, "Resume Printer" Unable to do maintenance command: Forbidden
> Cups -Show active jobs--none listed.
So was the status of the Printer "paused" to begin with? That error
message seems to suggest you haven't logged into CUPS (via the broswer)
with sufficient/root privileges to allow a resume.
If not paused, what happens if you try to Pause the printer from the
Do the Driver and Connection details under the Printer tab look
sensible? eg, in the browser (localhost:631) I click Printers from
heading, then click on the Queue Name Photosmart_5520 to see the
following (below the Maintenance & Administration dropdown buttons):
Description: HP Photosmart 5520
Location: corner of lounge
Driver: HP Photosmart 5520 Series hpijs, 3.13.10 (color, 2-sided printing)
Defaults: job-sheets=none, none media=iso_a4_210x297mm sides=one-sided
> The jobs that wouldn't print are shown as cancelled. One of them says
> "Filter failed" but the others don't. (Just looking at one printer at that
> Seems to be the same for all four listings. ( Each printer is, and has been,
> listed twice with slightly different settings--both used to work, at either
> I got the printers to work from a different computer, so it's OK on
> that end, apparently. That tells me that the router has not reassigned
> DHCP. (Both printers have fixed addresses.)
> I'm kind of snowed at this point. --doug
Don't despair, now you can dig in.
Do you have enough disk space where the filter and print queue will be
$ df -h
Check your journal for cups related messages:
$ journalctl -u cups
There's also the classic error_log, access_log & page_log files under
$ less /var/log/cups/error_log
(or viewable from the browser under Administration->Server section)
Using those logs can you narrow down when the printing stopped working?
Has a system change or update caused the breakage? Using rpm to see
which packages have been installed or updated might be helpful:
$ rpm -qa --last |less
Hopefully you can work out what's gone wrong and then know what to fix.
I'm trying a bare metal install of Tumbleweed (snapshot 20021218...but I've had the same result with several predecessor snapshots) on an HP Envy x360 (15z-ds100) with the "Intel Wi-FI 6 AX 200 (2x2) and Bluetooth 5 combo." When I get to the "Network Settings" page, no hardware is detected.
I could install without networking and tackle the issue later, but thought I'd seek advice here first (maybe there's a fix that will help others in the future).
My troubleshooting thus far (which may or may not be helpful) consists of switching over to a terminal (ctrl+alt F1), removing the iwlwifi module ("rmmod iwlwifi") and adding it back via "modprobe iwlwifi". That last command produces the following output:
[ 1544.250127] Intel(R) Wireless WiFi driver for Linux
[ 1544.259285] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2
[ 1544.259308] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-55.ucode failed with error -2
[ 1544.259325] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-54.ucode failed with error -2
[ 1544.259342] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-53.ucode failed with error -2
[ 1544.259357] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-52.ucode failed with error -2
[ 1544.259374] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-51.ucode failed with error -2
[ 1544.259390] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-50.ucode failed with error -2
[ 1544.259406] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-49.ucode failed with error -2
[ 1544.259422] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-48.ucode failed with error -2
[ 1544.259439] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
[ 1544.259456] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-46.ucode failed with error -2
[ 1544.259472] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-45.ucode failed with error -2
[ 1544.259489] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-44.ucode failed with error -2
[ 1544.259510] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-43.ucode failed with error -2
[ 1544.259528] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-42.ucode failed with error -2
[ 1544.259545] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-41.ucode failed with error -2
[ 1544.259561] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-40.ucode failed with error -2
[ 1544.259574] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-39.ucode failed with error -2
[ 1544.259575] iwlwifi 0000:02:00.0: no suitable firmware found!
[ 1544.259576] iwlwifi 0000:02:00.0: minimum version required: iwlwifi-cc-a0-39
[ 1544.259577] iwlwifi 0000:02:00.0: maximum version supported: iwlwifi-cc-a0-56
[ 1544.259578] iwlwifi 0000:02:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
I've attempted to copy additional firmware into /lib/firmware, but that location is read-only (and not easily made read+write from my experiments).
Should I just proceed with the install and address the network issue later (it may not even be there after install) or is there more troubleshooting you can suggest (or other options). FYI, I don't have a USB-to-RJ45 adapter at the moment, so I can't use wired networking.
Have two printers--HP and Epson--which were both working. Was looking at
a pdf in Okular, and tried to print it using the little printer icon in
the panel. It
showed four items in the print queue, which I can't account for, but I think
I got rid of them with the options available. Would not print. Tried the
printer, same routine, won't print. Now tried printing with each printer
a text in Kate. Neither printer will print. No error message. The Epson
scanner function, and that still works.
( I don't know why there is a printer icon in the panel, if it's not
going to print.)
Here is an nmap report on the LaserJet:
doug@linux1:~> nmap --reason 192.168.1.29
Starting Nmap 7.80 ( https://nmap.org ) at 2021-01-04 15:55 EST
Nmap scan report for 192.168.1.29
Host is up, received syn-ack (0.0066s latency).
Not shown: 992 closed ports
Reason: 992 conn-refused
PORT STATE SERVICE REASON
21/tcp open ftp syn-ack
23/tcp open telnet syn-ack
80/tcp open http syn-ack
443/tcp open https syn-ack
515/tcp open printer syn-ack
631/tcp open ipp syn-ack
8080/tcp open http-proxy syn-ack
9100/tcp open jetdirect syn-ack
A similar output for the Epson, but I already know that's on line as a
I don't know how to troubleshoot or fix this. Please advise.
I get a considerable number of sshd coredumps per day on Tumbleweed,
currently 20210101. there is no system crash or other notice and does not
seem to affect other ssh connections (I maintain quite a few to share
12:13 crash: ~ # coredumpctl info 24778 -o sshd.coredump.txt
PID: 24778 (sshd)
UID: 1000 (paka)
GID: 100 (users)
Signal: 11 (SEGV)
Timestamp: Sun 2021-01-03 10:49:57 EST (1h 23min ago)
Command Line: sshd: paka@notty
Control Group: /user.slice/user-1000.slice/session-27.scope
Owner UID: 1000 (paka)
Boot ID: 6daaababe19d42638b365590e4f26aee
Machine ID: 3384cbc37a574dcc99445aa25cd2db04
Message: Process 24778 (sshd) of user 1000 dumped core.
Stack trace of thread 24778:
#0 0x000055d628693563 cipher_free (sshd + 0x4e563)
#1 0x000055d628695b67 ssh_packet_close_internal (sshd + 0x50b67)
#2 0x000055d628655cbf main (sshd + 0x10cbf)
#3 0x00007f2cae063152 __libc_start_main (libc.so.6 + 0x28152)
#4 0x000055d62865624e _start (sshd + 0x1124e)
is this a known issue?
I see nothing similar lately on bugzilla
how would I trouble-shoot?
should I open a bug report?
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode