Ubuntu
gedit package

gedit python console NameError when changing colors

Bug #654867 reported by Jason Conti on 2010-10-04

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gedit	Expired	Medium	gnome-bugs #634002
	gedit (Ubuntu)	Fix Released	Low	LaserJock

Bug Description

Binary package hint: gedit

In Maverick gedit-2.30.3-1ubuntu1:

When configuring the Python Console plugin, changing the "Command Color" results in a python NameError:

Traceback (most recent call last):
  File "/usr/lib/gedit-2/plugins/pythonconsole/config.py", line 129, in on_colorbutton_command_color_set
    self.config.color_command = colorbutton.get_color().to_string()
  File "/usr/lib/gedit-2/plugins/pythonconsole/config.py", line 59, in <lambda>
    lambda self, value: self.gconf_set_str(GCONF_KEY_COMMAND_COLOR, value))
  File "/usr/lib/gedit-2/plugins/pythonconsole/config.py", line 81, in gconf_set_str
    v = PythonConsoleConfig.gconf.Value(gconf.VALUE_STRING)
NameError: global name 'gconf' is not defined

This can be fixed by including the prefix PythonConsoleConfig. to two of the gconf references in /usr/lib/gedit-2/plugins/pythonconsole/config.py . A patch will be attached.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gedit 2.30.3-1ubuntu1 [modified: usr/lib/gedit-2/plugins/pythonconsole/config.py]
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Mon Oct 4 17:51:49 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: gedit

Tags:

Related branches

lp:ubuntu/natty/gedit

Revision history for this message

Jason Conti (jconti) wrote on 2010-10-04:

Dependencies.txt Edit (4.4 KiB, text/plain; charset="utf-8")

gedit-pythonconsole-gconf.patch Edit (864 bytes, text/plain)

Pedro Villavicencio (pedro) on 2010-10-05

Changed in gedit (Ubuntu):
importance:	Undecided → Low

Brian Murray (brian-murray) on 2010-10-05

tags:

added: patch

LaserJock (laserjock) on 2010-10-26

Changed in gedit (Ubuntu):
status:	New → In Progress
assignee:	nobody → LaserJock (laserjock)

Revision history for this message

LaserJock (laserjock) wrote on 2010-10-27:

debdiff Edit (2.4 KiB, text/plain)

OK, here's a debdiff for Jason's patch. I tested it and it seems to fix the bug :-)

Changed in gedit (Ubuntu):
status:	In Progress → Confirmed

Revision history for this message

Sebastien Bacher (seb128) wrote on 2010-11-04:

Thank you for your work there, is there any chance you could send that patch back to GNOME as well by opening a bug on http://bugzilla.gnome.org?

Revision history for this message

LaserJock (laserjock) wrote on 2010-11-04:

Done, thanks Seb.

Changed in gedit:
importance:	Undecided → Unknown
status:	New → Unknown

Sebastien Bacher (seb128) on 2010-11-04

Changed in gedit (Ubuntu):
status:	Confirmed → Triaged

Bug Watch Updater (bug-watch-updater) on 2010-11-04

Changed in gedit:
importance:	Unknown → Medium
status:	Unknown → New

Revision history for this message

Sebastien Bacher (seb128) wrote on 2010-11-05:

sorry I had already applied the patch by the time I saw the debdiff, I copied the description from it in the patch though before uploading, thanks for the work!

Changed in gedit (Ubuntu):
status:	Triaged → Fix Committed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2010-11-05:

This bug was fixed in the package gedit - 2.30.4-1ubuntu2

---------------
gedit (2.30.4-1ubuntu2) natty; urgency=low

* debian/patches/02_gconf_import.patch:
- correct gconf import, thanks Jason Conti and LaserJock (lp: #654867)
-- Sebastien Bacher <email address hidden> Fri, 05 Nov 2010 19:10:00 +0100