Prev: Adware 911 - Run Linux and never be infested again! - www.Adware911.com
Next: util-linux-ng slackbuild clarification
From: Selex on 11 Apr 2008 02:07
Everytime I turn around something is being messed with in this program,
and I keep having to mess with it to get my printer working.

I keep getting an error when rc.hplip runs that it cannot connect to the
dbus messenger, and am I running it in root.

File is as such
-rwxr-xr-x 1 root root 4777 2007-06-10 01:14 rc.hplip
-rwxr-xr-x 1 root root 1560 2008-03-15 02:26 rc.messagebus
So both are executable and should be running when it goes through the
scripts.

When I run the script after I've logged in as root, I get no such error,
but I still cannot not print. I installed dbus 1.1.20, dbus-
python-0.82.4, pycairo 1.4.12, pyobject 2.14.1, and pygtk 2.12.1 to get
hplip to run, and am I missing a library? When I installed dbus it did
not copy the rc.message.new file into /etc/rc.d, so I manually did it,
and made it the rc.message script.

Selex
From: Keith Keller on 11 Apr 2008 02:39
On 2008-04-11, Selex <bob(a)someguy.com> wrote:
> Everytime I turn around something is being messed with in this program,
> and I keep having to mess with it to get my printer working.

Maybe you should just get a printer that doesn't require hplip. You can
probably find a LaserJet III on eBay or something.

--keith



--
kkeller-usenet(a)wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://www.therockgarden.ca/aolsfaq.txt
see X- headers for PGP signature information

From: Manuel Reimer on 11 Apr 2008 03:36
Selex wrote:
> I keep getting an error when rc.hplip runs that it cannot connect to the
> dbus messenger, and am I running it in root.

Check as root, if messagebus runs after you log in (pgrep dbus).

Also add this line (pgrep dbus) to your rc.hplip script to see if
messagebus is running when rc.hplip is executed. Maybe a simple "sleep"
on top of "rc.hplip" will fix this one.

> When I run the script after I've logged in as root, I get no such error,
> but I still cannot not print.

the hplip daemon doesn't have anything to do with your printing. You
have to enable and setup CUPS (rc.cupsd) first. Make the rc-script
executable and run

/etc/rc.d/rc.cupsd start

Now run

links localhost:631

to access the CUPS configuration. Go over to "Administration" and choose
"New printer".

CU

Manuel

From: Manuel Reimer on 11 Apr 2008 03:37
Keith Keller wrote:
> Maybe you should just get a printer that doesn't require hplip. You can
> probably find a LaserJet III on eBay or something.

None of the HP printers require the hplip-daemon to be running just to
print something out. The primary part of hplip are CUPS drivers, which
have to be set up just like any other printer driver.

CU

Manuel

From: Robby Workman on 11 Apr 2008 23:53
On 2008-04-11, Selex <bob(a)someguy.com> wrote:
> Everytime I turn around something is being messed with in this program,
> and I keep having to mess with it to get my printer working.
>
> I keep getting an error when rc.hplip runs that it cannot connect to the
> dbus messenger, and am I running it in root.
>
> File is as such
> -rwxr-xr-x 1 root root 4777 2007-06-10 01:14 rc.hplip
> -rwxr-xr-x 1 root root 1560 2008-03-15 02:26 rc.messagebus
> So both are executable and should be running when it goes through the
> scripts.
>
> When I run the script after I've logged in as root, I get no such error,
> but I still cannot not print. I installed dbus 1.1.20, dbus-
> python-0.82.4, pycairo 1.4.12, pyobject 2.14.1, and pygtk 2.12.1 to get
> hplip to run, and am I missing a library? When I installed dbus it did
> not copy the rc.message.new file into /etc/rc.d, so I manually did it,
> and made it the rc.message script.


Are you running Slackware 12.0 or Slackware -current?

If you're on 12.0, then you've screwed up, because the hplip version
shipped with it didn't use dbus at all.

If you're on -current, then you've screwed up, because the hplip version
that ships with it doesn't include an rc.hplip init script.

If you've installed a "new and shiny version of hplip" from LinuxPackages.net
or elsewhere, then you might have screwed up - check with the packager and
see if he/she has any ideas.

Also, if installing the dbus package didn't install an rc.messagebus script,
then you've screwed up.

In essence, I'd bet money that you've screwed up. Give more details on
exactly how you did it, and more help can perhaps be given.

-RW
 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Adware 911 - Run Linux and never be infested again! - www.Adware911.com
Next: util-linux-ng slackbuild clarification