gedit crashes on a simple text file of 6000 lines

Bug #137625 reported by Timmie
2
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Medium
Nicolas Deschildre

Bug Description

Binary package hint: gedit

Gedit crashes on a file of 6414 lines whereas Scite opens the file correctly.

To reproduce:

1) sudo apt-get install xtide
2) $: tide -m l > tide_list_term.txt (must set terminal encoding to latin1)
3) gedit open tide_list_term.txt
4) gedit would just crash!

Revision history for this message
Timmie (timmie) wrote :
Revision history for this message
Timmie (timmie) wrote :

I generated a error log from terminal.

Revision history for this message
Nicolas Deschildre (ndeschildre) wrote :

Hi!
Thanks for your bug report!
According to the log, it seems there is a mismatch between the python gnome binding version and the gnome library version, which is probably why it is crashing. Does it crash too with any other file?
Can you also give us :
- the version of ubuntu you are using
- the version of python-gnome2 (as seen in the synaptic package manager)
- the version of the libgnome2-0 (as seen in the synaptic package manager)
Can you tell us if you have upgraded from another version of ubuntu, or if it is a fresh install?

Thank you!

Changed in gedit:
assignee: nobody → ndeschildre
status: New → Incomplete
Revision history for this message
Timmie (timmie) wrote :

Here's the information:

- the version of ubuntu you are using
=> 2.6.20-16-generic, Ubuntu 7.04
- the version of python-gnome2 (as seen in the synaptic package manager)
=> 2.18.0-ubuntu1
- the version of the libgnome2-0 (as seen in the synaptic package manager)
=> .18.0-ubuntu1
Can you tell us if you have upgraded from another version of ubuntu, or if it is a fresh install?
Installed as Drapper, upgraded to edgy, feist via the update-manager.

In Edgy the same file opened without problems.
May this be a problem with some plug-in?

Thanks for looking at this.

Revision history for this message
Nicolas Deschildre (ndeschildre) wrote :

Ok before going deep, let's try something simple : update and upgrade feisty :)
It will download the list of the last updates available and then install them.
In order to do that, go to the synaptic package manager, click on "Reload" or "update" at the left of the toolbar (i'm guessing the name from my french localization) then click "upgrade" just at the right.

The problem sounds like you have a mismatch between two librairies (which shouldn't have occured) so maybe a simple upgrade will do the trick.

Revision history for this message
Timmie (timmie) wrote :

A upgrade did not help.

Revision history for this message
Nicolas Deschildre (ndeschildre) wrote :

Ok, i have dig a little, lots of cases are similar to yours. (example : [1] )
The trick seems to be that you have several versions of python installed (which makes sense since you updated from dapper) and gedit is picking the wrong older libraries.
Try to uninstall the older python libs (package python2.4), feisty depends on python 2.5.

[1] http://www.nabble.com/Python-C-API-version-mismatch-tf1393711.html#a3746481

Revision history for this message
Timmie (timmie) wrote :

Hi,
first thanks you for looking into my problem that extensively.

I already noticed that I have the 2 Python versions.
But there are programs that still rely on these:

$: sudo apt-get remove python2.4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libgdal1-grass
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  libqgis0 python-all python-all-dev python2.4 python2.4-dev
  python2.4-examples qgis qgis-plugin-grass scribus scribus-template
0 upgraded, 0 newly installed, 10 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 75.1MB disk space will be freed.
Do you want to continue [Y/n]?

I'd like to maintain these programs.

I had this conflict in various ocasions like when I wanted to start a develpment version of a program that uses wxpython. python always uses the python2.4 version of wxpython whereas the program would need the 2.5 version...

I had already reported this problem in the forums:
python runtime warning
http://ubuntuforums.org/showthread.php?t=543205

I don't know what to do because I am not a fulltime coder and only a python beginner.

Should I define the $PYTHON variable as in this thread here:
http://www.nabble.com/Python-C-API-version-mismatch-tf1393711.html#a3746481

Thanks again and regards!

Revision history for this message
Nicolas Deschildre (ndeschildre) wrote :

Me too i am not a python programmer :) So i'm afraid i won't be of much help for the technical details. Try following the advices in the related topic you find, and if you find the solution, could you explain it here ?
This problem shouldn't have occured after ubuntu upgrades, it seems like there is a wrong package dependency somewhere...

As long as we don't find the reasons and the solution on this problem, we can't act on it.

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

Does anybody get the issue on gusty or has easy steps to trigger it?

Changed in gedit:
importance: Undecided → Medium
Revision history for this message
Timmie (timmie) wrote :

I found the follwing setting in my .bashrc:

export PYTHONPATH=/usr/lib/python2.4/site-packages/

which I had put there after installing basemap for matplotlib. After removing it all Python is now running smoothly.

The issue seems to be solved!

Revision history for this message
Timmie (timmie) wrote :

I change to invalid because it does not exist anymore!

Changed in gedit:
status: Incomplete → Invalid
Revision history for this message
Timmie (timmie) wrote :

How do I mark this bug as "Triaged"?

Changed in gedit:
status: Invalid → In Progress
Revision history for this message
Sebastien Bacher (seb128) wrote :

why do you want to change it to Triaged without any explanation now?

Changed in gedit:
status: In Progress → Invalid
Revision history for this message
Timmie (timmie) wrote :

Because it was causing problems and now the thing is repaired.

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.