| 1 |
$LastChangedDate: 2024-05-11 14:46:02 +0200 (Sat, 11 May 2024) $ |
| 2 |
|
| 3 |
==== BUG REPORTING |
| 4 |
|
| 5 |
For sending a bug report, please drop me an email with a subject line beginning with '[FIM]'. |
| 6 |
Contact information is in the doc/FIM.TXT file, or in the bottom of this file. |
| 7 |
|
| 8 |
Please DO NOT dare sending bug reports about installation unless you have read the INSTALL |
| 9 |
file and you are sure all the dependencies on your system have been resolved. |
| 10 |
|
| 11 |
For example "[FIM] problems with resolution 457x3778" would be a good, informative |
| 12 |
subject for me. |
| 13 |
|
| 14 |
When submitting a bug report, please follow the following rules: |
| 15 |
|
| 16 |
- be as much informative as possible when describing your experience. |
| 17 |
- make a report about the current environment: |
| 18 |
( make ; make report ) 2>&1 | gzip > fim.`date +%Y%m%d%H%M`.log.gz |
| 19 |
and send me the created .tgz file |
| 20 |
- please give me information about the exact way you experienced the problem |
| 21 |
- please give me information about the resolution/video mode you are working with; |
| 22 |
from the bash shell, execute the following and send me the output: |
| 23 |
( for f in /sys/class/graphics/fb0/* ; do echo $f ; cat $f ; done ) |
| 24 |
- please send me the config.log file, too (especially if it is a build bug). |
| 25 |
it is of vital importance! |
| 26 |
(the config.log file is created by the configure script when you run the ./configure script) |
| 27 |
- if you are using an ad hoc method for installing (say, the ebuild for the Gentoo Linux ), |
| 28 |
consider sending the logfile created and named in the error messages. |
| 29 |
|
| 30 |
|
| 31 |
==== CORE DEBUGGING |
| 32 |
|
| 33 |
Consider debugging with gdb or letting me do this for you! |
| 34 |
by running |
| 35 |
|
| 36 |
$ ulimit -S -c unlimited |
| 37 |
|
| 38 |
before Fim, in the case Fim should crash, it will generate a file called 'core'. |
| 39 |
That file, if sent to me (but contact me before sending, because it could be big!), |
| 40 |
will be helpful for debugging Fim and discover the causes of the crash. |
| 41 |
|
| 42 |
p.s.: please compile the code configuring in this way: |
| 43 |
( use ./configure --help='-O0 -ggdb' ) |
| 44 |
and don't forget to send me the executable file, too :) |
| 45 |
|
| 46 |
==== CONTACT |
| 47 |
|
| 48 |
You can mail your report to dezperado_FOobAr_autistici_Baz_org, by replacing _FOobAr_ |
| 49 |
with a '@' and _Baz_ with a '.'. |
| 50 |
|
| 51 |
==== KNOWN BUGS |
| 52 |
|
| 53 |
20240402 the search history and the command history are not properly separated |
| 54 |
20240322 if using libcaca (-o ca=W) mode with a version older than pre-0.99.beta20 (like 0.99.beta19), pressing continuously 'n' has been observed to lead to an endless loop |
| 55 |
20240320 in gtk (-o gtk) mode, pressing 'n' continuously has been observed failing to refresh the images along the way |
| 56 |
20240320 in gtk (-o gtk) mode, if terminating via the window system while in the console, --final-commands COMMANDS will not be executed |
| 57 |
20150131 in aalib mode PageUp / PageDown do not seem to work. |
| 58 |
20150123 |
| 59 |
|
| 60 |
When in framebuffer mode, never, for ANY reason, press C-z (^Z) with the |
| 61 |
intention of putting fim in the background. It will blind your console and |
| 62 |
allow only blind typing, which is a very dangerous situation! |
| 63 |
|
| 64 |
20110603 Window splitting is disabled. |
| 65 |
|
| 66 |
==== MINOR ISSUES |
| 67 |
|
| 68 |
20091208 if fim is configured to take input from piped xfig (as xfig-3.2.5b), it could be - passively - subject to |
| 69 |
xfig's buffer overflow on files like: |
| 70 |
0 1 2 3 |
| 71 |
4 |
| 72 |
1 2 3 4 5 6 7 ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ |
| 73 |
( see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559274 |
| 74 |
and http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=xfig_poc.f;att=1;bug=559274) |
| 75 |
As long as xfig (fig2dev) is accessed through the popen() system call, there will be no harm to fim from xfig crash. |
| 76 |
20091015 In 16 bit graphics mode, some lines which should be white actually look blue (seems not fim' fault; happens on both on ARM and x86) |
| 77 |
20091013 fim -i < file.pdf # does not work on potentially multipage files |
| 78 |
20091009 fim does not support 1,2,4 bit modes |
| 79 |
20090328 problems with --std=c++98 in legacy src/FbiStuffJpeg.cpp code (now commented) |
| 80 |
20070919 while command suffers from being not interruptible in some cases (when the image is small and not 'panable') |
| 81 |
20070912 Debugging it with the framebuffer under gdb hangs the console (even with -p). |
| 82 |
20070904 problems could occur with the commands giving output when no std::cout << "" is returned soon after (see Commandconsole.cpp mehods for this..) |
| 83 |
20071128 tried: |
| 84 |
Linux host 2.6.19-gentoo-r5 #1 SMP Mon Sep 24 15:08:36 CEST 2007 ppc 7447A, altivec supported PowerBook5,4 GNU/Linux |
| 85 |
and gave problems with the PAGE_MASK macro, originally in /linux/include/asm-i386/page.h :) |
| 86 |
|
| 87 |
20080504 Seems like running the aalib driver under screen maps -3072 units down the arrow keys. |
| 88 |
I do not see this problem in aalib under ssh. |
| 89 |
20080127 Under screen, Fim behaves well but it doesn't handle well console switching: |
| 90 |
after a console switch, it doesn't redraw the image if not triggered to do so. |
| 91 |
20080106 keys 'Insert,Cancel' are not recognized in the commandline mode. |
| 92 |
This issue will be fixed after the fbi core will be cleaned up and revised. |
| 93 |
20070811 On CENTOS 64 bit, i reported linking problems : -ltermcap is required, too. |
| 94 |
I Don't know exactly how to fix this issue. |
| 95 |
2007* Bugs shared with fbi, not fully solved: |
| 96 |
- do not switch console or interrupt the program while it is busy: it could hang your console |
| 97 |
and force you to make tricks to get back the terminal (like typing blindly through consoles, |
| 98 |
or trying to get to some X instance via ALT-F7-like sequences, or even restart the computer), |
| 99 |
and blind typing could be dangerous, if you do now know what you are doing! |
| 100 |
|
| 101 |
==== OUTSTANDING FIXED ISSUES |
| 102 |
|
| 103 |
20110602 fim versions before svn version r373 segfault in 32 bit framebuffer mode, on 64 bit builds |
| 104 |
|
| 105 |
==== FIXED FBI/FBGS ORIGINATING BUGS |
| 106 |
|
| 107 |
Replaced popen with pipe calls : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=422034, in rev. 213. |
| 108 |
|
| 109 |
Original typo in fbgsh : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3119 fixed following the |
| 110 |
patch indicated on http://bugs.gentoo.org/show_bug.cgi?id=141684 : |
| 111 |
|
| 112 |
-gs -dSAVER -dNOPAUSE -dBATCH |
| 113 |
+gs -dSAFER -dNOPAUSE -dBATCH |
| 114 |
|
| 115 |
It could let a PostScript file execute evil code, according to the advisory. |
| 116 |
|
| 117 |
|
| 118 |
==== UNFIXED EXTERNALLY ORIGINATING BUGS |
| 119 |
|
| 120 |
20090329 On my debian box's aalib, the ASCII art driver leaks 224 bytes of memory. |
| 121 |
Actually, it happens the same when compiling aalib-1.4.0's aafire.c program against debian aalib |
| 122 |
and running it in console mode (no X). |
| 123 |
After clean aalib recompilation, these problems vanish. |
| 124 |
|
| 125 |
==== SOLVED ISSUES |
| 126 |
|
| 127 |
20110712 in sdl (x11) mode, when fim is spawned in a non-terminal environment, the readline mode does not work in the proper way. detecting this situation may be helpful to disable the readline mode at all in these cases, until a readline-centric fix is found. (seems fixed with r688) |
| 128 |
|