After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 149225 - Can't connect to CUPS server in mixed ipv4/ipv6
Can't connect to CUPS server in mixed ipv4/ipv6
Status: RESOLVED NOTGNOME
Product: gnome-cups-manager
Classification: Deprecated
Component: gnome-cups-manager
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2004-08-03 22:17 UTC by Sebastien Bacher
Modified: 2008-01-29 13:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2004-08-03 22:17:36 UTC 
This bug has been reported in the Debian BTS: http://bugs.debian.org/217257

"When running gnome-cups-manager it displays the following error and exits:

The CUPS server could not be contacted.

I have done some debugging and research, and apparently the bug is
caused by gethostbyname. I'm using a 2.6 kernel with both ipv4 and
ipv6 support, and this seems to cause the troubles.

The call to gnome_program_init in main sets the RES_USE_INET6 flag in
_res.options. After that all calls to gethostbyname returns an ipv6
address instead of ipv4. The function httpConnectEncrypt in libcups2
doesn't like ipv6 addresses and fails and then gnome_cups_check_daemon
in libgnomecups also fails.

One quick fix is to reset the RES_USE_INET6 flag after the call to
gnome_program_init:

   _res.options &= ~RES_USE_INET6;"
Comment 1 Morten Welinder 2004-08-04 13:23:06 UTC 
Why isn't this a problem for any program using libcups2?
Comment 2 Andreas J. Guelzow 2004-08-05 15:45:02 UTC 
this sounds like a libcups bug. Did you file it with them?
Comment 3 Kjartan Maraas 2008-01-29 13:10:18 UTC 
Moving all gnome-cups-manager bugs to new product. Filter on Kjartan's spring cleaning.