[Bug 32763] Pasting a very wide string follows a buffer overrun that causes the prog to exit

[Tom]

Public bug report changed:
https://launchpad.net/malone/bugs/32763

Description changed to:
    I accidently tried to paste a file that was 164k big to the gconf-
    editor list-selection box and the editor crashed! I was
    wondering...doing it twice forced the discovering...

    URL to the file I copied (started copying with "2006-02-14T06:08:59Z
    From" and copied everything to the end) :

    http://64.233.179.104/search?q=cache:cezlZkDfXbIJ:doc.gwos.org/index.php%3Ftitle%3DSpecial:Newpages%26feed%3Datom+xgl+svgs&hl=de&gl=de&ct=clnk&cd=3&client=firefox

    The gdb output:
    ----------------------------

    Starting program: /usr/bin/gconf-editor
    [Thread debugging using libthread_db enabled]
    [New Thread 1997719232 (LWP 20042)]
    The program 'gconf-editor' 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 17955 error_code 16 request_code 10 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.)
    The program 'gconf-editor' 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 17956 error_code 16 request_code 97 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.)

    Program exited with code 01.
    -------------------------------------------------

    
    Every other gnome-app I tried to does the same and crashed also: like the ctrl+L adress bar in nautilus, for example.

    My PC is a notebook, Fujitsu Siemens Amillo M3438 with an nvidia
    6600 graphics card 512MB ram 80gig HD and an Intel 1,8Ghz processor.
    Running Dapper Drake that except this bug very very stable is! I
    love this distro, all you guys rock! Thanks for all your effort!

    Greets, Tom