Many errors in gedit after upgrading from breezy to dapper

Bug #48308 reported by Bruce Sherwood
12
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

After upgrading from breezy to dapper, gedit emits a large number of strange error messages, as shown below. (And what does gedit have to do with Python? Is it written in Python? Am I missing some piece of Python after the upgrade?) I tried reinstalling gedit, which made no difference.

bruce@ubuntu-Bruce:~$ gedit test.txt
** (gedit:7278): WARNING **: Could not import pygtk
Traceback (most recent call last):
  File "/usr/lib/gedit-2/plugins/modelines.py", line 20, in ?
    import gedit
ImportError: No module named gedit

** (gedit:7278): WARNING **: Could not load python module modelines

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

** (gedit:7278): CRITICAL **: gedit_plugin_update_ui: assertion `GEDIT_IS_PLUGIN (plugin)' failed

Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 48308] Many errors in gedit after upgrading from breezy to dapper

Looks like your pygtk is broken. What's the output of:

dpkg -l 'py*gtk*' | cat

Revision history for this message
Bruce Sherwood (bruce-sherwood) wrote :

Here is the requested output. The first time I ran this it said <none> for both python-gtk and python-gtk-1.2, so I installed python-gtk-1.2 (but the package manager didn't list python-gtk). After installing, no change in the behavior of gedit. Where is the module "gedit" supposed to be that modelines.py is trying to import?

bruce@ubuntu-Bruce:~$ dpkg -l 'py*gtk*' | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-===============-============================================
un python-gtk <none> (no description available)
ii python-gtk-1.2 0.6.12-4ubuntu1 GTK support module for Python
ii python-gtk2 2.8.6-0ubuntu1 Python bindings for the GTK+ widget set
ii python2.4-gtk2 2.8.6-0ubuntu1 Python bindings for the GTK+ widget set

Revision history for this message
Steven Harms (sharms) wrote :

Has this behavior been fixed, or have you tried it from a fresh dapper install?

Revision history for this message
Bruce Sherwood (bruce-sherwood) wrote :

Not sure exactly what is meant by "fresh dapper install". I can't imagine wiping my dual-boot machine and installing dapper from scratch. I did however run the software update and nothing changed with gedit. The update process did however say it couldn't download gtk+2.0/libgtk2.0 (and dev and common), nor gtk+2.0/gtk2-engines-pixbuf.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. do you use a local session with xorg? does "python -c "import gtk"" work fine? do other pygtk applications are working too? do you run it with your user?

Changed in gedit:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Bruce Sherwood (bruce-sherwood) wrote :

That must be the problem. I built /usr/local/bin/python from source, and that's the python displayed with "which python". I find that /usr/local/bin/python -c "import gtk" yields an import error, whereas /usr/bin/python -c "import gtk" is fine. Clearly the problem is with my nonstandard install of python (done for good reasons), not with Ubuntu.

How would I get gedit to use /usr/bin/python rather than /usr/local/bin/python?

Revision history for this message
Dennis Kaarsemaker (dennis) wrote : Re: [Bug 48308] Re: Many errors in gedit after upgrading from breezy to dapper

 status Rejected

You can remove /usr/local/bin from your $PATH (or move it to
after /usr/bin).

Changed in gedit:
status: Needs Info → Rejected
Revision history for this message
Sebastien Bacher (seb128) wrote :

why do you need to install python to /usr/local? You should stick the packages of the distribution

Revision history for this message
Bruce Sherwood (bruce-sherwood) wrote : Re: [Bug 48308] Re: Many errors in gedit after upgrading from breezy to dapper

I have a very technical reason for doing this, having to do with
building a package for Python (the Visual module) that depends on a
library not part of the Ubuntu distribution, and not wanting to disturb
the regular Python installation.

Bruce

Sebastien Bacher wrote:

>why do you need to install python to /usr/local? You should stick the
>packages of the distribution
>
>
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

"python-visual - VPython 3D scientific visualization library"

why not installing that package?

Revision history for this message
Bruce Sherwood (bruce-sherwood) wrote :

I have the Ubuntu package installed, with the Ubuntu Python package. I'm
working on a new beta version of Visual and want to leave in place the
existing package for comparison.

Bruce

Sebastien Bacher wrote:

>"python-visual - VPython 3D scientific visualization library"
>
>why not installing that package?
>
>
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

ok, anyway not a packaging bug so good luck with that

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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