Bug 164151 – Can't look up blogs

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 164151 - Can't look up blogs


Summary:	Can't look up blogs


Status:	RESOLVED FIXED

Product:	gnome-blog
Classification:	Other
Component:	Blog Applet
Version:	0.8
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME blog maintainers
QA Contact:	GNOME blog maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-01-15 08:53 UTC by James Ogley
Modified:	2005-05-20 21:31 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Only use proxy if: use_proxy and host != "" and port != 0 (729 bytes, patch) 2005-05-20 21:27 UTC, Olav Vitters	committed	Details \| Review

Description James Ogley 2005-01-15 08:53:14 UTC

Please describe the problem:
I run my own blog (Blosxom, using an XML-RPC interface that provides the
BloggerAPI), when I run gnome-blog 0.8, I can't lookup the blogs available (this
worked in 0.7, and Drivel's able to communicate with it).

Here's the trace if I run from the command line:

ogley@riggwelter:~> gnome-blog-poster
/opt/gnome/share/themes/Smooth-EyeCandy/gtk-2.0/iconrc:23: Unable to locate
image file in pixmap_path: "stock_stock.svg"
Using gconf_prefix /apps/gnome-blog
/usr/lib/python2.3/site-packages/gnomeblog/gconf_widgets.py:6:
DeprecationWarning: use gtk.ComboBox
  gtk.OptionMenu.__init__(self)
blog type: custom
Using prefix /apps/gnome-blog
Getting list for RPC interface http://www.rubberturnip.org.uk/cgi-bin/api/RPC2
Traceback (most recent call last):

+ Trace 54534

File "/usr/lib/python2.3/site-packages/gnomeblog/blogger_prefs.py", line 186 in _onLookupBlogsButton
```
blog_id_pairs = blog.getBlogList(gconf_prefix)
```
File "/usr/lib/python2.3/site-packages/gnomeblog/blog.py", line 13 in getBlogList
```
return blog_backend.getBlogList(username, password, url, client, gconf_prefix)
```
File "/usr/lib/python2.3/site-packages/gnomeblog/bloggerAPI.py", line 34 in getBlogList
```
bloglist = server.blogger.getUsersBlogs(appkey, username, password)
```
File "/usr/lib/python2.3/xmlrpclib.py", line 1029 in __call__
```
return self.__send(self.__name, args)
```
File "/usr/lib/python2.3/xmlrpclib.py", line 1316 in __request
```
verbose=self.__verbose
```
File "/usr/lib/python2.3/site-packages/gnomeblog/proxy.py", line 31 in request
```
return Transport.request(self, host, "http://"+host+handler, request_body, verbose)
```
File "/usr/lib/python2.3/xmlrpclib.py", line 1062 in request
```
self.send_content(h, request_body)
```
File "/usr/lib/python2.3/xmlrpclib.py", line 1176 in send_content
```
connection.endheaders()
```
File "/usr/lib/python2.3/httplib.py", line 712 in endheaders
```
self._send_output()
```
File "/usr/lib/python2.3/httplib.py", line 597 in _send_output
```
self.send(msg)
```
File "/usr/lib/python2.3/httplib.py", line 564 in send
```
self.connect()
```

File "/usr/lib/python2.3/httplib.py", line 532 in connect

socket.SOCK_STREAM): socket.gaierror: (-2, 'Name or service not known') ogley@riggwelter:~>



Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:

Comment 1 James Ogley 2005-01-15 22:45:32 UTC

This is caused by GConf key /system/http_proxy/use_http_proxy being set to
"True" but /system/http_proxy/host and/or /system/http_proxy/port being invalid
- seems reasonable, but perhaps, if host is empty (as was the case for me -
think that's what gnome-network-preferences sets it as if you have "Manual proxy
configuration" checked, but nothing in the fields, it should fall back to a
direct connection?

Comment 2 Olav Vitters 2005-05-20 21:27:56 UTC

Created attachment 46690 [details] [review]
Only use proxy if: use_proxy and host != "" and port != 0

As suggested in comment 1, do not solely rely on the use http_proxy flag; also
ensure host isn't blank and port isn't 0.

Comment 3 Olav Vitters 2005-05-20 21:31:38 UTC

Committed to HEAD.

Marking FIXED.