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

alpinelinux UART serial - broken rendering #25

Open
coelner opened this issue Jul 6, 2021 · 4 comments
Open

alpinelinux UART serial - broken rendering #25

coelner opened this issue Jul 6, 2021 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@coelner
Copy link

coelner commented Jul 6, 2021

Describe the bug

rpi_zero:~# gpg-tui 
failed to initialize clipboard: XcbConn(ClosedParseErr)
[Nothing is shown - q closes program]

To Reproduce

run gpg-tui over the UART serial on the alpine linux version on a rpi zero.

Expected behavior

the same output after running it under tmux.

Screenshots/Logs

If applicable, add screenshots or logs to help explain your problem.

System Information

  • OS: [ alpine-rpi-3.14.0 210615]
  • Rust Version: [rustc 1.47.0]
  • GPGME version: [ gpgme-tool 1.15.1]
  • GPGME engine version: [gpg (GnuPG) 2.2.29]
  • Project Version: [e.g. 0.6.0-r0 edge repo]

Additional context

I run this on a rpi zero over the UART serial. Using tmux it works and the keys get shown.
tmux env:

TMUX=/tmp/tmux-0/default,4188,0
USER=root
SHLVL=2
HOME=/root
TERM_PROGRAM_VERSION=3.2
PAGER=less
PS1=\h:\w\$ 
LOGNAME=root
TERM=screen
LC_COLLATE=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.local/bin
LANG=C.UTF-8
TERM_PROGRAM=tmux
SHELL=/bin/ash
PWD=/root
CHARSET=UTF-8
TMUX_PANE=%0

env for the UART shell:

USER=root
SHLVL=1
HOME=/root
PAGER=less
PS1=\h:\w\$ 
LOGNAME=root
TERM=vt100
LC_COLLATE=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/root/.local/bin
LANG=C.UTF-8
SHELL=/bin/ash
PWD=/root
CHARSET=UTF-8
@coelner coelner added the bug Something isn't working label Jul 6, 2021
@orhun
Copy link
Owner

orhun commented Jul 6, 2021

failed to initialize clipboard: XcbConn(ClosedParseErr)

FYI this is normal for non-X11 environments, since copy/paste feature requires X11.

[Nothing is shown - q closes program]

Can you press '?' and share what's shown the bottom right? It seems like $GNUPGHOME is not set (or set to somewhere else) so the keyring is empty. For example:

cap

Also you can compare these values to your working environment. I'm not familiar with the UART serial so I think it's a (shared) keyring problem.


Are you having any other problems about the rendering? Are the other keys work normally or is it completely broken?

@coelner
Copy link
Author

coelner commented Jul 6, 2021

failed to initialize clipboard: XcbConn(ClosedParseErr)
  • FYI this is normal for non-X11 environments, since copy/paste feature requires X11.
GPGME version: 1.15.1                 │
│    └─switch to normal mode          │  GPGME protocol: OpenPGP               │
│                                     │  GPGME engine: "/usr/bin/gpg"          │
│                                     │  GPGME engine version: 2.2.29 (>1.4.0) │
│                                     │  GnuPG home directory: "/root/.gnupg"  │
│ Use arrow keys / hjkl to navigate   │  GnuPG data directory:                 │
│ through the key bindings.           │  "/usr/share/gnupg"                    │
│ Corresponding commands and          │  Output directory: "/root/.gnupg/out"  │
│ additional information will be shown│  Default signing key: not specified   

the $GNUPGHOME is not set, but it does not change anything.

I get a blank screen with the direct call within ash, but after calling tmux the output is visible.Both is about the serial connection.

Due the missing clipboard the I/O is limited (maybe there a way to paste it into the shell buffer/ or disable the menu items)

@orhun
Copy link
Owner

orhun commented Jul 6, 2021

Hmm it's weird. I don't really have the environment to reproduce this issue but feel free to guide me.

I get a blank screen with the direct call within ash, but after calling tmux the output is visible.Both is about the serial connection.

I wonder what does tmux do differently.

I'll research a little bit. It'd be good if you let me know if anything changes.

@coelner
Copy link
Author

coelner commented Jul 6, 2021

No problem, I was just stumpling over this.
[background: the rpi should be a air gap gnupg key generator and master key storage]

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

2 participants