Gedit in Dapper returns errors

[Tod Merley]

On 7/14/06, Dave M G <martin at autotelic.com> wrote:
>
> Ubuntu Users,
>
> Each time I start up gedit from the command line, I get the following
> errors:
>
> ImportError: could not import gtksourceview
> Traceback (most recent call last):
>   File "/usr/lib/gedit-2/plugins/modelines.py", line 24, in ?
>     class ModelinePlugin(gedit.Plugin):
> AttributeError: 'module' object has no attribute 'Plugin'
>
> ** (gedit:15692): WARNING **: Could not load python module modelines
>
> ** (gedit:15692): CRITICAL **: gedit_plugin_update_ui: assertion
> `GEDIT_IS_PLUGIN (plugin)' failed
>
>
> The last line of those errors will repeat many times, and come up even
> more as I use gedit.
>
> I tried reinstalling gedit from within Synaptic, but it has not helped.
>
> Can anyone let me know what to do to get rid of these?
>
> Thank you for any advice.
>
> --
> Dave M G
>
> --
> ubuntu-users mailing list
> ubuntu-users at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>

Hi Dave!

I do not have your problem but was considering removing gedit and seeing if
the mentioned files also went away and re-appeared.  However, seeing that
"ubuntu-desktop" would also be removed made me a bit shy of doing a remove
or total remove.

I would be tempted to try this:

0. Use updatedb and locate (man updatedb and man locate) to find the
gtksourceview files.  You should see some .so and some
python.langmentioned.  Check the permissions and other access
parameters of these files
and do compares as below.
1. Find or make another Ubuntu installation like the one you have (same
version and updates).
2. Try a file compare (man cmp) between your working and non-working linux
install "flagged" gedit files.
3.  If there is a differance, replace the file in the non working
installation with a copy of the one in the working installation.
4. If not, expand the basic idea looking for the differance.  You can use
(man updatedb (from root)) and (man locate) to find the gedit files.
5. If worse comes to worse, check the HD and other hardware, secure the
network, and pull the data/work files and do a fresh install.

Interesting problem.  It might be good to look at the syslogs and messages!
I wonder why what got corrupted??!?

Good Hunting!

Tod
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20060715/65ac13f6/attachment.html>