bad flag alias index & bad flag vector alias errors

Bug #583911 reported by Don Schoeman on 2010-05-21
This bug affects 18 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)

Bug Description

Binary package hint: gedit

This problem most probably is not only related to gedit but I noticed it in gedit first.

When a file is saved to harddrive, gedit seems to hang for a few seconds (this happens even when saving very small text files). When running gedit from the terminal the following errors floods the terminal while the applications "hangs":

error: line xxxxxx: bad flag alias index: 0
error: line xxxxxx: bad flag vector alias

The file is still saved after these errors but the period of non-responsiveness is annoying. This did not happen on prior versions of Ubuntu. I noticed similar errors reported as per Bug #578917 for the software-center package.

Ubuntu 10.04 LTS
gedit version: 2.30.2

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gedit 2.30.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri May 21 18:52:08 2010
EcryptfsInUse: Yes
SourcePackage: gedit

Don Schoeman (don.sch) wrote :
Pedro Villavicencio (pedro) wrote :

could you attach the output of dmesg just after getting the issue to the report? thanks.

Changed in gedit (Ubuntu):
importance: Undecided → Low
status: New → Incomplete

I too is affected by this. On ubuntuforums some people have been debugging it:
It seems that myspell-en-za is the culprit. I've removed the package and haven't seen the problem since.

When i run gedit from the command line i get my console dumped with:

error: line 15: bad flag alias index: 0
error: line 15: bad flag vector alias

and the line number just increase etc...
Didn't get anything in dmesg

Changed in gedit (Ubuntu):
status: Incomplete → Confirmed
Don Schoeman (don.sch) wrote :

I'm not sure that dumping the whole dmesg result would provide any help, I only noticed some similar non-informational error messages at the end of the dmesg result:

[ 56.296848] end_request: I/O error, dev fd0, sector 0
[ 68.468828] end_request: I/O error, dev fd0, sector 0

There is nothing wrong with my HDD though even though it may seem so looking at those errors.

bug fixed removing the

myspell-en-za (south african english dictionary)

sudo aptitude remove myspell-en-za

bugfix shoud be aplied to this package

other dictionaries are working correctly (like myspell-pt-br (brasilian) myspell-en-gb (british) wich i use).

I have this bug too. I could not remove the myspell-en-za package because of dependencies. Instead I did:

sudo rm /usr/share/myspell/dicts/en_ZA.*

This fixed the issue.

Niels Egberts (nielsegberts) wrote :

I can confirm removing the south african english dictionary is a good workaround.

psypher (psypher246) wrote :

Removing that package wants to also remove this:
language-support-en language-support-writing-en

What would that break?


Jonas (jonas-f-henriksen) wrote :

I second psypher on this: Can anyone provide a workaround here?

Runar Ingebrigtsen (ringe) wrote :

Here is my strace for this bug, which appears using tomboy.

Runar Ingebrigtsen (ringe) wrote :

There seems to be some common error among myspell builds, how can I try to confirm this?

Runar Ingebrigtsen (ringe) wrote :

This isn't an upstream bug. It's a generic myspell localization bug in Ubuntu. At least there's nothing to be found about flagvector trouble upstream.

Sivert Henriksen (sivert) wrote :

Problem affects me as well. However removing myspell-en-za or removing the dict-file isn't working. Is there any way to see which dict is doing this?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers