Ubuntu
abiword package

Lots of artifiacts

Bug #333583 reported by Bruce Cowan
52
This bug affects 8 people
Affects Status Importance Assigned to Milestone
AbiWord
Invalid
Medium
Fedora
Won't Fix
Medium
abiword (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: abiword

In the current Jaunty AbiWord, there are a lot of artifacts on the page canvas. This makes editing a document very difficult.

This seems to be only be a problem with compositing window managers.

See original description
Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

Description of problem:

In Fedora 10 running with the compiz-fusion-0.7.8-2.fc10.i386 Window manager the caret in AbiWord-2.6.5 appears as a solid rectangular block which not blink. Furthermore, upon typing large amounts of screen dirt from the caret are generated.

This bug was not present in Fedora 9, nor does it appear in compiz-fusion with the nivdia video card. It does not appear in metacity either. From my knowledge of abiword my guess is that compiz-fusion is not handling screen captures or restores with called from a gtk-idle loop.

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

compiz-fusion-0.7.8-2.fc10.i386
intel 82G33/G31
fedora 10.

How reproducible:
100% reproducible in the combination of hardware and software shown above. Bug was not present in fedora 9.

Steps to Reproduce:
1. enable compiz-fusion with intel 82G33/G31 video card in Fedora 10
2. Start abiword
3.

Actual results:

Observed solid rectangle where the blinking caret should be.

Expected results:

A blinking caret should appear at the location where text enters abiword
Additional info:

Revision history for this message
In , Matěj (matj-redhat-bugs) wrote :

Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.

Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

Created attachment 330064
xorg.conf used for my desktop.

Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

Created attachment 330065
My most recent x11.log file

Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

Created attachment 330066
x11.0.log for auto-detected server

OK here is the additional information requested.

The first x11.log is the log file captured from the xorg.conf file attached.
The second x11.0.log file the log file resulting from the server obtained without an xorg.conf file.

Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

Also the second x11.0.0log file is running the compiz-fusion window manager. The caret bug is the same as ever.

Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :

I also see this. The problem stops when I use metacity and occurs when I use compiz. This is not related to the grace font bug; grace still glitches when using Metacity.

Picture attached. This is just from moving the cursor around. Try to guess the path I took. ;)

Fonts can also be cut off in white from the cursor, and not entirely appear.

Revision history for this message
GiuseppeVerde (launchpad-digitasaru) wrote :

Moving to confirmed because I can see this too.

Changed in abiword:
status: New → Confirmed
Bruce Cowan (bruce89-deactivatedaccount)
description: updated
Revision history for this message
seb0 (sjousten) wrote :

I have this bug too it's very annoying. I have to turn compiz off when I want to use abiword.
I hope you will do something quickly to solve this problem.

Thank you anyway

Revision history for this message
Bruce Cowan (bruce89-deactivatedaccount) wrote :

BTW, AbiWord 2.6.6+ fixes this.

Revision history for this message
seb0 (sjousten) wrote :

I have already tried that with abiword 2.6.8 from the sources and it don't seems that it solve anything, I'll try it again. Have you used the repository proposed in the install wiki or have you done like me with the sources?

Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

Hi folks!

How is the progress on this bug? I've upgraded to fedora 11 and this bug is still present.

We now have a quite a lot of commentary in AbiWord's bugzilla related to this. See here:

http://bugzilla.abisource.com/show_bug.cgi?id=12066

Basically I can't use compiz or compiz-fusion on my intel grahics card. It also appears to affect ATI graphics cards although nvidia cards work fine.

Revision history for this message
In , Martin (martin-redhat-bugs) wrote :

More info:

We blink the caret by taking a snapshot of the screen pixmap, then draw the
caret over that. It appears that taking this snapshot of the screen pixmap
returns a solid black rectangle, rather than what was on the screen.

Revision history for this message
Paul Garvin (paul-paulgarvin) wrote :

Having this issue as well on Xubuntu 9.06 (Abiword 2.6.6, XFCE 4.6.0). It's the compositor that is doing it. Turn the compositor off and everything goes back to normal.

Revision history for this message
RHTopics (tyrht01) wrote :

I am also having this problem with Abiword while using compiz. Disabling compiz stops the problem.

System and installation information:------------------------------

lsb_release -rd : Description: Ubuntu 9.04, Release: 9.04

apt-cache policy compiz
      Installed: 1:0.8.2-0ubuntu8.1
      Candidate: 1:0.8.2-0ubuntu8.1
      Version table:
     *** 1:0.8.2-0ubuntu8.1 0
            500 http://us.archive.ubuntu.com jaunty-updates/main Packages
            100 /var/lib/dpkg/status
         1:0.8.2-0ubuntu8 0
            500 http://us.archive.ubuntu.com jaunty/main Packages

apt-cache policy abiword
      Installed: 2.6.6-0ubuntu1
      Candidate: 2.6.6-0ubuntu1
      Version table:
     *** 2.6.6-0ubuntu1 0
            500 http://us.archive.ubuntu.com jaunty/main Packages
            100 /var/lib/dpkg/status

apt-cache policy xserver-xorg-video-radeon
      Installed: 1:6.12.1-0ubuntu2
      Candidate: 1:6.12.1-0ubuntu2
      Version table:
     *** 1:6.12.1-0ubuntu2 0
            500 http://us.archive.ubuntu.com jaunty/main Packages
            100 /var/lib/dpkg/status

video card: ATI Technologies Inc RS482 [Radeon Xpress 200M]

grep 'radeon' /var/log/Xorg.0.log:
    (II) Matched radeon from file name radeon.ids
    (==) Matched radeon for the autoconfigured driver
    (II) LoadModule: "radeon"
    (II) Loading /usr/lib/xorg/modules/drivers//radeon_drv.so
    (II) Module radeon: vendor="X.Org Foundation"

system memory: 2 GB with 128 MB used by video card

Revision history for this message
David Adam (zanchey) wrote :

Upstream bug: http://bugzilla.abisource.com/show_bug.cgi?id=12066 and https://bugs.freedesktop.org/show_bug.cgi?id=19353

RH bug: https://bugzilla.redhat.com/show_bug.cgi?id=478564

http://bugzilla.abisource.com/show_bug.cgi?id=12066#c11 suggests this is less of a problem with Karmic Alpha 3. Has anyone who sees this issue upgraded to Karmic? If so, perhaps you could let us know whether the issue is still present.

Bug Watch Updater (bug-watch-updater)
Changed in fedora:
status: Unknown → In Progress
Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
David Adam (zanchey) wrote :

I can't reproduce this issue in Karmic.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Upstream AbiWord bugzilla marked it invalid as a bug in both ATI and Intel video drivers. Comment #4 above from the original reporter states that AbiWord 2.6.6+ fixed this bug report for him. Karmic final release did include updated intel video drivers.

I am marking this bug report fix released based on this information.

Changed in abiword (Ubuntu):
status: Confirmed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in abiword:
status: Unknown → Invalid
Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Bug Watch Updater (bug-watch-updater)
Changed in fedora:
status: In Progress → Won't Fix
Bug Watch Updater (bug-watch-updater)
Changed in abiword:
importance: Unknown → Medium
Bug Watch Updater (bug-watch-updater)
Changed in fedora:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.