Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#14848 - [gedit] won't start (most of the time)
Attached to Project:
Arch Linux
Opened by Rulatir (Rulatir) - Wednesday, 27 May 2009, 13:32 GMT
Last edited by Jan de Groot (JGC) - Saturday, 06 June 2009, 22:32 GMT
Opened by Rulatir (Rulatir) - Wednesday, 27 May 2009, 13:32 GMT
Last edited by Jan de Groot (JGC) - Saturday, 06 June 2009, 22:32 GMT
|
DetailsDescription:
Since a recent pacman -Syu, gedit won't start most of the time. Console output: /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: Invalid symbolic color 'bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: error: invalid identifier `bg_color', expected valid identifier /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: Invalid symbolic color 'bg_color' /usr/share/themes/Clearlooks/gtk-2.0/gtkrc:49: error: invalid identifier `bg_color', expected valid identifier TypeError: Cannot create a consistent method resolution order (MRO) for bases ImplementorIface, GInterface, gtk.Orientable ** ERROR:pygobject.c:923:pygobject_new_full: assertion failed: (tp != NULL) Przerwane (I believe the bg_color lines are irrelevant but still paste them for completeness). It does NOT happen every time, just most of the time - about 1 in 10 attempts succeeds. Passing --sm-client-disable appears to increase the chance to about 1 in 3. Additional info: * package version(s) gedit 2.26.2-1 gedit-plugins 2.26.2-1 gedit-plugins-extra 2.24.1-4 gtk2 2.16.1-1 pygobject 2.16.1-1 pygtk 2.14.1-4 python 2.6.2-1 * config and/or log files etc. Steps to reproduce: Start gedit. |
This task depends upon
Closed by Jan de Groot (JGC)
Saturday, 06 June 2009, 22:32 GMT
Reason for closing: Works for me
Additional comments about closing: Must be one of your plugins.
Saturday, 06 June 2009, 22:32 GMT
Reason for closing: Works for me
Additional comments about closing: Must be one of your plugins.
Comment by Jan de Groot (JGC) -
Wednesday, 27 May 2009, 22:36 GMT
I think this is coming from one of the gedit-plugins packages that is triggering a fatal assertion in pygobject. Searching the internet for the error shows up multiple programs with this issue, the source of this problem is pygobject.