gedit randomly crash on close with GLib-GIO:ERROR:/build/buildd/glib2.0-2.27.91/gio/gdbusconnection.c:4404:call_in_idle_cb: assertion failed: (vtable != NULL && vtable->method_call != NULL)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gedit (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: gedit
gedit randomly crash when I close it (ALT+F4 or Window button) with the following assertion.
$ gedit
**
GLib-GIO:
Aborted (core dumped)
After a crash the global menu doesn't work correctly when gedit is launched again (either active but clicking on the submenus does nothing or the whole menu is disabled)
Test Case:
- open a terminal
- launch gedit
- close it
- repeat until it crashes (usually between 5 to 10 tries)
Apport doesn't want to automatically report it so I've attached the data collected including the core dump.
Sorry for this poor quality report.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gedit 2.30.4-1ubuntu3
ProcVersionSign
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
Date: Fri Jan 21 16:12:03 2011
EcryptfsInUse: Yes
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.utf8
LC_MESSAGES=
SHELL=/bin/bash
SourcePackage: gedit
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a '.crash' file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/ apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.