search

adrianlopezroche / fdupes

FDUPES is a program for identifying or deleting duplicate files residing within specified directories.
2.42k stars 186 forks source link

Can't type return when inside the fdupes terminal screen #174

Open Sciamano72 opened 1 year ago

Sciamano72 commented 1 year ago

Hello, I have installed fdupes in my Linux Mint 21.1 installation using ubuntu repositories (I've always done it this way). Package version 1:2.1.2-1build1. Now, whenever I launch fdupes I can never choose what file to keep because I can't send the enter command: I hit the return key (which works perfectly when "outside" fdupes) but nothing happens. Same thing happens when I try to exit the program: I type 'exit' but can't send the command because the return key is not working. WTH?

adrianlopezroche commented 1 year ago

I'm not sure what it could be. To fdupes the enter key is just a newline character, so I figure it should work unless maybe there's something wrong with the terminfo mappings or the latest ncurses library on Linux Mint 21.1? I'm using an older version of Mint, so I can't test it myself. You could try running fdupes with the --plain parameter as a workaround while the problem is discovered.

Sciamano72 commented 1 year ago

I have no idea, if you give me more info on how to check the mappings I will gladly do my best to help. In the terminal I can't even exit by using CTRL+C, but it only happens in fdupes (using nano all the CTRL+key combinations work). Anyway I was able to check for duplicates using the --plain parameter, thanks for the suggestion.

adrianlopezroche commented 1 year ago

I know very little about terminfo so I'm afraid I can't help there. I'm hoping someone will see this who can help, but I think your best option will be to file a bug report with the Linux Mint folks and see if they can figure it out.

Sciamano72 commented 1 year ago

I understand. At least I can use the --plain parameter and still make fdupes work. Anyway I will file a bug report @ Linux Mint and see what happens. I'm startled by the fact that it looks like no one else is affected by this problem, though!