Editors crash scrolling file with long lines

Bug #26439 reported by Rkimber
54
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Bluefish
Invalid
Undecided
Unassigned
GTK+
Expired
Medium
gtk+2.0 (Ubuntu)
Triaged
Low
Ubuntu Desktop Bugs

Bug Description

I have experienced this problem with Gedit (standard Ubuntu 5.10 installation)
and with Bluefish 1.04 (compiled on my dual opteron), so it might be a gtk problem.

A file with long lines - e.g.:-

http://www.psr.keele.ac.uk/area/uk/ge59/maj.htm

will cause the editors to crash if you try to scroll down the document by
dragging the scroll bar down with the mouse.

In the terminal, Bluefish gives:-
(bluefish:15351): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file:
assertion `filename != NULL' failed

(bluefish:15351): GdkPixbuf-CRITICAL **: gdk_pixbuf_new_from_file:
assertion `filename != NULL' failed the dir_icon and unknown_icon items
in the config file are invalid The application 'bluefish' lost its
connection to the display :0.0; most likely the X server was shut down
or you killed/destroyed the application.

While Gedit gives:-
The program 'gedit' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadLength (poly request too large or internal Xlib
length erro'. (Details: serial 30590 error_code 16 request_code 1
minor_code 0) (Note to programmers: normally, X errors are reported
asynchronously; that is, you will receive the error a while after
causing it. To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
function.) Terminated

I'm using 2.6.12-9-amd64-k8-smp, Ubuntu 5.10, gtk 2.8.6-0ubuntu2.1

Revision history for this message
Rkimber (rkimber) wrote :

Acrually, I've realized that part of the Bluefish error message relates to
another problem. The Bluefish output at the terminal for this bug just reads:-

The application 'bluefish' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.

Revision history for this message
Carthik Sharma (carthik) wrote :

Hi Rkimber,

Can you reproduce this bug with the latest Dapper packages installed?
If yes, can you please provide us with the debug backtrace?

If this is no longer a bug, please let us know so we can close this bug.

Sorry for the delayed response. You help is highly appreciated.

Revision history for this message
Rkimber (rkimber) wrote :

There is no crash with Dapper.

However, neither editor will display the whole file properly. The very long line at the end of the file (above) seems to screw up the display of the last section of the file.

Revision history for this message
Carthik Sharma (carthik) wrote :

adding Bluefish.

Revision history for this message
Carthik Sharma (carthik) wrote :

Also affects gedit

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

Probably a GTK issue, might be http://bugzilla.gnome.org/show_bug.cgi?id=127731 upstream

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

marking as confirmed since there is an upstream bug

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Medium → Low
status: Needs Info → Confirmed
Changed in gtk:
status: Unknown → Confirmed
Changed in bluefish:
status: Unconfirmed → Rejected
Changed in gtk+2.0:
status: Confirmed → Triaged
Changed in gtk:
importance: Unknown → Medium
Changed in gtk:
status: Confirmed → Expired
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.