[Jaunty] gedit theme errors when opening

[KevinM]

Binary package hint: gedit

Using gedit version 2.26.0 on Jaunty kernel 2.6.28-11-generic #35-Ubuntu SMP Wed Mar 18 21:55:34 UTC 2009 x86_64 GNU/Linux
Whenever I open a file with gedit, I get a number of error messages about it's theme:
$gksudo gedit /boot/grub/menu.lst
/usr/share/themes/Human/gtk-2.0/gtkrc:82: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:83: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:194: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:83: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:194: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
$ gedit /etc/X11/xorg.conf
/usr/share/themes/Human/gtk-2.0/gtkrc:82: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:83: Murrine configuration option "lightborder_ratio" will be deprecated in future releases. Please use "lightborder_shade" instead.
/usr/share/themes/Human/gtk-2.0/gtkrc:194: Murrine configuration option "highlight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
The kernel version of Jaunty has been updated from Alpha3 onwards, so it's not a fresh install.

[Sebastien Bacher (seb128)]

the warnings are clear that's a gtkrc theme bug

[Kenneth Wimer (kwwii)]

Right, I am assuming this is from the inclusion of the new engine. I will see to it that the gtkrc's get updated.

[Artem Popov (artfwo)]

Hi! Isn't this bug another duplicate of bug 345417? There's quite a number of these floating around already...