Comments

39 Comments

The "W" (export font glyphs in textual format) feature goes really well with xxdiff - to compare before and after versions of changes made.

karma

Works.

In the following, fontopia was run in a terminal, not a console, unless otherwise noted:

The eurlatgr.psfu font is psf1. If you convert it to psf2 and save as [new name], exit fontopia, start fontopia on [new name], then convert it back to psf1, you get a message "You chose to change this font length From:512 char To:256 char ..." and if you proceed the font is indeed truncated. However, the original psf1 font had 512 char, so why can't the new psf1?

If font metrics are displayed, and no changes are made, and the OK button is selected, there is an info message at the bottom of the screen: "Applying changes to glyph size", even though there was no change to the glyph size. This spurious message is also displayed if the font version is changed, even though there was no change to the glyph size.

For some fonts in /lib/kbd/consolefonts, while almost all of the glyph matrix displays OK, there are some items for which no glyph is displayed but instead there are 2x2 hex unicodes displayed: Agafari-14.psfu, drdos8x16.psfu, drdos8x6.psfu, Goha-14.psfu, GohaClassic-12.psfu, greek-polytonic.psfu, niCyr_8x16.psf, UniCyrExt_8x16.psf, viscii10-8x16.psfu - there may be others. Also, for the first glyph in eurlatgr.psfu, in the glyph matrix, the symbol displayed is a filled in hexagon with a reversed question mark in the center. Why the two different glyph representations for "unknown unicodes"?

If the font type is changed to bdf, even if bdftopcf converts the font (to pcf) OK, "setfont [font].bdf" complains "Bad input file size".

When viewing the unicode table ("U"), ESC must be pressed twice to exit. (This is in a terminal - in a console ESC only needs to be pressed once.)

MINOR COSMETIC BUG: I use green on black terminal colors. After running fontopia, the colors have been changed to white on black, and the terminal must be reset to restore the color scheme.

If you do a "save as" (CTRL+D), and you change your mind about saving, or hit CTRL+D by mistake, you must press ESC twice to cancel. (This is in a terminal - in a console ESC only needs to be pressed once.)

THIS IS NOT A BUG: some fonts give "unknown font format" error: koi8r-8x14, cp857.14 - there may be others.

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

If fontopia is executed in a terminal on font ter-v32n, if the terminal font is set too large, an error message results: "Can't display glyph. Font metrics (weight or height) larger than screen size." [Should that be "width" instead of "weight"?] In order to clear the error message, ENTER must be pressed twice, instead of once. If the terminal font size is reduced, then fontopia runs as expected.

If fontopia is executed in a console on font ter-v32n, after a "setfont ter-v32n" has been done, an error message results: "Error: Font height is larger than screen height." If however, a "setfont ter-v16n" is done first, and then "fontopia ter-v32n" is run, then fontopia functions as expected, and the font display matrix on the right hand side shows correct glyphs.

karma

Works.

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

Works.

161.cp contains 3 fonts, as setfont informs the user. Executing "fontopia 161.cp", only the size 16 font is visible. If the 16 font is changed and saved, it works, but the user cannot view or change the size 8 or size 14 fonts also included in 161.cp.

If fontopia is used to change the font version of default8x16.psfu to bdf (default8x16.bdf), and the resultant bdf file is input to bdftopcf, 2 errors result: 1) no font name is specified; 2) the linecount on the STARTPROPERTIES is wrong.

The show keys display has garbage on the bottom of the screen.

While running fontopia in a console, it isn't possible to switch consoles (CTRL+ALT+F3, etc does not work).

If fontopia is run in a console, the font matrix displayed in the upper right of the screen will not be correct if the console font is not set to the font being edited before starting fontopia. When running fontopia in a terminal, if the type font is code page, then the font matrix displayed may not be correct.

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

Mostly works. dnf upgrade does not pull in upgraded gnudos. However, new problem: Export unicode table does not work for fonts ter-v32n.psf, default8x16.psfu - causes abend. Unicode table displays OK for these 2 fonts, but with some truncated long lines. Export unicode table works for font ter-124b.psf. Abends trash keyboard which on my machine may be recovered from by holding down left super/win key and then hitting 2 key and 3 key in rapid succession.

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

Works. dnf upgrade did not see dependency on upgraded gnudos. Looking very functional. Minor quibbles: editing 24x12 fonts works, but changing version does not (size is changed when version is changed - unable to reset size back to 24x12). When changing sizes, one might hope for some automatic "best guess" scaling, to be adjusted by hand later, but there is no scaling.

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

Works

BZ#1354191 Logout mate session throws Gtk-CRITICAL error in journal

Works

BZ#1354191 Logout mate session throws Gtk-CRITICAL error in journal
karma

Works for me.

BZ#1361910 fontopia abends trashing keyboard
karma

Works for me

BZ#1361910 fontopia abends trashing keyboard

aborts now properly caught by abrt-hook-ccpp

BZ#1305083 SELinux is preventing abrt-hook-ccpp from 'getattr' accesses on the file file.
karma

bug is fixed

BZ#1306413 [abrt] nano: main(): nano killed by SIGSEGV

fixes bug 1278415

karma

Lock message PID is now correct.

karma

File lock is now cleared after read into.

karma

bug is fixed. Thanks.