clangen / musikcube

a cross-platform, terminal-based music player, audio engine, metadata indexer, and server in c++
https://musikcube.com
BSD 3-Clause "New" or "Revised" License
4.2k stars 295 forks source link

Segmentation fault in Kitty terminal #572

Open xavier-balesi opened 1 year ago

xavier-balesi commented 1 year ago

Impossible to launch musikcube in kitty terminal.

Config:

POT image

But it works well under the builtin ubuntu terminal (also tested with success in tmux).

clangen commented 1 year ago

Hmm, weird. I tried kitty v0.26.5 on both Linux and macOS and it seems fine. Can you let me know which shell you're using, and if possible, your environment variables? Most useful would be LC_ALL, LC_CTYPE and LANG, but a full dump from env would be preferred -- just make sure you audit them before pasting them here so you don't expose any sort of sensitive information.

xavier-balesi commented 1 year ago

My shell : GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) LC_ALL and LC_CTYPE are not defined (neither in kitty nor in builtin term)

Here is the filtered dump of my env : dumpenv.txt

Thanks

xavier-balesi commented 1 year ago

OK playing around with the environment variables I managed to launch musikcube with TERM=xterm-256color instead of TERM=xterm-kitty

adhyuthn commented 1 year ago

That works but it breaks the icat functionality

lampdog commented 1 year ago

Ok, I was having some similar issue. Actually, musikcube simply wasn't working on kitty terminal, not returning anything. Like @xavier-balesi said, it was working on other terminals on the same system. Sad times. Then, I've crossed with another problem in kitty: some sudo commands not working, like using nano the change the files /usr/share/applications/*.desktop. So I found this page. I made the procediment, and now musikcube is working on kitty. It seems the problem was not with musikcube, but with kitty. I'm using Pop_os 22.04.

Ps. I don't think it's nice to mess with environment variables. Can lead to other problems.