Bug 61643 – unable to start abiword

Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours

Bug 61643 - unable to start abiword

Summary:	unable to start abiword

Status:	CLOSED DUPLICATE of bug 61153

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	abiword (Show other bugs)
Sub Component:
Version:	7.3
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	wdovlrrw
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-03-22 10:28 EST by Leonid Kanter
Modified:	2007-04-18 12:41 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-03-22 14:19:49 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Leonid Kanter 2002-03-22 10:28:52 EST

Description of Problem:

On fresh-installed beta3 I'm unable to start abiword

Version-Release number of selected component (if applicable):

abiword-0.99.2-1

How Reproducible:

always

Steps to Reproduce:
1. start AbiWord in xterm

Actual Results:

/usr/bin/AbiWord: line 67: 19409 Segmentation fault     
$ABISUITE_LIBEXEC/AbiWord_d "$@"

Expected Results:

must work

Additional Information:
	
If LANG is set to C, it show window with message that it's unable to add fonts
to Xserver font path and than fall down with the same message. In ru_RU.koi8r
locale it fall down immediately without showing any windows.

Comment 1 David L. Parsley 2002-03-22 14:19:44 EST

<aol>me too!</aol>
FYI, I happened to have the abiword rpms from abisource.com, and installed
abiword-gnome, -fonts and -clipart.  Works fine, except for having to manually
chkfontpath --add ...

Comment 2 Bernhard Rosenkraenzer 2002-03-25 09:46:23 EST


*** This bug has been marked as a duplicate of 61153 ***

Note You need to log in before you can comment on or make changes to this bug.