public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <dalek1967@bellsouth.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] CUPS problem
Date: Sun, 06 Jan 2008 18:24:00 -0600	[thread overview]
Message-ID: <47817120.5020506@bellsouth.net> (raw)
In-Reply-To: <7bef1f890801061600wf34072fr91befa42c963f1dd@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1395 bytes --]

Alan E. Davis wrote:
> I have installed two or three times, deleted /etc/cups and reinstalled
> the printer.  It showed up as an HPLIP device when installing, w/ CUPS
> and/or the kde printer utility.   NOtably the utility OR the
> localhost:631 interface did not show any option for a USB printer.
> The address that ended up being used was a usb:<printername>.  When I
> get gentoo booted up I'll look at it again.  For now, I have to print,
> so I've installed Ubuntu on another partition.  Printing works fine
> there, so that's a start.
>
> Thank you,
>
> Alan
>
> On Jan 7, 2008 2:48 AM, Mick <michaelkintzios@gmail.com> wrote:
>   
>> On Sunday 06 January 2008, Dale wrote:
>>     
>>> Alan E. Davis wrote:
>>>       
>>>> Any ideas?
>>>>         
>>> I ran into something similar to the a while back and I had to un-merge
>>> cups, delete the config files, then reemerge cups and reconfigure my
>>> printer.   Keep in mind that when you unmerge something, the config
>>> files remain in /etc unchanged.
>>>       
>> Assuming that you have set the correct device in the GUI for your printer,
>> then the most likely error is that your have not provided the correct path
>> for it.  Show us what you have defined the path as in case we can help.
>> --
>> Regards,
>> Mick
>>
>>     
>
>
>
>   

They recently changed it over to hplip.  Is that installed on your system? 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 2118 bytes --]

  reply	other threads:[~2008-01-07  0:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06  3:27 [gentoo-user] CUPS problem Alan E. Davis
2008-01-06  8:00 ` Dale
2008-01-06 16:48   ` Mick
2008-01-07  0:00     ` Alan E. Davis
2008-01-07  0:24       ` Dale [this message]
2008-01-07  0:44         ` Alan E. Davis
2008-01-07  1:02           ` Dale
2008-01-07  5:06         ` Randy Barlow
2008-01-07  5:25           ` Dale
2008-01-07  5:32             ` Randy Barlow
2008-01-07  5:53               ` Dale
2008-01-08  9:56                 ` Mick
2008-01-08 23:43                   ` Alan E. Davis
2008-01-09  5:51                     ` Randy Barlow
2008-01-09 11:01                       ` Alan E. Davis
2008-01-09 13:00                     ` Mick
2008-01-09 13:09                       ` Alan E. Davis
2008-01-09 14:11                         ` Alan McKinnon
  -- strict thread matches above, loose matches on Subject: below --
2007-12-07 19:45 [gentoo-user] cups problem Roger Mason
2007-12-07 19:57 ` Billy Holmes
2007-12-07 20:42   ` Roger Mason
2007-12-07 20:53     ` Billy Holmes
2007-12-07 21:56 ` Randy Barlow
2007-12-08 12:23   ` Roger Mason
     [not found] <200609260955.20095.gentoo@appjaws.plus.com>
2006-09-26 13:58 ` Boyd Stephen Smith Jr.
2006-06-25  0:28 Michael W. Holdeman
2006-06-25  1:21 ` darren kirby
2006-06-25  2:01   ` Michael W. Holdeman
2006-06-25  3:19     ` darren kirby

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47817120.5020506@bellsouth.net \
    --to=dalek1967@bellsouth.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox