Launchpad has imported 5 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=689790.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-03-22T13:11:23+00:00 G. wrote:

Description of problem:

I plugged my USB printer, clicked the + on the printer box from the
gnome 3 control panel.   It gave me local and network.  Both were blank.

If I used the system-config-printers it found everything no problem, the
network printer and the local USB printer.

I think there's something wrong with how the gnome 3 is detecting the
printers.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/862922/comments/0

------------------------------------------------------------------------
On 2011-03-29T10:42:16+00:00 Tim wrote:

What does 'lpinfo -l -v' say, as root?  Also, how about 'rpm -q control-
center?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/862922/comments/1

------------------------------------------------------------------------
On 2011-03-29T13:09:49+00:00 G. wrote:

[root@liandra ~]# rpm -q control-center
control-center-2.91.92-1.fc15.x86_64

lpinfo -l -v:

Device: uri = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = serial:/dev/ttyS0?baud=115200
        class = serial
        info = Serial Port #1
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = scsi
        class = direct
        info = SCSI Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = lpd
        class = network
        info = LPD/LPR Host or Printer
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = socket
        class = network
        info = AppSocket/HP JetDirect
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = http
        class = network
        info = Internet Printing Protocol (http)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = https
        class = network
        info = Internet Printing Protocol (https)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = cups-pdf:/
        class = file
        info = CUPS-PDF
        make-and-model = Virtual PDF Printer
        device-id = MFG:Generic;MDL:CUPS-PDF Printer;DES:Generic CUPS-PDF 
Printer;CLS:PRINTER;CMD:POSTSCRIPT;
        location = 
Device: uri = hp
        class = direct
        info = HP Printer (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = hpfax
        class = direct
        info = HP Fax (HPLIP)
        make-and-model = Unknown
        device-id = 
        location = 
Device: uri = bjnp
        class = network
        info = Canon network printer
        make-and-model = Unknown
        device-id = 
        location =

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/862922/comments/2

------------------------------------------------------------------------
On 2011-03-29T15:34:01+00:00 Tim wrote:

CUPS can only see the cups-pdf device and serial devices.

Presumably the printer was connected and powered on when you ran lpinfo?
Can you please very that system-config-printer can find the printer?
What device URI does it have?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/862922/comments/3

------------------------------------------------------------------------
On 2012-08-07T17:23:23+00:00 Fedora wrote:

This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control-
center/+bug/862922/comments/8


** Changed in: gnome-control-center (Fedora)
       Status: Unknown => Won't Fix

** Changed in: gnome-control-center (Fedora)
   Importance: Unknown => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/862922

Title:
  GCC fails to detect and load available local and network printers

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/862922/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to