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#2162 - anjuta crashes under GNOME
Attached to Project:
Arch Linux
Opened by Christian Huber (crimbil) - Wednesday, 09 February 2005, 10:38 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 09 February 2005, 14:35 GMT
Opened by Christian Huber (crimbil) - Wednesday, 09 February 2005, 10:38 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 09 February 2005, 14:35 GMT
|
DetailsAnjuta 1.2.2 crashes, when it's started in the GNOME environment. This doesn't happen in a plain X-Session or in a windowmanager like fluxbox.
Terminal output: (anjuta:4049): GLib-GObject-WARNING **: IA__g_object_set_valist: construct property "type" for object `ESplash' can't be set after construction ** Message: Initializing AP class ** Message: Initializing AP Instance ** Message: Initializing launcher class (anjuta:4049): Gtk-CRITICAL **: gtk_frame_compute_child_allocation: assertion `GTK_IS_FRAME (frame)' failed |
This task depends upon
Closed by Roberto Carvajal (rcarvajal)
Wednesday, 09 February 2005, 22:10 GMT
Reason for closing: Not a bug
Wednesday, 09 February 2005, 22:10 GMT
Reason for closing: Not a bug
There are others that have the same problem: http://bbs.archlinux.org/viewtopic.php?t=9037
I really can't reproduce the bug, maybe this have something to do with the gnome theme or something like that (that mess up with gtk)..
So we have to wait until a new anjuta release or until someone figured out what is the problem..
Can't fix something that i don't know why is causing problems :)
The new gtk-engines 2.6.1 fixes the problem:
* engines/smooth/src/engine/smooth_gtk2_engine.c:
(smooth_rc_style_parse): Use g_quark_from_string() instead
of g_quark_from_static_string() since the latter will cause
problems when used in modules that are dynamically loaded
and unloaded. This should solve a ton of crashes related
to changing themes. Closes bug #165942, bug #166018,
bug #160803, and is also related to other theme related
crashes all the way back to 1.4.x. Theme engine authors
should be made aware of this so we can get external theme
engines fixed.
CLOSED, NOT AN ANJUNTA BUG :)