manage printing, not able to connect to localhost

[mrstordal]

I am running Salix 13.37 Ratpoison Edition.
When go through the Ratmenu and to "Manage Printing", Vimprobable gives me the error message "can not connect to localhost", and the cups interface does not open. What can be wrong? It has worked before, allowing me to install a couple of printers.

Grateful for any help on this one!

[mimosa]

Please post the contents of .config/vimprobable/vimprobablerc and the output of

Code: Select all

#ifconfig -a

Can you think of anything you might have done to your networking setup since the last time you added a printer?

For good measure, what does ratmenu's file say under that entry? I'm not running the ratpoison edition at the moment (awaiting 14.0) and I can't remember where the file lives, but I hope my question is clear.

[mrstordal]

Thanks!

I don't seem to have a configuration file for Vimprobable...
But this is the other output:

eth0 Link encap:Ethernet HWaddr 00:1f:c6:ed:c4:8a
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Base address:0xe400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:150 errors:0 dropped:0 overruns:0 frame:0
TX packets:150 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10488 (10.2 KiB) TX bytes:10488 (10.2 KiB)

wlan0 Link encap:Ethernet HWaddr 00:15:af:45:a3:2e
inet addr:192.168.101.107 Bcast:192.168.101.255 Mask:255.255.255.0
inet6 addr: fe80::215:afff:fe45:a32e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:65488 errors:0 dropped:4 overruns:0 frame:0
TX packets:31522 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:83786624 (79.9 MiB) TX bytes:2911915 (2.7 MiB)


#!/bin/sh

ratmenu -font \
-xos4-terminus-medium-r-normal--12-120-72-72-c-60-iso8859-1 \
-back ~/.ratmenu/main.sh \
"Dotnew" "gksu xterm -e dotnew" \
"Gslapt Package Manager" "gksu gslapt" \
"Htop" "xterm -e htop" \
"Keyboard" "gksu xterm -e keyboardsetup" \
"Manage Printing" "vimprobable2 http://localhost:631/" \
"Mount Manager" "gmountman" \
"Mounted Devices" "ratpoison -c 'echo $(mount)'" \
"Sourcery SlackBuild Manager" "gksu sourcery" \
"System Clock" "gksu xterm -e clocksetup" \
"System Language" "gksu xterm -e localesetup" \
"System Services" "gksu xterm -e servicesetup" \
"Users and Groups" "gksu xterm -e usersetup"

Thank you for looking at it!

[mimosa]

That all looks as though it should work (the ifconfig output here is slightly different, but I'd guess that's to do with 14.0 versus 13.37).

What happens if you try to open

http://localhost:631/

directly in Vimprobable - or if that fails, another broswer?

Also, if you're not reluctant to trash your uptime, it might be worth rebooting just to see if networking untwists its undergarments that way. How is your networking set up - just the default wicd? In which case you might get the same benefit by:

Code: Select all

#service stop wicd
[wait a while]
#service start wicd

[mrstordal]

Again, thank you for helping me out!

I rebooted, and it worked again... and then it quit on me again.
What I tried to do, was printing on a network printer. The printer was reckognized in Libre Office, but I have not yet been able to get a printout. That might be because the printer is a shared printer on a Mac. (?) After I tried, I was back with the same error message. This time I will try to just restart wicd.

[mimosa]

Well, it's a start. i'm afraid I'm stumped as to where to look for a better solution that actually fixes the problem. However, maybe something is set wrong in Wicd's preferences ... or the preferences for the particuar connection (different place). Perhaps you could post these to see if anything outlandish appears (taking care to disguise any information identifying your network).

[mrstordal]

Suddenly it worked... And I got the shared printer working
Which is good, but still leaves me in the dark as to why I could not connect to the cups service, and how often it will happen.
I had to reboot every time, and Vimprobable froze on me the last time, and I needed to do a ctr-t K on it.
Thank you, Mimosa, for sharing in my troubles!