Date: Sun, 27 Jan 2008 14:38:42 -0500 From: Joe Marcus Clarke <marcus@marcuscom.com> To: "Steiner, Bernard" <Bernard.Steiner@lahmeyer.de> Cc: freebsd-gnome@freebsd.org Subject: Re: abiword crash on stratup (was: Re: GNOME's newbiew woes and rantings) Message-ID: <1201462722.70499.8.camel@shumai.marcuscom.com> In-Reply-To: <0E3C8932B8AFFF4294C69ABF71FB23656C7F3F@ZDEXV001.lahmeyer.com> References: <0E3C8932B8AFFF4294C69ABF71FB23656171C5@ZDEXV001.lahmeyer.com> <1201034787.54891.33.camel@shumai.marcuscom.com> <0E3C8932B8AFFF4294C69ABF71FB23656C7F3F@ZDEXV001.lahmeyer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-UTDwBgUI0V96xFZPpYmD Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2008-01-27 at 16:17 +0100, Steiner, Bernard wrote: > Hi there, >=20 > >> Some processes SEGV on me straight away (abiword, some screen > savers, and others which I haven't the foggiest idea what they are > supposed to do). The number of *.core files I got since I started on > GNOME simply amazes me. > >> > >> Methinks I am missing something very basic and fundamental here. I > just cannot begin to assume that anybody would even consider using > GNOME if it really were as buggy as that. >=20 > [JMC answered] > > That said, I run GNOME on amd64 (as do a few other users), and I > don't > > have the problems you're describing. There was a recent bug in > AbiWord > > on amd64 that I fixed which caused it to crash at startup. As far > as I > > know AbiWord has since been working for people on amd64. >=20 > I have since re-make-d abiword WITH_DEBUG=3Dyes and gotten the > following: >=20 > ... > DEBUG: Impossible to open font file > [/usr/local/lib/X11/fonts/OTF/GohaTibebZemen.otf] [0] > .DEBUG: Impossible to open font file > [/usr/local/lib/X11/fonts/OTF/SyrCOMAdiabene.otf] [0] > ... > DEBUG: pd_Document::setAttrProp: setting dom-dir to ltr > DEBUG: Could not open > file /usr/local/share/AbiSuite-2.4/templates/normal.awt-en > ... > DEBUG: Doing replace document > DEBUG: XAP_App::notifyFrameCountChange(): count=3D1 > DEBUG: !!!!!!!!! _showdOCument: Initial izoom is 100 > DEBUG: Got FrameImpl f2bc00 area 12573f0 > DEBUG: searchFont [Sans] >=20 > **** (1) Assert **** > **** (1) font at gr_UnixGraphics.cpp:1198 **** > **** (1) Continue ? (y/n) [y] : >=20 >=20 > I do have -r--r--r-- 1 root wheel 334284 Jan 13 > 14:31 /usr/local/lib/X11/fonts/OTF/GohaTibebZemen.otf > so I don't understand why there's such a fuzz about it... > Having said that, I have, in the meantime, installed libotf and will > see whether that gets me anywhere. I don't think you'll get far at all since AbiWord doesn't use libotf. You might try removing the OTF fonts as they might be corrupt. You should also verify you have abiword 2.6.4_3 installed as it has the fix for the amd64 crash. >=20 >=20 > On another note, I would like somebody to put in the GNOME FAQ the > hint that removable media are supposed to get > mounted on /media. Took me a couple of days to work that out. > My /media faithfully served as a mount point for > digital cameras' images and as such the mountpoint on root carried > schg,sunlnk and the /media filesystem > was mode 700 for root (underlying directory re-exported read-only via > nullfs :-) The use of /media is already documented in hier(7). It is designed to contain _subdirectories_. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-UTDwBgUI0V96xFZPpYmD Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkec3cEACgkQb2iPiv4Uz4djpACdHvPZvnjhhA1NLIkdSoBsPvwH zbYAn3ha7E7+AP0PJS9+dvcsirK+UtjF =dm24 -----END PGP SIGNATURE----- --=-UTDwBgUI0V96xFZPpYmD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1201462722.70499.8.camel>