Apache OpenOffice (AOO) Bugzilla – Issue 88724
DEV300_m9 and BEA300_m1 freeze on startup on Kubuntu 6.06 LTS
Last modified: 2009-09-25 18:19:35 UTC
Installation of DEV300_m9 (or DEV300_m10) works well but when I launch ./soffice I can configure OOo but when I try to open a file from the startcenter I get the following error message : Logic error 3 Signal 6 during fontconfig initialization called, ignoring fontconfig and OOo freezes. My version of Kubnutu is 6.06 LTS I did not had this problem with Dev300_m3.
On Ubuntu 6.06 LTS I can't confirm. DEV300_10 starts without errors when using the startcenter.
Yes, I presume there is a dependence issue specific to (K)ubuntu 6.06 LTS (Dapper Drake). But I don't know how to confirm that.
Interesting. The "Logic Error 3" is unknown to me. "Signal 6 during fontconfig initialization called, ignoring fontconfig" however is an assertion from psprint/source/printer/cupsmgr.cxx. This is actually a copy/paste error instead of fontconfig it should say "CUPS" here. This happens if during cupsGetDests (which is the call to ask the CUPS system for its list of printers) a crash occurs which we ignore then and take as an indication that CUPS is misconfigured and not to be used. The hang afterward I can only guess about; since without CUPS the print system now falls back to good old command line, I could imagine that the command line "lpc status" does not return respectively hangs on that system. Could you confirm this ?
I am trying Dev300_m10 at home with my professionnal laptop which is not connected to office network. This network give us access to printers. At home, without connected printer, OOo 2.4 (it was already the case with previous versions) hangs for about 3 minutes after startup on the first dialog I click on. After that OOo works normally. Is it possible that the issue with Dev300_m10 is another manifestation of the same problem ? However I have waited for more than 3 minutes before I killed Dev300_m10. Launching OOo 2.4 in a terminal does not give this error message. "lpc status" give nothing.
If I launch Dev300_m9 before the network is started, OOo crashes with the following message error : Logic error 3 Logic error 3 KCrash: Application 'soffice.bin' crashing... X IO Error
I forgot to give an information : Dev300_m3 worked well on the same laptop and in the same conditions (at home without network printer). Something has changed between m3 and m9. Perhaps an exotic compiler flag ?
Same problem with BEA300_m1.
Thanks to the help of ericb, it seems that, under Kubuntu, the desktop is not detected. If I add SAL_USE_VCLPLUGIN="gen" export SAL_USE_VCLPLUGIN to the beginning of the soffice shell script, then BEA300_m1 works well. I presume it will be the same for DEV300_m9 and DEV300_m10. If I change "gen" into "kde", I get the same error message : Signal 6 during fontconfig initialization called, ignoring fontconfig
Perhaps it is a problem of dependence : (K)ubuntu 6.06 has version 2.2 of glibc2 and BEA300_m1 needs version 2.3.1 (cf readme). I don't understand why dependencies are not specified in Debian packages.
Hi, I have installed a clean (no other OOo installed) installation of BEA300_m1 under Ubuntu 6.06, glibc2 version is 2.2 without any problem. All modules load and works correctly. Adding the FR language pack works well too. Kind regards - Sophie
If I replace the proprietary driver nvidia by the free driver provided by Ubuntu (nv) in my xorg.conf, then BEA300_m1 works well.
and closed.
New data for this issue after tests on Dev300_m17 and OOo 2.4.1 RC2 : - with environnement variable SAL_USE_VCLPLUGIN="kde" OOo crashes with error message : Logic error 3 Signal 6 during fontconfig initialization called, ignoring fontconfig - with SAL_USE_VCLPLUGIN="gen" OOo don't crash but the look&feel is ... :) - with SAL_USE_VCLPLUGIN="gtk" OOo don't crash but icons et menus disappear when the mouse goes over - with SAL_USE_VCLPLUGIN="gtk" and SAL_NO_NWF="1" (it seems that the value 1 does not matter) OOo works well with l&f gtk under kde. I have only 6 warning messages like : (soffice:16328): Gtk-WARNING **: gtkwidget.c:7322: widget class `GtkWindow' has no property named `link-color' and : (soffice:16328): Gtk-WARNING **: gtkwidget.c:7322: widget class `GtkWindow' has no property named `visited-link-color' If I add export SAL_DISABLE_SYNCHRONOUS_PRINTER_DETECTION="true" the problem of hanging at startup when my laptop is connected to another network disappears (cf. my 4th additional comment).
.
Could you please attach a stack trace of the crash with the kde plugin ? The setting of SAL_DISABLE_SYNCHRONOUS_PRINTER_DETECTION will cause OOo not to wait for CUPS or lpr to find the installed printers before displaying them, which explains why it starts up immediately after that.
Created attachment 54349 [details] log of script soffice running with strace
I have attached the log of the command strace soffice.sh where soffice.sh is the following script : #!/bin/sh # script pour lancer OOo avec JMF JMFHOME=/home/faure/bin/JMF2.1.1e CLASSPATH=$JMFHOME/lib/jmf.jar:.:${CLASSPATH} export SAL_USE_VCLPLUGIN="kde" export SAL_DISABLE_SYNCHRONOUS_PRINTER_DETECTION="true" /opt/ooo-dev3/program/soffice "$@" I need to kill OOo by ctrl+C after the error message Signal 6 during fontconfig initialization called, ignoring fontconfig
For OOo 2.4.1 and from Dev300_m19 it works well (KDE l&f) with only export SAL_NO_NWF="1" OOo being configured to use system fonts for the UI.
I confirm I have the same problem with dev300m22. and JBF workaround works also for me. export SAL_NO_NWF="1" OOo being configured to use system fonts for the UI. nb : Simply Mepis 7 / KDE 3.5 / Ati Radeon Yves
and now? one year later? does it also haappen with a clear user environment and the latest version of openOffice.org?
Oh sorry, I forgot to update this issue. I do not use KDE anymore, partially because of the lack of system integration of OOo in KDE. So I can't say if the problem still occur with OOo 3.x and I do not know what is the best resolution mode to close this issue. worksforme, wontfix ? Regards JBF
if nobody gives a further comment here I set the issue to invalid
-> closed