Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ncspot window looking corrupted/wrong #556

Closed
AtlasC0R3 opened this issue Jun 21, 2021 · 15 comments
Closed

ncspot window looking corrupted/wrong #556

AtlasC0R3 opened this issue Jun 21, 2021 · 15 comments
Labels
bug Something isn't working

Comments

@AtlasC0R3
Copy link

Describe the bug
So, normally ncspot looks like normal ncurses, clean and straightforward. However, my terminal (Konsole) did not like that.

To Reproduce
Steps to reproduce the behavior:

  1. Open ncspot

Expected behavior
I expected it to not look corrupted-ish, and I know how it's supposed to look like, I had it installed on Debian and it looked just fine, but with Arch Linux, everything looks.. wrong.

Screenshots
image
i dont think thats how its supposed to look like

System (please complete the following information):

  • OS: Arch Linux
  • Terminal: Konsole
  • Version: 0.7.3
  • Installed from: cargo (AUR too, both ncspot and ncspot-git looked like this)

Backtrace/Debug log
stderr.log

error: could not find `Cargo.toml` in `/home/atlas` or any parent directory

To debug crashes a backtrace is very helpful. Make sure you run a debug build of ncspot, e.g. by running the command mentioned in the link above.
(I don't quite think this is going to be very useful...)

Additional context
It's most likely an issue with Konsole. Or Arch.

@AtlasC0R3 AtlasC0R3 added the bug Something isn't working label Jun 21, 2021
@TheSemicolons
Copy link

Same issue on OpenBSD 6.9. The font probably doesn't support some characters being used, but I have no idea what font would.

2021-06-22-102128_683x409_scrot

@AtlasC0R3
Copy link
Author

It doesn't seem like a font-related issue, I tried a bunch of them and they did the same garbled mess thing.
Peek 2021-06-22 12-48

It may be an encoding issue though. Tried XTerm, UXTerm, Yakuake and the tty shell (CtrlAltF*) and they all did the same thing.

@hrkfdn
Copy link
Owner

hrkfdn commented Jun 22, 2021

Hmm, would you happen to know if this also occurs with versions <0.7.x? I wonder if it's because of b80e018

@TheSemicolons
Copy link

localhost$ pkg_info ncspot
Information for inst:ncspot-0.5.0

Comment:
ncurses Spotify client

Description:
Cross-platform ncurses Spotify client written in Rust with
a low resource footprint. The UI is heavily inspired by
ncurses MPD clients, such as ncmpc.

Maintainer: Henrik Friedrichsen henrik@diff.cc

WWW: https://github.com/hrkfdn/ncspot

@AtlasC0R3
Copy link
Author

Tried launching ncspot 0.5.0 and 0.4.0 by launching their *.tar.gz executables, they look equally corrupted.
Here's a screenshot of 0.4.0:
image

Oh by the way, the screenshots I sent previously are all running on the latest AUR version, which I believe is the latest available.

@hrkfdn
Copy link
Owner

hrkfdn commented Jun 23, 2021

Then the change I mentioned is not related. What locale are you using? What is TERM set to? I use LANG=en_US.UTF-8 and have no problems on OpenBSD with rxvt-unicode or GNOME-Terminal on Debian.

@TheSemicolons
Copy link

localhost$ echo $TERM
xterm
localhost$ echo $LANG

localhost$

Looks like LANG isn't set by default in OpenBSD. When I set it with export LANG="en_US.UTF-8" and then run ncspot it works.

@AtlasC0R3
Copy link
Author

My TERM variable was also set to xterm, although I had xterm-256. Changing the lang variable didn't do anything, although it is already set to en_CA.UTF-8 by default.

@TheSemicolons
Copy link

The API for Spotify was having issues yesterday. I confirmed today with ncspot-0.5.0 on OpenBSD using export LANG="en_US.UTF-8" then running ncspot works in both xterm and st-256color.

2021-06-24-130837_564x364_scrot

@rabfel-hobmet
Copy link

just did a fresh arch install and i'm having this issue. didn't have it on kde neon or manjaro. does look to be something with the LANG. once i set that i'll be back to let you all know if that fixed it. i'm having trouble figuring that out though, lol.

@rabfel-hobmet
Copy link

yeah, it was language issues. if you run: locale and see that it's showing "C" instead of your locale, just start following the crumbs or message me. once you get it to show your locale, it works perfect. :)

@AtlasC0R3
Copy link
Author

AtlasC0R3 commented Sep 3, 2021 via email

@Bettehem
Copy link
Contributor

Bettehem commented Sep 3, 2021

You should enable at least en_US.UTF-8 as instructed in the Arch Linux Installation guide.
If en_US.UTF-8 isn't enabled apps can misbehave.

@rabfel-hobmet
Copy link

Good to know it's an Arch related issue. I don't think I set my Lang variables properly either, I'll check that when I can. Thanks!

yes, it's from not setting the locale correctly. it wasn't too bad to fix. I think this issue can be closed. message me if you need links.

@AtlasC0R3
Copy link
Author

Yep, confirmed. export LC_ALL="en_CA.UTF-8" fixed the app. Thanks a lot!
Now I'll just need to figure out how to make LC_ALL default to that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants