gedit crashed with SIGSEGV in _start()

[Charlie Kravetz]

Binary package hint: gedit

Intitial startup of the system each day, when attempting to open a plain text document on the desktop, gedit fails to open the document. The second attempt will open the document and give me this crash report.

This is reproducable every time.

WORKAROUND: Attempt to open the document again.

Xubuntu 8.10 with gedit text editor added.

[Charlie Kravetz (cjkgeek)]

The actual apport generated crash log

[A. Walton (awalton)]

Thanks for reporting, however the backtrace provided does not contain the information necessary to diagnose this problem. Please try to obtain a better backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Charlie Kravetz (cjkgeek)]

After installing the debug symbols, I can no longer get a failure. I am going to have to wait until I can obtain the required backtrace.

Further, apport failed finding launchpad to report the bug, thus there are no apport logs attached to the original report.

Version of GEDIT:
apt-cache policy gedit
gedit:
  Installed: 2.24.2-0ubuntu1
  Candidate: 2.24.2-0ubuntu1

  Version table:
 *** 2.24.2-0ubuntu1 0
        500 http://ubuntu.osuosl.org intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     2.24.0-0ubuntu1 0
        500 http://ubuntu.osuosl.org intrepid/main Packages

[Charlie Kravetz (cjkgeek)]

Still can not obtain a backtrace for this. Here are my ~/.xsession-errors log, apport.log, and syslog from today with the error opening gedit.

[Sebastien Bacher (seb128)]

did you get the issue again?

[Charlie Kravetz (cjkgeek)]

Yes, it still happens.

[Charlie Kravetz (cjkgeek)]

And again today, 01-12-2009, we had the same issue. Gedit did not open the first time from the desktop, but did open the second attempt. It appears to be random now, not every time I attempt to open a file.

[Charlie Kravetz (cjkgeek)]

Thank you for fixing this. I am using Jaunty 9.04 (development version) and this bug appears to be fixed.