Solene Rapenne <sol...@perso.pw> wrote:
> on amd64/current, when starting gromit it produces a core dump.
>
> egdb backtrace reports this, kdump did not showed anything useful.
>
> #0 0x0000111993b96dbe in IA__gdk_cursor_new_from_pixmap
> (source=0xffffffffe5a06aa0, mask=0xffffffffe5a06ad0, fg=0x11198b62bf70,
> bg=0x1119397a9960, x=14, y=14) at gdkcursor-x11.c:376
> 376 gdkcursor-x11.c: No such file or directory.
> (gdb) bt
> #0 0x0000111993b96dbe in IA__gdk_cursor_new_from_pixmap
> (source=0xffffffffe5a06aa0, mask=0xffffffffe5a06ad0, fg=0x11198b62bf70,
> bg=0x1119397a9960, x=14, y=14) at gdkcursor-x11.c:376
> #1 0x0000111697f06c31 in ?? ()
> #2 0x0000111697f079ab in ?? ()
> #3 0x0000111697f04056 in ?? ()
> #4 0x0000000000000000 in ?? ()
while it produce a core dump, the program doesn't even seem to respect its
flag.
README says:
However: The window does not hide, if you erase everything with the eraser
tool, you have to clear the screen explicitely with the "gromit --clear"
command or hide Gromit with "gromit --visibility".
solene@t480 ~ $ gromit --visiblity
Unknown Option: "--visiblity"
Please see the Gromit README for the correct usage
solene@t480 ~ $ gromit --clear
Unknown Option: "--clear"
Please see the Gromit README for the correct usage
It has not been updated since 2004.
I propose its removal if nobody wants to fix it.
