gnome-control-center

GCC fails to detect and load available local and network printers

Bug #862922 reported by Nathanel Titane
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center
New
Undecided
Unassigned
gnome-control-center (Fedora)
Won't Fix
Medium
gnome-control-center (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

Linux Mercury 3.0.0-12-generic-pae #19-Ubuntu SMP Fri Sep 23 23:10:56 UTC 2011 i686 athlon i386 GNU/Linux

Currently running gnome-shell as default DE. I dumped unity.

Trying to detect printers via the gcc printer sub-module loops and stops searching after 30 seconds wether on local or network devices.

using system-config-printer flawlessly queries and install available devices.

Termianl output:

nathanel@Mercury:~$ lpinfo -l -v
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 = beh
        class = network
        info = Backend Error Handler
        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 = ipp
        class = network
        info = Internet Printing Protocol (ipp)
        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 = smb
        class = network
        info = Windows Printer via SAMBA
        make-and-model = Unknown
        device-id =
        location =
Device: uri = parallel:/dev/lp0
        class = direct
        info = LPT #1
        make-and-model = unknown
        device-id =
        location =
Device: uri = cnijnet:/00-1E-8F-8E-78-B0
        class = network
        info = Canon-MX340-series_00-1E-8F-8E-78-B0
        make-and-model = Canon MX340 series
        device-id =
        location =

-----------------------------

Similar bug found on Fedora bug tracker (Bug #689790): https://bugzilla.redhat.com/show_bug.cgi?id=689790

Revision history for this message
In , G. (g.-redhat-bugs) 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.

Revision history for this message
In , Tim (tim-redhat-bugs) wrote :

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

Revision history for this message
In , G. (g.-redhat-bugs) 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 =

Revision history for this message
In , Tim (tim-redhat-bugs) 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?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
Revision history for this message
Nathanel Titane (nathanel.titane) wrote : Re: [Bug 862922] Re: GCC fails to detect and load available local and network printers
Download full text (3.2 KiB)

Will do
On Sep 30, 2011 8:01 AM, "Sebastien Bacher" <email address hidden> wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. The issue you are reporting is an upstream one and it
> would be nice if somebody having it could send the bug to the developers
> of the software by following the instructions at
> https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please
> tell us the number of the upstream bug (or the link), so we can add a
> bugwatch that will inform us about its status. Thanks in advance.
>
> ** Changed in: gnome-control-center (Ubuntu)
> Importance: Undecided => Low
>
> ** Bug watch added: Red Hat Bugzilla #689790
> https://bugzilla.redhat.com/show_bug.cgi?id=689790
>
> ** Also affects: gnome-control-center (Fedora) via
> https://bugzilla.redhat.com/show_bug.cgi?id=689790
> Importance: Unknown
> Status: Unknown
>
> ** Also affects: gnome-control-center
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/862922
>
> Title:
> GCC fails to detect and load available local and network printers
>
> Status in GNOME Control Center:
> New
> Status in “gnome-control-center” package in Ubuntu:
> New
> Status in “gnome-control-center” package in Fedora:
> Unknown
>
> Bug description:
> Linux Mercury 3.0.0-12-generic-pae #19-Ubuntu SMP Fri Sep 23 23:10:56
> UTC 2011 i686 athlon i386 GNU/Linux
>
> Currently running gnome-shell as default DE. I dumped unity.
>
> Trying to detect printers via the gcc printer sub-module loops and
> stops searching after 30 seconds wether on local or network devices.
>
> using system-config-printer flawlessly queries and install available
> devices.
>
> Termianl output:
>
> nathanel@Mercury:~$ lpinfo -l -v
> 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 = beh
> class = network
> info = Backend Error Handler
> 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 = ipp
> class = network
> info = Internet Printing Protocol (ipp)
> 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 = smb
> class = network
> info = Windows Printer via SAMBA
> make-and-model = Unknown
> device-id =
> location =
> Device: uri = parallel:/dev/lp0
> class = direct
> info = LPT #1
> make-and-model = unknown
> device-id =
> location =
> Device: uri = cnijnet:/00-1E-8F-8E-78-B0
> class = network
> info = Canon-MX340-series_00-1E-8F-8E-78-B0
> make-and-model = Canon MX340 series
> device-id =
> location =
>
> -----------------------------
>
> Similar bug found on Fedora bug tracker (Bug #689790):
> https://bugzilla.redhat.com/show_bug.cgi?id=689790
>
> To manage noti...

Read more...

Revision history for this message
Sebastien Bacher (seb128) wrote :

If you do can you let us know the bug number?

Sebastien Bacher (seb128)
Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
In , Fedora (fedora-redhat-bugs) 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

Bug Watch Updater (bug-watch-updater)
Changed in gnome-control-center (Fedora):
importance: Unknown → Medium
status: Unknown → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.