gedit crashed with SIGABRT in g_assertion_message()

[Jani Uusitalo]

Had just opened Gedit, and the file chooser dialog from there. Had successfully selected one directory in the dialog, and the crash occurred when I clicked (I think) on the file name listing column. Couldn't reproduce it again.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gedit 3.10.4-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
Uname: Linux 3.13.0-16-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Mar 8 08:15:01 2014
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2012-05-25 (652 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcCmdline: gedit
Signal: 6
SourcePackage: gedit
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gedit crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to trusty on 2013-11-17 (110 days ago)
UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare ssh sudo vboxusers

[Paul White (paulw2u)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner.

Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.

I'm setting the status of this bug to 'Invalid' as the reporter says he could not reproduce the problem again and there have been no comments added in the eight years that have passed since the bug reported was raised.