[apport] BloGTK.py crashed with IOError in __init__()

Bug #93662 reported by brimstone
14
Affects Status Importance Assigned to Milestone
blogtk (Ubuntu)
Invalid
Undecided
Dan O'Huiginn

Bug Description

Binary package hint: blogtk

crashed 3 times while setting up program, then doesn't start at all & crashes at startup

ProblemType: Crash
Architecture: i386
Date: Mon Mar 19 12:10:37 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/share/blogtk/BloGTK.py
InterpreterPath: /usr/bin/python2.4
Package: blogtk 1.1-2build1
PackageArchitecture: all
ProcCmdline: python2.4 /usr/bin/BloGTK
ProcCwd: /home/micky
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
PythonArgs: ['/usr/bin/BloGTK']
SourcePackage: blogtk
Uname: Linux marvin 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux

Revision history for this message
brimstone (newsletter-fluctus) wrote :
Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

The installation of blogtk seems entirely messed up - thanks for pointing it out.

I think the bug you are reporting here is a side-effect of blogtk not installing properly, combined with bad error-handling. The proxy config file ~/.BloGTK/proxies.conf hasn't been written properly, and rather than raising an error the script proxy.py tries to carry on with meaningless data.

I just installed blogtk, and ran it from a terminal. I got the following error:

Creating new BloGTK prefs directory
Config file not found - Will Open Prefs!
Creating New Config!
Creating new proxies.conf
/usr/share/blogtk/config.py:457: GtkDeprecationWarning: gtk.TRUE is deprecated, use True instead
  self.proxyButton_None.set_active(gtk.TRUE)
Traceback (most recent call last):
  File "/usr/share/blogtk/config.py", line 174, in fillForm
    self.defaultPublish = self.parser.get("Default", "defaultPublish")
  File "/usr/lib/python2.4/ConfigParser.py", line 520, in get
    raise NoOptionError(option, section)
ConfigParser.NoOptionError: No option 'defaultpublish' in section: 'Default'
Creating file for custom tag entry

plus a lot more warnings along the lines of "/usr/share/blogtk/config.py:457: GtkDeprecationWarning: gtk.TRUE is deprecated, use True instead"

Somehow, running blogtk also seemed to crash gaim and emacs-snapshot - I've no idea what that's about.

Anyway, I'm going to have a look at the package, and see if there's anything I can do to clean it up a bit...

Changed in blogtk:
assignee: nobody → daniel-ohuiginn
status: Unconfirmed → In Progress
Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

In fact, I believe this is a side-effect of https://launchpad.net/ubuntu/+source/blogtk/+bug/90371 (which I think is the crash on setup you mentioned, and would be what causes the later crash). Not marking it as a duplicate until I've investigated a bit further, though.

Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

Could you please attach all files in ~/.BloGTK, in particular proxies.conf and BloGTK.conf.

Note that BloGTK.conf is likely to contain the password for your blog account, so you should edit that file to conceal your password and any other personal details.

best,
Dan O'Huiginn

Revision history for this message
brimstone (newsletter-fluctus) wrote :

I just deleted and reinstalled BloGTK - seems to work perfectly now.

I'm sorry that I can't provide the files now - this is actually my first posted msg at launchpad and I missed saving the relevant files - my mistake :-/ But thanks for the fast reply!

Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

Never mind; it's useful to know that this went away on reinstall. I'll close this bug for now, since I can't reproduce your exact error on my machine either. Feel free to reopen it if you get the same problems again in the future.

Revision history for this message
Dan O'Huiginn (daniel-ohuiginn) wrote :

problem vanished on reinstall

Changed in blogtk:
status: In Progress → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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