Comments

39 Comments

Hotspot works if turned on via nmcli, but not via Gnome settings: "System policy prohibits use as a Hotspot".

Test Case NM Ethernet
Test Case NM Gnome Hotspot
Test Case NM nmcli
karma

works

karma

works

BZ#1486924 "info awk" gives broken link "Cannot find node 'Invoking gawk'."
karma

works

BZ#1486924 "info awk" gives broken link "Cannot find node 'Invoking gawk'."
karma

Still gives same error for "info awk".

BZ#1486924 "info awk" gives broken link "Cannot find node 'Invoking gawk'."
karma

"info awk" still gives same error.

BZ#1486924 "info awk" gives broken link "Cannot find node 'Invoking gawk'."
karma

GUI and rpm script work.

BZ#1448623 GUI broken & Error with RPM Script
karma

GUI and rpm scripts both work.

BZ#1448623 GUI broken & Error with RPM Script
karma

Upgrade scripts now work OK. GUI still waiting on upstream fix.

Post install scripts do not show errors. Waiting on upstream fix for GUI.

BZ#1448623 GUI broken & Error with RPM Script
karma

No black screens. Flickering in top 1.5in of screen for 10 sec. when: 1) start abiword; 2) click on screen; 3) enter text; 4) page up to top of doc; 5) open existing doc. Unusable for me. (Xorg)

BZ#1390020 [abiword] text body in abiword turns black all the time, e.g. when losing focus
BZ#1287835 abiword screen flickering
BZ#1398773 Paging up or down causes black screen and flickering - clicking reveals text
karma

Flickering (10 sec - top 1.5 in) and text blanking for newly entered text makes this update unusable for me. Flickering when click on text or refocus or page up to top. No black screens.

BZ#1390020 [abiword] text body in abiword turns black all the time, e.g. when losing focus
BZ#1287835 abiword screen flickering
BZ#1398773 Paging up or down causes black screen and flickering - clicking reveals text
karma

Initial black screen with 15 sec flcikering, followed by black screen. Click on screen results in another 15 sec of flickering followed by black screen. Opening existing doc causes extreme flickering (15 sec) followed by black screen. Totally unusable.

BZ#1287835 abiword screen flickering
BZ#1390367 black window after start
karma

Before this update, abiword worked fine for me on F24. Now there is temporary (15 sec) flickering when at top of doc, or when save is done. With a new doc, the text blanks in and out, making it pretty much unusable.

BZ#1287835 abiword screen flickering
BZ#1390367 black window after start
karma

Started mediawriter-4.0.7-0.fc24; plugged in USB containing live iso; got dialog box re restore; system completely hung; required manual forced cold boot.

BZ#1396839 mediawriter abends with SIGABRT after Live iso USB insertion

Still abends with SIGABRT. Info box displayed shows process got further than with mediawriter-4.0.0-2.fc24.x86_64

BZ#1396839 mediawriter abends with SIGABRT after Live iso USB insertion
karma

Works.

No regressions noted.

BZ#1363855 font version change causes fontopia abend and trashes keyboard
BZ#1361910 fontopia abends trashing keyboard
karma

Works.

No regressions noted.

Anomaly not previously noted: If while viewing the font metrics for eurlatgr.psfu, the version is switched to BDF, then the number of characters cannot be changed back to 512. The number of characters switches from 512 to 256 while passing through versions CP and RAW. The number of characters can be switched back to 512 if the version is changed to PSF1 or PSF2, but not for BDF.

BZ#1363855 font version change causes fontopia abend and trashes keyboard
BZ#1361910 fontopia abends trashing keyboard

I am unable to get fontopia to read otf2bdf bdf output, even if it is 512 chars. gbdfed reads otf2bdf outputs fine, and mate-font-viewer will preview otf2bdf output. mate-font-viewer will not display bdf files created by fontopia. gbdfed will not read bdf files created by fontopia. setfont gives the same "Bad input file size" error message with all bdf fonts, regardless of their source. I do not have expertise in this area, and I am unable to get fontopia, otf2bdf, gbdfed, and mate-font-viewer to play nice together. Note that mate-font-viewer doesn't actually allow you to view all the font glyphs, but to view "The quick brown fox ..." in that font.

I'm pretty sure that setfont does not support bdf fonts, so the above bug concerning that should be discarded. I ran otf2bdf on FreeMono.ttf to create FreeMono.bdf. FreeMono.bdf looks very complete, yet setfont still complains with the same error message "Bad input file size", but I believe the message is really saying "this font format is not supported by setfont". (The setfont man page is not completely clear on which formats are supported.) If I understand correctly, the bdf format provides a way to import an X font into a console font format via fontopia, but the bdf format is not itself a console font format.