|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
Re: GLib-GObject-CRITICALI have applied the patch pointed by Don Lewis and available
under "http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/112283" I have recompiled the editors/openoffice.org-2 (recompiled java/jdk15 just before). While opening any document the following error messages appear in the terminal openoffice is launched from: (process:67964): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function (process:67964): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (process:67964): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed I believe it is amd64 specific. One of the differences is that amd64 build of OOo is always made WITHOUT_MOZILLA. Can anyone on 7.0 or 8-CURRENT on i386 test OOo WITHOUT_MOZILLA? In comparison with Marcin I have no problems (I hope) with JRE, but I have compiled the native one, bootstrapping from native jdk too. And I can save the newly created .odt file, OOo hangs with the error messages above when I try to close (saved) document. System conf: [wep4017] ~> ls /var/db/pkg/ | grep jdk jdk-1.5.0.13p7_1,1 [wep4017] ~> java -version java version "1.5.0_13-p7" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-p7-root_20_nov_2007_17_47) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_13-p7-root_20_nov_2007_17_47, mixed mode) [wep4017] ~> uname -a FreeBSD wep4017.physik.uni-wuerzburg.de 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Nov 19 19:14:19 CET 2007 root@...:/usr/obj/usr/src/sys/GENERIC amd64 [wep4017] ~> cat /etc/make.conf CPUTYPE ?= nocona SUP_UPDATE = YES SUPFILE = /root/standard-supfile PORTSSUPFILE = /root/ports-supfile DOCSUPFILE = /root/doc-supfile DOC_LANG = en_US.ISO8859-1 .if ${.CURDIR:M*/usr/ports*} .include "/etc/ports.conf" .endif # added by use.perl 2007-11-12 11:31:04 PERL_VER=5.8.8 PERL_VERSION=5.8.8 [wep4017] ~> cat /etc/ports.conf WITH_OPTIMIZED_CFLAGS= yes WITH_OPTIMIZED_FLAGS= yes WITH_GHOSTSCRIPT_AFPL= yes WITHOUT_CUPS= yes A4= yes RANDOMIZE_MASTER_SITES= yes .if ${.CURDIR:M*/editors/openoffice.org-2*} WITH_KDE= yes WITH_SYSTEM_FREETYPE= yes WITHOUT_GNOMEVFS= yes WITHOUT_MOZILLA= yes # Not enough space #LOCALIZED_LANG= all .endif _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICALAlexey Shuvaev wrote:
> I believe it is amd64 specific. One of the differences is that > amd64 build of OOo is always made WITHOUT_MOZILLA. > Can anyone on 7.0 or 8-CURRENT on i386 test OOo WITHOUT_MOZILLA? > In comparison with Marcin I have no problems (I hope) with JRE, but > I have compiled the native one, bootstrapping from native jdk too. > And I can save the newly created .odt file, OOo hangs with the error > messages above when I try to close (saved) document. I think we have exactly the same problem. My JRE works otherwise fine. --Marcin _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICAL / cannot initialize gtk_recent_managerAlexey Shuvaev wrote:
> (process:67964): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function > > (process:67964): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed > > (process:67964): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed > > > I believe it is amd64 specific. One of the differences is that > amd64 build of OOo is always made WITHOUT_MOZILLA. > Can anyone on 7.0 or 8-CURRENT on i386 test OOo WITHOUT_MOZILLA? > In comparison with Marcin I have no problems (I hope) with JRE, but > I have compiled the native one, bootstrapping from native jdk too. > And I can save the newly created .odt file, OOo hangs with the error > messages above when I try to close (saved) document. Which version of GTK+ are you using? gtk-2.12.1_1 glib-2.14.2 I have recompiled everything with debug (hours....) and narrowed this down here: (gdb) list 676 */ 677 GtkRecentManager * 678 gtk_recent_manager_new (void) 679 { 680 return g_object_new (GTK_TYPE_RECENT_MANAGER, NULL); 681 } 682 683 /** 684 * gtk_recent_manager_get_default: 685 * (gdb) where #0 IA__gtk_recent_manager_new () at gtkrecentmanager.c:681 #1 0x000000080f11a136 in IA__gtk_recent_manager_get_default () at gtkrecentmanager.c:698 #2 0x000000080d51ab2c in SystemShell::AddToRecentDocumentList () from /usr/local/openoffice.org-OOG680_m7/program/libsfx680fx.so g_object_new fails: (process:78374): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function (process:78374): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (process:78374): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed probably because type 'GTK_TYPE_RECENT_MANAGER' is not registered. This happens only if SystemShell::AddToRecentDocumentList is able to to find gtk_recent_manager_get_default and gtk_recent_manager_add_item functions. Support for this has been introduced in rev 1.8 of shell/source/unix/sysshell/systemshell.cxx http://qa.openoffice.org/issues/show_bug.cgi?id=75190 I will try to fix this or turn this feature somehow off. --Marcin _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICAL / cannot initialize gtk_recent_managerCan you try this dirty patch? --- shell/source/unix/sysshell/systemshell.cxx.orig 2007-12-05 01:05:04.117619430 +0100 +++ shell/source/unix/sysshell/systemshell.cxx 2007-12-05 02:50:40.620069880 +0100 @@ -126,14 +126,15 @@ } bool ret = (NULL != sym_gtk_recent_manager_get_default) && (NULL != sym_gtk_recent_manager_add_item); - return ret; + return 0; } //############################## void AddToRecentDocumentList(const rtl::OUString& aFileUrl, const rtl::OUString& aMimeType) { - static bool bIsRecentManagerPresent = init_recent_manager_api(); + // static bool bIsRecentManagerPresent = init_recent_manager_api(); + static bool bIsRecentManagerPresent = 0; // Convert file URL for external use (see above) rtl::OUString externalUrl = translateToExternalUrl(aFileUrl); Yes, I think it should "bool" not "int" --Marcin _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICAL / cannot initialize gtk_recent_managerOn Wed, Dec 05, 2007 at 01:33:30AM +0100, Marcin Cieslak wrote:
> Which version of GTK+ are you using? [wep4017] ~> ls /var/db/pkg/ | grep gtk gtk-2.12.1_1 [wep4017] ~> ls /var/db/pkg/ | grep glib glib-2.14.2 I have just started the rebuild with your patch applied. Works it around for you? Thank you for investigations! _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICAL / cannot initialize gtk_recent_managerHello!
I recompiled the OOo-2 with your patch and now it seems to be working. Thanks! --- shell/source/unix/sysshell/systemshell.cxx.orig 2007-06-19 18:12:44.000000000 +0200 +++ shell/source/unix/sysshell/systemshell.cxx 2007-12-05 17:28:49.000000000 +0100 @@ -126,14 +126,15 @@ } bool ret = (NULL != sym_gtk_recent_manager_get_default) && (NULL != sym_gtk_recent_manager_add_item); - return ret; + return 0; } //############################## void AddToRecentDocumentList(const rtl::OUString& aFileUrl, const rtl::OUString& aMimeType) { - static bool bIsRecentManagerPresent = init_recent_manager_api(); + // static bool bIsRecentManagerPresent = init_recent_manager_api(); + static bool bIsRecentManagerPresent = 0; // Convert file URL for external use (see above) rtl::OUString externalUrl = translateToExternalUrl(aFileUrl); _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICAL> I believe it is amd64 specific.
I am experiencing the same problem on 6-STABLE i386 using native jdk15. I just started an overnight build with Marcin's hack and will report back tomorrow. - Bartosz _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICALBartosz Fabianowski wrote:
>> I believe it is amd64 specific. > > I am experiencing the same problem on 6-STABLE i386 using native jdk15. > I just started an overnight build with Marcin's hack and will report > back tomorrow. The bug http://www.openoffice.org/issues/show_bug.cgi?id=75190 has just got reopened. This bug only does not show up if gtk+ will get initialized by something else. I think if you are running GNOME you may get gtk+ initialized anyway due to the "File -> Open" file picker support. Can anyone confirm if forcing OOo to think it runs under GNOME by setting environment variable OOO_FORCE_DESKTOP=gnome fixes the problem? The relevant desktop detection code is here: http://lxr.go-oo.org/source/gsl/vcl/unx/source/plugadapt/salplug.cxx#345 --Marcin _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
|
|
Re: GLib-GObject-CRITICAL> Can anyone confirm if forcing OOo to think it runs under GNOME by
> setting environment variable > > OOO_FORCE_DESKTOP=gnome > > fixes the problem? Yes, this works for me. I am running KDE as my desktop environment and OpenOffice.org normally crashes on closing or opening a file (thankfully, saving always works). With this setting, it runs like a charm. This is the unpatched 2.3.1 build straight from ports. - Bartosz _______________________________________________ freebsd-openoffice@... mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-openoffice To unsubscribe, send any mail to "freebsd-openoffice-unsubscribe@..." |
| Free embeddable forum powered by Nabble | Forum Help |