Originally reported via forums thread: https://forums.mageia.org/en/viewtopic.php?f=7&t=10575 Two issues that are linked and related to the GTK color selector. When trying to change the background color via menu Format > Page Background > Page Color and clicking on any color with the mouse and OK, background color will not be changed. This is because the color selection is reportedly broken, color needs to be selected either with enter or space key, and then abiword will crash with a segfault. This is known upstream: http://bugzilla.abisource.com/show_bug.cgi?id=13638 and also mentioned in the Changelog for 3.0.1: > Gtk Background Dialog: properly get the color on close with the new color chooser widget. Cherry-pick from trunk@35029 (Hubert Figuière) > Gtk Dialogs Background and options: fix the color chooser. (Hubert Figuière) > Gtk option dialog: fix the color selector for gtk3: We instantiate it manually instead of doing it in the UI file. This diverge from trunk. (Hubert Figuière) Verified already that this is fixed in abiword 3.0.1 which should be pushed as an update to mga5. Reproducible: Steps to Reproduce:
URL: (none) => http://bugzilla.abisource.com/show_bug.cgi?id=13638CC: (none) => doktor5000
(In reply to Florian Hubold from comment #0) > Originally reported via forums thread: > https://forums.mageia.org/en/viewtopic.php?f=7&t=10575 > > > Two issues that are linked and related to the GTK color selector. > When trying to change the background color via menu Format > Page Background > > Page Color and clicking on any color with the mouse and OK, background > color will not be changed. > > This is because the color selection is reportedly broken, color needs to be > selected either with enter or space key, and then abiword will crash with a > segfault. > > This is known upstream: http://bugzilla.abisource.com/show_bug.cgi?id=13638 > and also mentioned in the Changelog for 3.0.1: > > > Gtk Background Dialog: properly get the color on close with the new color chooser widget. Cherry-pick from trunk@35029 (Hubert Figuière) > > Gtk Dialogs Background and options: fix the color chooser. (Hubert Figuière) > > Gtk option dialog: fix the color selector for gtk3: We instantiate it manually instead of doing it in the UI file. This diverge from trunk. (Hubert Figuière) > > > Verified already that this is fixed in abiword 3.0.1 which should be pushed > as an update to mga5. > > Reproducible: > > Steps to Reproduce: Update pushed to core/updates_testing . Florian, can you write an advisory? The version is 3.0.1 with 1.1 (%mkrel 1 and subrel 1).
Assignee: shlomif => qa-bugs
(In reply to Shlomi Fish from comment #1) > Florian, can you write an advisory? Sure, here goes suggested advisory: ======================== In abiword versions prior to 3.0.1, when trying to change the background color via the menu Format > Page Background > Page Color and clicking on any color with the mouse, then OK, the background color will not be changed. This is because the color selection dialog was broken, the color would have needed to be selected either with enter or space key, and then abiword would crash with a segmentation fault. This update fixes both issues. References: http://bugzilla.abisource.com/show_bug.cgi?id=13638 http://www.abisource.com/changelogs/3.0.1.phtml https://bugs.mageia.org/show_bug.cgi?id=17349 ======================== Updated packages in core/updates_testing: ======================== i586 abiword-3.0.1-1.1.mga5.i586 abiword-devel-3.0.1-1.1.mga5.i586 python-abiword-3.0.1-1.1.mga5.i586 x86_64 abiword-3.0.1-1.1.mga5.x86_64 abiword-devel-3.0.1-1.1.mga5.x86_64 python-abiword-3.0.1-1.1.mga5.x86_64 Source RPMs: abiword-3.0.1-1.1.mga5.src.rpm
Status: NEW => ASSIGNED
As I'm not the packager this time, I can confirm (again) that the update to abiword-3.0.1-6.mga5.x86_64.rpm fixes both mentioned issues, the crash and the color selector in general. Background color can now be changed as expected \o/ Only other thing I noticed is that when selecting text, the highlighting of the selected text is in black - vs. black text, which is a pretty bad choice. But not related to the update, 3.0.0 shows the same issue. Might also simply be a local theming problem.
Whiteboard: (none) => MGA5-64-OK
I can confirm that Florian is correct, the Abiword 3.0.1 package in the core/updates_testing repo fixes the problem. I am the original poster in the the forum thread Florian links to in his bug description.
CC: (none) => jbarntt56
Off topic but just curious about subrel usage. Version is already bigger value than the previous one. So why you used subrel? Release should be enough?
CC: (none) => tarakbumba
(In reply to Atilla ÃNTAÅ from comment #5) > So why you used subrel? Release should be enough? Good point actually, also mentioned in https://wiki.mageia.org/en/Updates_policy#Maintainer_.28or_any_interested_packager.29 But in this particular case, the release in cauldron is already much higher, I don't think this warrants to re-submit the update candidate without subrel (which would also require intervention by sysadmins for manual removal).
Testing on mga5-32 Packages installed from testing: python-abiword-3.0.1-1.1.mga5 abiword-3.0.1-1.1.mga5 Page colour can be changed using the menu with the mouse. (I see the same black on black problem with highlighted text as mentioned in comment #3) OK for mga5-32
Whiteboard: MGA5-64-OK => MGA5-64-OK MGA5-32-OK
This update is now validated. The Advisory needs to be uploaded to SVN. The packages can then be pushed to updates.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
Whiteboard: MGA5-64-OK MGA5-32-OK => MGA5-64-OK MGA5-32-OK advisory
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0213.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED