** Changed in: gedit
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/917344
Title:
gedit crashed with SIGABRT: (tp != NULL)
To manage notifications abou
This is not a bug in gedit.
The issue was caused by a chain of python imports in the set of plugins I was
running. This specific problem was cause by bzr-dbus and bzr-notify both of
which had fallback conditions to import from old gtk or old gobject.
I located the problem imports by placing a pdb
** Changed in: gedit (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/917344
Title:
gedit crashed with SIGABRT: (tp != NULL)
To manage not
** Changed in: gedit
Status: Unknown => New
** Changed in: gedit
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/917344
Title:
gedit crashed
Sent upstream: https://bugzilla.gnome.org/show_bug.cgi?id=670061
** Bug watch added: GNOME Bug Tracker #670061
https://bugzilla.gnome.org/show_bug.cgi?id=670061
** Changed in: gedit (Ubuntu)
Status: New => Confirmed
** Also affects: gedit via
https://bugzilla.gnome.org/show_bug.cgi?
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/G
