GNOME Bugzilla – Bug 304199
first-time launch incorrectly handled
Last modified: 2005-05-19 19:19:34 UTC
Distribution: Slackware Slackware 10.1.0 Package: gnome-blog Severity: blocker Version: GNOME2.10.1 unspecified Gnome-Distributor: GARNOME Synopsis: first-time launch incorrectly handled Bugzilla-Product: gnome-blog Bugzilla-Component: Blog Applet Bugzilla-Version: unspecified Description: Description of Problem: File gnome-blog-poster has an incorrect order of statements regarding initial launch of gnome-blog (attempts to access an uninitialized variable). Steps to reproduce the problem: 1. Run gnome-blog-poster for the first time. 2. 3. Actual Results: Python interpreter error signalling access to an unitialized variable. Expected Results: Blog-poster launching and initially opening a Preferences dialog. How often does this happen? Until you manage to launch it successfully for the first time. ;) Additional Information: File gnome-blog-poster should be patched so that the following lines: (line 29) client = gconf.client_get_default() value = client.get_bool(self.prefs_key + "/initialized") if (value == None or value == gtk.FALSE): poster._showPrefDialog() client.set_bool(self.prefs_key + "/initialized", gtk.TRUE) are at the very end of class BloggerApp's __init__ routine. ------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-14 20:05 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was zoran.rilak@gmail.com.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Please also include the error message, that makes it easier to find duplicates. *** This bug has been marked as a duplicate of 163795 ***