[plug] Printing problem RH6

Desire'e dynamix at wanet.com.au
Mon Jul 19 12:16:13 WST 1999


just out of insterest have you had your epson working on rh6 at all..
( i had this problem with COL22 ..apparently rh6 has the same one ...there is a
fix)  if youve had it working i cant help but it if it wasnt  maybe i can point
you in the right direction
regardz Desiree

On Mon, 19 Jul 1999, you wrote:
> Hi all
> 
> I have only recently being having a play with vmware a little behind you
> all I guess.
> Managed to completely crash linux and for some reason this has affected
> the print set-up.
> Must confess to running vm as su root trying to figure out why I could
> not print from vm as a user.
> 
> Ironically now I can print from vmware to my printer okay but not from
> linux even when vm's not running.
> 
> I've tried logging output of the lpr command when run as a user but I
> get no output
> nothing in the print cue either.
> 
> If I run lpr file tail -f as su root here's what I get.
> root at localhost bin]# lpr /home/mark/WordPerfect/Melwire2 | tail -f
> /var/log/mes
> sages
> Jul 19 06:49:14 localhost pppd[912]: local  IP address 202.61.192.149
> Jul 19 06:49:14 localhost pppd[912]: remote IP address 202.61.192.15
> Jul 19 06:49:32 localhost inetd[962]: execv /usr/sbin/in.identd: No such
> file or
>  directory
> Jul 19 06:56:54 localhost kernel: parport0: PC-style at 0x378
> [SPP,ECP,ECPEPP,EC
> PPS2] 
> Jul 19 06:56:54 localhost kernel: parport0: detected irq 7; use procfs
> to enable
>  interrupt-driven operation. 
> Jul 19 06:56:54 localhost kernel: parport0: Printer, EPSON Stylus COLOR
> 800 
> Jul 19 06:56:54 localhost kernel: lp0: using parport0 (polling). 
> Jul 19 06:58:40 localhost PAM_pwdb[1031]: 1 authentication failure;
> mark(uid=500
> ) -> root for su service
> Jul 19 06:58:47 localhost PAM_pwdb[1032]: (su) session opened for user
> root by m
> ark(uid=500)
> Jul 19 06:59:32 localhost inetd[1067]: execv /usr/sbin/in.identd: No
> such file o
> r directory
> 
> Have tried re installing  RH print filters and other bits and pieces. 
> lpd daemon is definitely running. I did not fiddle with any of the
> permissions for lpr or spool directories not deliberately any way.
> 
> Whats going on? I could do with and appreciate some help.
> 
> 
> Mark


More information about the plug mailing list