Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#51667 - [abiword] Text area not readable

Attached to Project: Arch Linux
Opened by Jack Random (jackrandom) - Thursday, 03 November 2016, 07:44 GMT
Last edited by Jan de Groot (JGC) - Thursday, 22 December 2016, 11:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
Abiword displays documents as transparent/black background with GTK 3.22.

Additional info:
* package version(s)
abiword: 3.0.2-1
gtk3: 3.22.2+4+gc54f348-1
gnome-shell: 3.22.1+2+g5a08886-1

* config and/or log files etc.
tested on freshly installed system

* Steps to reproduce:
- open Abiword with Gnome 3.22 installed. bug occurs with every theme (also Adwaita)

* screenshot:
https://imgur.com/a/ZetLH

References:
Bug also filed here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842443
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 22 December 2016, 11:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 3.0.2-3 which is in staging at the moment (libwmf rebuild).
Comment by Olivier (olive) - Friday, 04 November 2016, 09:59 GMT
I can confirm the bug. I have recompiled abiword with

--with-gtk2 --without-goffice

and it works correctly. The gtk3 version always had problems. In the past I had also display problems and flickering like this: https://bbs.archlinux.org/viewtopic.php?id=208900 although it was less severe than now. I think to stick with gtk2 until upstream manages to have a really stable gtk3 version is the thing to do.
Comment by Alex Theotokatos (alex.theoto) - Sunday, 04 December 2016, 07:43 GMT
I get:
Unknown option --with-gtk2
and I have the same problem
Comment by Olivier (olive) - Sunday, 04 December 2016, 08:09 GMT
@alex.theoto the --with-gtk2 is a compile time option (to be passed to the configure script at compile time); not a run-time option you pass to abiword. You have to recompile the package and edit the PKGBUILD. You must also pass --without-goffice; otherwise it does not compile. To make a good package you must also adjust the dependencies accordingly (depend on gtk2 instead of gtk3).

By the way why is this package still broken? As is, this package is unusable; if, for some reason recompiling with gtk2 is unacceptable; then remove this package entirely. We do not know how much time upstream will take to fix this. Anyway, if it does, we can always revert back to gtk3. I don't see the point of shipping a broken, unusable software.
Comment by Alex Theotokatos (alex.theoto) - Sunday, 04 December 2016, 09:02 GMT
Current version is 3.0.2-2 with the same problem. Happens even without gnome desktop.
I'm sorry, you wrote 'recompile'. Bad reading...
Gtk2 does the trick. Though cursor is little unstable, abiword is still functional.
Thanks for your hint.
Comment by Julius-Paul Jann (Nokius) - Monday, 05 December 2016, 14:35 GMT
Can confirm the bug using i3 wm

I have both version of GTK

pacman -Qs gtk
local/gtk2 2.24.31-1
GObject-based multi-platform GUI toolkit (legacy)
local/gtk3 3.22.4-1
GObject-based multi-platform GUI toolkit

pacman -Qs abiword
local/abiword 3.0.2-2
Fully-featured word processor

When moving selecting abiword as window the text field flickers if not it stay black




Comment by Olivier (olive) - Monday, 05 December 2016, 16:04 GMT
@Nokius As I said, the "--with-gtk2" is a *compile time* option. You won't fix the package by installing gtk2 or other things. You need to recompile the package with gtk2; or provide a patch to make it works correctly with gtk3 (which is beyond my competence).
Comment by Kaijie Chen (ckj996) - Friday, 09 December 2016, 05:23 GMT Comment by Olivier (olive) - Friday, 09 December 2016, 09:11 GMT
This patch fixes the problem for me.

Loading...