Issue: RedHat 7.0 (Winston)
System: PWS 620, SINGLE 933mhz, matrox g400 1536 RAM
Test Case: #12)
2.) Abiword_d crashed due to a fatal error(GNOME) segmentation fault
Programs below do not launch when icon is selected.
--gPhoto does not work(i.e. no window or any activity on screen)
--gDict does not work
--gcharmap has crashed due to a fatal error
--xSane does not work
--xScanimage does not work
--XMixer does not work
In addition to the "Abiword_d crashed due to a fatal error" entry:
AbiWord did start when I was working locally. However, when being logged in via
telnet (xhost and DISPLAY is ok) AbiWord immediately crashes with exactly this
Please file this report against all the other packages you've listed as well -
other developers are responsible for them.
Abiword_d still crashes in Beta 4
Does 'abiword -nosplash' work?
AbiWord still won't start in Pinstripe due to a segfault. Also, --nosplash
doesn't work either.
This defect is considered MUST-FIX for Winston Release-Candidate #1
*Beta 5 did not fix the problem
Yep, BETA5 AbiWord hosed, won't even start up
Fixed - the problem was that libpng 1.0.8 is not binary compatible with 1.0.6
and doesn't increase the soname - and abiword was linked dynamically, compiled
*** Bug 15179 has been marked as a duplicate of this bug. ***
*** Bug 15822 has been marked as a duplicate of this bug. ***
Still crashing in RC1 in XFree4. It actually looks like the problem is that the
adding of the Abi font dir to the fontpath fails (xset fp+
/usr/share/AbiSuite/fonts as called in the AbiWord script gives the following)
X Error of failed request: 86
Major opcode of failed request: 51 (X_SetFontPath)
Serial number of failed request: 9
Current serial number in output stream: 11
and then Abi can't load it's fonts and segfaults. With no window manager
running, I actually don't get a segfault, and it pops up its window about being
unable to find its fonts. Adding the Abi font dir to the default xfs font path
does allow AbiWord to start and run properly.
xset fp+ seems to be broken in XF4... Reassigning.
It's probably somewhat related to the fact that
re-running mkfontdir in the abi font directory
gives you no fonts in your fonts.dir. Are there
some missing files (fonts.alias, fonts.scale, perhaps?)
definitely an abiword problem.
Not really. xset +fp is failing for some bizarre reason.
However, the cleanest fix would really be for abiword
to call chkfontpath in %post/%preun, much like
the font packages themselves do. (It's also
easier to do this than to dig inside the X library
*** Bug 16177 has been marked as a duplicate of this bug. ***
This defect has been re-classified as SHOULD-FIX for Winston Gold-release
AbiWord (RC1): OK in one install, also for users, and in one upgrade; fail in another upgrade
chkfontpath has been added.
*** Bug 16937 has been marked as a duplicate of this bug. ***