Thank you for your bug report, is that still an issue?
** Summary changed:
- gedit crashed with SIGABRT in __kernel_vsyscall()
+ gedit crashed with SIGABRT in __kernel_vsyscall():
connection->initialization_error == NULL
** Summary changed:
- gedit crashed with SIGABRT in __kernel_vsyscall():
connection->initialization_error == NULL
+ gedit crashed with SIGABRT in initable_init():
connection->initialization_error == NULL
** Visibility changed to: Public
** Changed in: gedit (Ubuntu)
Status: New => Incomplete
** Changed in: gedit (Ubuntu)
Importance: Medium => Low
--
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/752871
Title:
gedit crashed with SIGABRT in initable_init():
connection->initialization_error == NULL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/752871/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
