Description of problem: The top inch or so of the abiword main screen (that is, the "document page") flickers excessively, making it unusable. Version-Release number of selected component (if applicable): abiword-1:3.0.1-4.fc23.x86_64 How reproducible: always Steps to Reproduce: 1. start abiword 2. type a word Actual results: The top inch or so of the "page" flickers. Expected results: No flickering. Additional info: Starting abiword, the initial blank "page" does not flicker. But as soon as a word is typed, it starts flickering. This occurs both when the abiword screen is maximized, and when it is not maximized. Opening an existing document causes instant flickering. The flickering "rolls" from top to bottom.
I am also having this issue. Has this really not moved since December?
In addition to what Don says, opening an existing document will start the flickering. (In reply to Don Swaner from comment #0) > Description of problem: > The top inch or so of the abiword main screen (that is, the "document page") > flickers excessively, making it unusable. > > Version-Release number of selected component (if applicable): > abiword-1:3.0.1-4.fc23.x86_64 > > How reproducible: > always > > Steps to Reproduce: > 1. start abiword > 2. type a word > > Actual results: > The top inch or so of the "page" flickers. > > Expected results: > No flickering.
My abiword version is 3.0.1-10.fc23
Also occurs Fedora 24 per https://bugs.sugarlabs.org/ticket/4915 where an underlying cause was repeating draw signal from the Abi.Widget. Also occurs Ubuntu 16.04 per https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1574278 where workarounds using Gtk theme were described.
http://bugzilla.abisource.com/show_bug.cgi?id=13791
Upstream maintainer here. I have been using Fedora since Fedora 14 and never seen that issue. Be it on the packaged version (I just tried again) or upstram compiled from source. Using the default Adwaita theme in GNOME. We are gonna need more details on what could be a contributing factor to the problem.
Flickering still happening in F23: abiword-3.0.1-10.fc23.x86_64 ----------------------------------- Flickering does NOT happen in F24: abiword-3.0.1-10.fc24.x86_64 Using mate-desktop. Using Nouveau. Have been using abiword for many Fedora releases. Never experienced this problem until F23. Problem goes away in F24.
As per comment 4 and Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1574278, if you change the desktop theme to Adwaita, the flickering goes away. All of the MATE desktop themes cause flickering for me (in F23) except for Adwaita and the High Contrast theme with the brown folder. (Note that my Adwaita theme is semi-broken, in that it complains that "This theme will not look as intended because the required window manager theme 'Adwaita' is not installed.")
(In reply to Don Swaner from comment #8) > As per comment 4 and Ubuntu bug > https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1574278, if you > change the desktop theme to Adwaita, the flickering goes away. All of the > MATE desktop themes cause flickering for me (in F23) except for Adwaita and > the High Contrast theme with the brown folder. (Note that my Adwaita theme > is semi-broken, in that it complains that "This theme will not look as > intended because the required window manager theme 'Adwaita' is not > installed.") And what window manager do you use then?
See Fedora Forum http://forums.fedoraforum.org/showthread.php?t=309946 for a discussion and fix re Adwaita theme and MATE desktop: "select Adwaita, then click customise. change the window border to anaconda. then click to save the theme and give it the name Adwaita." This fix gets rid of the Adwaita warning message and also fixes the Abiword flicker.
So, I installed MATE Desktop and I couldn't reproduce. (but it definitely wreaked some havoc)
I have an older PC: 1 CPU: AMD Athlon(tm) 64 Processor 3500+ smpboot: Total of 1 processors activated (4409.13 BogoMIPS) NOUVEAU(0): Chipset: "NVIDIA NV4E" and only 2G of memory. Even if I close all windows except Abiword, I still get the flickering, so the problem isn't memory. Perhaps under F23 there just isn't enough CPU cycles with all the usual system processes going on? Perhaps the F24 system is better optimized so there isn't any flickering (on my machine)? In comment 4, the bug described at https://bugs.sugarlabs.org/ticket/4915 references the Gnome desktop, and in the other link: https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1574278, indicates flickering with LXDE and Openbox desktops. So the problem has been observed on at least 4 different desktops, and multiple Linux distros. Maybe "older machine" is the commonality?
In F24, even if a kernel compile is running (using kcbench), so that CPU usage is 100%, there is not any flickering with abiword, which would go to show that the problem with abiword flickering in F23 is NOT due to my older machine.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Still happenning even in F25 since upstream bug hasn't been closed.
As noted in comment 13, the abiword flickering problem for me personally ended with F23. As far as I am concerned, the bug was fixed with F24. It may have had to do with a kernel release. If you need to keep this bug open for some other reason, fine.
See bug https://bugzilla.redhat.com/show_bug.cgi?id=1398773 - F25 has a flickering problem, but different symptoms than this bug.
abiword-3.0.2-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-d2e43d0928
abiword-3.0.2-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ea95a6a39f
abiword-3.0.2-2.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-673afe7e75
abiword-3.0.2-2.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-564152f164
abiword-3.0.2-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-564152f164
abiword-3.0.2-2.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-673afe7e75
Hub I can confirm here the black screen is still there on at least Fedora 25 with 3.0.2 on Xorg just opening up Abiword to a new blank doc. More details from others in the updates: F-24: https://bodhi.fedoraproject.org/updates/FEDORA-2016-673afe7e75 F-25: https://bodhi.fedoraproject.org/updates/FEDORA-2016-564152f164 Let me know if there's patches you would like me to test.
black screen is another bug we already know about upstream. Introduced with Gtk 3.22. The flickering hasn't been fixed, yet it is not reproducible in all configurations.
(In reply to Hubert Figuiere from comment #25) > black screen is another bug we already know about upstream. Introduced with > Gtk 3.22. The flickering hasn't been fixed, yet it is not reproducible in > all configurations. what is the upstream bug for the black screen? Is there an upstream bug for the flickering?
Black screen http://bugzilla.abisource.com/show_bug.cgi?id=13791 (works fine with Gtk 3.20 - so F24 should be safe - or a flatpak with the proper runtime) Flickering is http://bugzilla.abisource.com/show_bug.cgi?id=13791 To reproduce here I have to run in Xnest.
ok. cut & paste glitch. Black screen is actually http://bugzilla.abisource.com/show_bug.cgi?id=13815 Flickering is http://bugzilla.abisource.com/show_bug.cgi?id=13791 Sorry about that.
The prior 3.0.1 version was working well for me in fc24 (except for black ruler-but I can live with that ok) but this version introduces an approx 1 cycle per second flickering of the display. It did fix black ruler in 3.0.1, but I am going to revert back from 3.0.2
I never had the problem on Fedora until I tried in Xnest, that is run in Wayland, so I'm still curious which config causes it. The black screen was just fixed upstream and will be in 3.0.3. Albeit not sure when I'll release 3.0.3. I'll try soon, but I'd love to have this bug fixed too, once and for all.
> The black screen was just fixed upstream and will be in 3.0.3. Albeit not I'm happy to pull in patches if you provide git references or links.
See bug 1390020 comment 8
abiword-3.0.2-3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ffbf1200ab
abiword-3.0.2-3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca183cdc57
I just tried 302-3-fc25 and the screen was black until I clicked in it. After that the screen was white but flickered. Ruler is white btw. I can try it on fc24 when I get home tonight. For the time being I have reverted to 301.
abiword-3.0.2-3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ffbf1200ab
abiword-3.0.2-3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ca183cdc57
abiword-3.0.2-3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
The problem still persists for me with abiword-3.0.2-3.fc24. The top inch or so of the screen flickers for about 10 seconds when: abiword is started; the page is clicked on; text is entered; page up to top of document. For me abiword-3.0.2-3.fc24 is unusable. abiword-1:3.0.1-10.fc24.x86_64 works fine for me. My hardware: Computer: Compaq Presario CPU: AMD Athlon(tm) 64 Processor 3500+ System Memory: 2GiB Video: GeForce 6150 LE, NVIDIA Corporation, driver nouveau
There was never any claim this one was fixed upstream. This bug should be reopen.
abiword-3.0.2-3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
Problems still persist for abiword-3.0.2-3.fc25. Same symptoms as F24. Mate desktop environment for both F24 and F25. A couple of issues with F25 have been temporarily solved for me by turning off hardware acceleration (for the nouveau driver). However, the abiword flicker still occurs with or without hardware acceleration.
(In reply to Hubert Figuiere from comment #40) > There was never any claim this one was fixed upstream. This bug should be > reopen. Was going to once all the updates are through bodhi else it just overrides it.
I have attached a patch on the upstream bug. If somebody could test it before we commit to it. That will warrant a 3.0.3 release is this works. Thanks !
F-25 scratch build here https://koji.fedoraproject.org/koji/taskinfo?taskID=17021918
Thanks. Tested F-25 as installed from workstation media, first with abiword-3.0.2-3.fc25 installed with dnf, and then scratch build abiword-3.0.2-3.1.fc25 and libabiword-3.0.2-3.1.fc25 installed with rpm. No change to observed symptoms. High CPU load; one core at 100%, rapid flicker of text insertion cursor. Draw callback test program from http://bugzilla.abisource.com/show_bug.cgi?id=13791#c14 showed continuous __draw_cb lines.
The black flickering is gone on my F25 installation but now some smaller white flickering is happening and GNOME Screen recording (Shift+Ctlr+Alt+R) did not capture it.
Has anyone got anywhere with this bug?
https://bbs.archlinux.org/viewtopic.php?id=176663 notes that this is probably attributable to the windowing toolkit: gtk+ I get no flickering with something like this: export NO_AT_BRIDGE=1 ; abiword srgc-TEMPLATE-lease-ALL.doc There is a test set of code in comment at https://bugzilla.abisource.com/show_bug.cgi?id=13791 [herrold@centos-7 test]$ vi gtk-test.sh [herrold@centos-7 test]$ chmod 755 gtk-test.sh [herrold@centos-7 test]$ ./gtk-test.sh Traceback (most recent call last): File "./gtk-test.sh", line 3, in <module> import gi ImportError: No module named 'gi' ad as the needed Python 3 module is not present on my box, I re-set to run with Python (2) [herrold@centos-7 test]$ vi gtk-test.sh [herrold@centos-7 test]$ ./gtk-test.sh ** (gtk-test.sh:6048): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. __draw_cb cr=(0.0, 0.0, 250.0, 250.0) __draw_cb cr=(229.0, 5.0, 16.0, 240.0) [herrold@centos-7 test]$ cat gtk-test.sh #!/usr/bin/python import gi gi.require_version('Abi', '3.0') from gi.repository import Abi gi.require_version('Gtk', '3.0') from gi.repository import Gtk def __draw_cb(widget, cr): print('__draw_cb cr=%r' % cr.copy_clip_rectangle_list()) win = Gtk.Window(title="PyAbiword") Abi.init([]) widget = Abi.Widget() widget.connect('draw', __draw_cb) win.add(widget) win.connect("delete-event", Gtk.main_quit) win.show_all() Gtk.main() ---------- snip ------------
It may be sensible to put this reproducer into a separate bug for gtk+, and note it here
interestingly the inability to connect to the dbus (there is one running here) seems to be a failure of permissions down in glib [357979.827469] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [358579.182509] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [358641.751116] abiword[5653]: segfault at 0 ip 00007fc02489e82d sp 00007ffc984e6980 error 4 in libglib-2.0.so.0.4600.2[7fc02484a000+134000] [358654.274206] abiword[5654]: segfault at 0 ip 00007f688aeb982d sp 00007ffce5446210 error 4 in libglib-2.0.so.0.4600.2[7f688ae65000+134000] [358681.837656] abiword[5667]: segfault at 0 ip 00007fa0509f282d sp 00007ffca49352a0 error 4 in libglib-2.0.so.0.4600.2[7fa05099e000+134000] [358781.846179] abiword[5684]: segfault at 0 ip 00007f9d1281782d sp 00007fff44331570 error 4 in libglib-2.0.so.0.4600.2[7f9d127c3000+134000] [358787.534055] abiword[5685]: segfault at 0 ip 00007f6ec0cfd82d sp 00007ffea4851130 error 4 in libglib-2.0.so.0.4600.2[7f6ec0ca9000+134000] [359179.843690] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [359239.463505] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
As author of that reproducer ... NO_AT_BRIDGE has no effect, it still reproduces for me.
This is happening to Fedora 26, Xfce spin. I've noticed when the text input cursor is blinking the screen flicks at the same pace. After a while, once the text input cursor stops, the screen flickering does it too. I'm using Arc theme but tested it with Adwaita and Greybird but the issue still happens. running 'abiword --verbose=2 File' doesn't display anything. Is there something else that can be done to help fixing this issue? Thanks.
Abiword is pretty quiet upstream, no posts to the dev mailing list this year [1], ultimately we're awaiting upstream dealing with this. At this point Abiword is close to dead upstream so it's very much take it as it is. [1] https://www.abisource.com/mailinglists/abiword-dev/
I am upstream (one of the only two committers in the last year). If you want to help fixing the issue, you can provide a patch (I know what has to be done but it is non trivial), or you can find a way for the maintainer(s) to have more free time to commit to AbiWord.
Yay, I think I've fixed it. Please see patch on Abisource 13791, or http://dev.laptop.org/~quozl/z/1diDDl.txt
*** Bug 1450574 has been marked as a duplicate of this bug. ***
(In reply to Gerardo Rosales from comment #53) > This is happening to Fedora 26, Xfce spin. I've noticed when the text input > cursor is blinking the screen flicks at the same pace. > > After a while, once the text input cursor stops, the screen flickering does > it too. > > I'm using Arc theme but tested it with Adwaita and Greybird but the issue > still happens. > > running 'abiword --verbose=2 File' doesn't display anything. Is there > something else that can be done to help fixing this issue? > > Thanks. This is also happening to me on Fedora 26 using Xfce. Nothing has changed to fix this problem since it first arose on Fedora 25. I haven't tried a non-Xfce desktop to see if that improves things.
there is a patch waiting upstream at: http://bugzilla.abisource.com/show_bug.cgi?id=13791 I have not had time to test locally yet there is the suggesting in that thread that changing the theme underneath also mitigates the flicker
The patch waiting upstream continues to work fine for me. Changing the theme, making other applications busy, doing kernel compiles, enabling or disabling compositing window manager, typing, or even waving the mouse around can have an effect on this problem. It is a race condition between a 10ms application timer and GTK+ drawing. Changing the theme can increase the time to draw, and so for some people fixes the flickering.
This patch break on Wayland. see comments on the upstream bug.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora 'version' of '25'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
*** Bug 1521056 has been marked as a duplicate of this bug. ***
abiword-3.0.2-6.fc26.i686 in Fedora 26 LXDE also suffers from this issue. Just in case it helps.
@ fedora yeah .. see comment #61, and #60 I tried a manual build, in advance of a new release cut upstream, and the instructions upstream are so stale as to be not useful I have on my 'want to do' list, decomposing new ones out of the .spec file, but had not gotten to it yet, with the thought of doing a git CO to current, rolling a tarball, and seeing if I could diverge with an interim candidate to test. Please feel free to give that a try and report results, as well Thank you
(Just adding myself to the CC list, I've been encountering this on Fedora 27.)
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
I am seeing this on Abiword x86_64 3.0.2-8.fc27 running on Fedora 27 LXDE using Adwaita. I tried all available themes and it flickers in all cases. My fedora is running as a guest in a VirtualBox with 3D acceleration enabled, but no other apps exhibit this behavior. Unloading plugins makes no difference.
This bug is fixed for me: abiword-3.0.2-8.fc27.x86_64 works fine for me on a Gnome Wayland desktop with Intel graphics, on bare metal. Abiword also works fine on an up-to-date F27 Xfce desktop on the same hardware. Not sure which release fixed it for me.
Thanks maharvey67. Yes, it is unique to AbiWord; the problem is in how events are handled within AbiWord. Thanks Don. That it works for one person is not unusual; it is a timing race condition that depends on when an expose event arrives relative to when a redraw is requested. Also, a slightly different code path is exercised for Wayland vs X11, and a compositor will hide the flicker, with increased CPU load as the only evidence. As you first pointed out, "older machine" is a correlating symptom, but it also happens on virtual machines. There's a fixed 10 millisecond timer in the code; and so the results vary by machine speed.
The upstream Abiword bug report is now marked fixed, as various related changes have been pulled into the ABI-3-0-0-STABLE branch in the last two months. There's also a Flatpak available for testing.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 EOL if it remains open with a Fedora 'version' of '28'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.