Looks like something got updated on me and I don’t see anything informative in /var/log/cups/error_log.
It is filled with messages about bad driver information in samsung files. Not useful with an HP printer.
Any diagnostic suggestions, anyone, please?
On 01/11/2013 11:36 PM, bkorb wrote:
> filled with messages about bad driver information in samsung
> files.
based on the sparse info provided: i’d next try to install the correct
HP driver.
before posting again please try to imagine what other might help us
help…maybe review this for hints: http://tinyurl.com/anel
I have been updating the printing apps from the Printing Repository to fix hplip problems. You failed to mention 1) openSUSE Version or 2) Desktop Used so I shall assume openSUSE 12.2 and KDE. For these do this:
To fully upgrade, I would do the following tasks for openSUSE 12.2 using KDE:
Thank You,
OpenSuSE 12.2 – looking at repo now. Thanks. Yep. The priorities are all 99 and that one is about #8.
Too obvious. It has been working for several months. I am certain it relates to having done an “Online Update”.
I do not need a primer on how to ask a question, I need some information about what information someone might find helpful.
I could tar up the stuff in /etc/cups* and /var/log/cups, but there’s bound to be too much, too. Does this help?
$ lpinfo -vnetwork socket
network ipps
network https
network ipp
direct pipe
network http
direct hp
network lpd
network smb
network beh
direct hpfax
$ sr zypper repos
# | Alias | Name | Enabled | Refresh
---+---------------------------+------------------------------------+---------+--------
1 | Packman Repository | Packman Repository | Yes | Yes
2 | google-chrome | google-chrome | Yes | Yes
3 | google-talkplugin | google-talkplugin | Yes | Yes
4 | libdvdcss | DVD Repository | Yes | No
5 | libdvdcss repository | libdvdcss repository | Yes | Yes
6 | openSUSE-12.2-1.6 | openSUSE-12.2-1.6 | No | No
7 | packman | Packman repository (openSUSE_12.2) | Yes | No
8 | repo-debug | openSUSE-12.2-Debug | No | Yes
9 | repo-debug-update | openSUSE-12.2-Update-Debug | No | Yes
10 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No | Yes
11 | repo-non-oss | openSUSE-12.2-Non-Oss | Yes | Yes
12 | repo-oss | openSUSE-12.2-Oss | Yes | Yes
13 | repo-source | openSUSE-12.2-Source | Yes | Yes
14 | repo-update | openSUSE-12.2-Update | Yes | Yes
15 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss | Yes | Yes
I’ve added the printer repo now, so now to test it…
No updated packages.
$ rpm -q -a|egrep -i 'cups|gutenprint'python-cups-1.9.61-2.1.2.x86_64
cups-libs-1.5.3-2.4.1.x86_64
gutenprint-5.2.7-16.1.2.x86_64
cups-libs-32bit-1.5.3-2.4.1.x86_64
cups-devel-1.5.3-2.4.1.x86_64
cups-1.5.3-2.4.1.x86_64
cups-pk-helper-0.2.2-2.1.2.x86_64
cups-client-1.5.3-2.4.1.x86_64
cups-backends-1.0-271.1.1.x86_64
python-cupshelpers-1.3.9-2.2.1.noarch
> I am certain it relates to having done an “Online Update”.
then back out of the offending update, and log the bug against it…
Thank you. I surely do wish I knew which one it was. There were several pages of them the other day and I let 'em rip while I had dinner. Were I to know which one it was, I surely would file a bug report. But I neither know which one nor know exactly how to tell.
You did not say which desktop you are using. In KDE, if you follow my instructions, it gets updated. Read them again, please.
Thank You,
I’m sorry. I did omit that. Yes, it is KDE. I use YaST for GUI and zyupper for command line updates. Your instructions added a new printing repo, but after adding the repo, selecting “Online Update” did not pull any new drivers or other rpms.
$ zypper repos
# | Alias | Name | Enabled | Refresh
---+---------------------------+------------------------------------+---------+--------
1 | Packman Repository | Packman Repository | Yes | Yes
2 | Printing_Repo | Printing Repo | Yes | Yes
3 | google-chrome | google-chrome | Yes | Yes
4 | google-talkplugin | google-talkplugin | Yes | Yes
5 | libdvdcss | DVD Repository | Yes | No
6 | libdvdcss repository | libdvdcss repository | Yes | Yes
7 | openSUSE-12.2-1.6 | openSUSE-12.2-1.6 | No | No
8 | packman | Packman repository (openSUSE_12.2) | Yes | No
9 | repo-debug | openSUSE-12.2-Debug | No | Yes
10 | repo-debug-update | openSUSE-12.2-Update-Debug | No | Yes
11 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No | Yes
12 | repo-non-oss | openSUSE-12.2-Non-Oss | Yes | Yes
13 | repo-oss | openSUSE-12.2-Oss | Yes | Yes
14 | repo-source | openSUSE-12.2-Source | Yes | Yes
15 | repo-update | openSUSE-12.2-Update | Yes | Yes
16 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss | Yes | Yes
I just noticed that the second packman (#8) was not auto refreshing. I changed that, did a refresh and tried the Online Update again. Still nothing new.
E [11/Jan/2013:14:23:14 -0800] [Job 98] Stopping unresponsive job!
E [11/Jan/2013:14:28:25 -0800] [Job 52] Unable to queue job for destination "HP-LaserJet-Professional-M1217nfw-MFP-Fax-3"!
E [11/Jan/2013:15:06:56 -0800] [Job 52] Files have gone away!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 5!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 6!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 7!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 8!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 9!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 10!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 11!
E [11/Jan/2013:15:06:56 -0800] Missing <Job #> directive on line 12!
E [11/Jan/2013:15:28:00 -0800] [Job 101] Stopping unresponsive job!
E [11/Jan/2013:15:57:17 -0800] Unable to bind socket for address [v1.::1]:631 - Address already in use.
E [11/Jan/2013:15:57:17 -0800] Unable to bind socket for address 127.0.0.1:631 - Address already in use.
E [11/Jan/2013:16:04:28 -0800] [Job 101] Stopping unresponsive job!
From the CUPS admin page. Looks like I may have been trying to login via two sessions at 15:57:17. I surely have no idea what the “Missing <Job #>” stuff is about. The “stopping unresponsive job” come from my persistent attempts to print something.
Another forum:
Please attach your /etc/cups/cupsd.conf
Does it help here?
$ cat /etc/cups/cupsd.conf
LogLevel 2
SystemGroup dev sys root
#Port 631
Listen *:631
Listen localhost:631
Listen /var/run/cups/cups.sock
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseRemoteProtocols CUPS
BrowseLocalProtocols CUPS
BrowseAddress @LOCAL
DefaultAuthType Basic
WebInterface Yes
<Location />
Allow @LOCAL
Order allow,deny
Allow 127.0.0.2
</Location>
<Location /admin>
Order allow,deny
Allow @LOCAL
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
Order allow,deny
Allow @LOCAL
</Location>
<Policy default>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy authenticated>
JobPrivateAccess default
JobPrivateValues default
SubscriptionPrivateAccess default
SubscriptionPrivateValues default
<Limit Create-Job Print-Job Print-URI Validate-Job>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job Cancel-My-Jobs Close-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After Cancel-Jobs CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy allowallforanybody>
<Limit All>
Order deny,allow
Allow from all
</Limit>
</Policy>
DefaultPolicy default
# 2013-01-11,15:56:02 modify_cupsd_conf Listen localhost
# 2013-01-11,15:56:57 modify_cupsd_conf Allow @LOCAL
# 2013-01-11,15:56:57 modify_cupsd_conf BrowseAddress @LOCAL
# 2013-01-11,15:56:57 modify_cupsd_conf Browsing On
# 2013-01-11,15:56:57 modify_cupsd_conf Listen all
Does it explain the job number messages shown earlier?
Thank you for any help!
Similar issue: https://bugzilla.redhat.com/show_bug.cgi?id=737230
but as noted earlier here: cups-1.5.3-2.4.1.x86_64
That bug report also asked for a few things, but this is now just shooting in the dark:
$ python -c 'import socket;print socket.getaddrinfo("localhost", 631)'
(10, 1, 6, '', ('::1', 631, 0, 0)), (10, 2, 17, '', ('::1', 631, 0, 0)), (10, 3, 0, '', ('::1', 631, 0, 0)), (2, 1, 6, '', ('127.0.0.1', 631)), (2, 2, 17, '', ('127.0.0.1', 631)), (2, 3, 0, '', ('127.0.0.1', 631))]
$ ip addr show dev lo
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
$ egrep -v $'^ ]*(#|$)' /etc/hosts
127.0.0.1 localhost
192.168.10.9 goflex
192.168.1.254 modem
192.168.10.1 router
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
I can print to my HP M1217 printer, but I have to use the ethernet connection.
I can print to it with USB, but only on my Mac. Therefore, the USB port
still works, but the HP Linux drivers are misconfigured or broken.
It was the recent upgrade that did in my USB access to the printer.
I have been unable to determine if you have followed my instructions to upgrade hplip from the printing repository or not. If you have posted this info already, then you have my apologies. But humor me and open up a terminal session and type in the command:
rpm --query --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} -> %{VENDOR}
' hplip
And this is what I see:
hplip-3.12.11-62.1-x86_64 -> obs://build.opensuse.org/Printing
Lets us see what you get. Further, it is my opinion, that using the network port on a HP printer is superior to using a direct USB connection anytime there are two or more PC’s that need to use a single printer. I only use HP printers and using the network connection is the way to go.
Thank You,
# rpm --query --queryformat '%{NAME}-%{VERSION}-%{RELEASE}-%{ARCH} -> %{VENDOR}
' hplip
hplip-3.12.4-3.1.2-x86_64 -> openSUSE
I followed your instructions well enough that I have that additional repository in my repo list, but when I told YaST to update, nothing new was pulled. As you see, my hplip is 3.12.4 not 3.12.11. Also, before my last post, I deleted every printer and started over. I didn’t mention it, but the “configure printer” task from the YaST control center could not see the thing via the USB port, though lsusb sees it:
$ lsusb
Bus 002 Device 002: ID 03f0:0e2a Hewlett-Packard
WRT multiple computers, my wife insists on using a color ink jet printer, even for black and white printing, so it’s all mine.
Well you have at least missed one step, read through it again:
To fully upgrade, I would do the following tasks for openSUSE 12.2 using KDE:
1. Go to **YaST** (Enter Root Password) / **Software** / **Software Repository** and specify the URL addition of the Packman Repository "http://packman.inode.at/suse/openSUSE_12.2/" excluding the quotes **if not already done**.
2. Go to** YaST** (Enter Root Password) / **Software** / **Software Repository** and specify the URL addition of the Packman Repository "http://download.opensuse.org/repositories/Printing/openSUSE_12.2/" excluding the quotes, **this fixes the printer issue**.
3. Go to** YaST** (Enter Root Password) /** Software** / **Software Management** and select **Options** and check **Allow Vendor Change**.
4. Again, still in **Software Management** select **Package** / **All Packages **/ ** Update if newer version available** and press the **Accept** button on the bottom right.
I am thinking you missed step 3. Consider that I have included a step-by-step procedure that you only need to follow exactly and it should work. Now we all had to start somewhere, not knowing much about Linux and no one knows it all, that is for sure. But we are trying very hard to help you here. If the problem really matters to you, then please follow ALL of the instructions.
Thank You,
To be completely clear, I do, indeed, appreciate your help very much! I am trying. I am also attempting to be helpful 
From the Software Repositories YaST application:
Printing Repo
URL: http://download.opensuse.org/repositories/Printing/openSUSE_12.2
Category: YUM
Bringing back up the Software Management, the option menu has “Allow vendor change” as you had asked and as I had done last night.
It was step 4 that I apparently cheated on: I usually use the “Online Update” application to do that and confusingly thought it sufficient. Apparently not: ``130 packages will be updated’’. Oh, dear. Time for my coffee anyway.
Oh, dear, oh, dear. I hate conflicts.
libavfilter2-0.11.1-1.4 requires libswresample0 0.11.1 “but there ain’t no such-a-thing”
k3b-codecs-2.0.2-15.86. requires k3b = 2.0.2-15.86 “but we can’t”
Merde. I hope de-installing libavfilter2 and skipping the k3b codecs doesn’t break anything…
P.S. also for clarity: when I first got the printer a couple of months ago, hplip found it on the usb port just fine. It is only now…
For libavfilter2-0.11.1-1.4, just do not install it. I find that I have libavfilter1 & libavfilter3 from Packman. As for k3b,basically you are switching all of the k3b files to Packman. k3b comes with openSUSE, but not k3b-codecs, so to install k3b-codecs, you must downgrade the k3b version to what you get from Packman. The version number changes are only slight and not sure why openSUSE and Packman don’t agree but it does not matter, get them all from Packman. In general, here is what I have to say about package problems:
To avoid package problems, the most important thing to do is to: NEVER
ignore a dependency, even if YaST/zypper/updater gives you such an option!
In general, never switch to an >inferior< architecture and the solution is
most often to just switch Vendor to the >Packman< repository. So changing
the vendor is OK, but >ignoring< dependencies is never a very good idea!
As for hplip, it seems to have developed several problems fixed by the version in the printing repository. You just need to switch over too it. As for any question asked by YaST, just copy the text and post the question it asks here. We have no time limit and so ask as many questions as you wish.
Thank You,