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

QT apps failed to detect physical screen size within aarch64 chroot #34078

Closed
darkgeek opened this issue Nov 14, 2021 · 1 comment
Closed

QT apps failed to detect physical screen size within aarch64 chroot #34078

darkgeek opened this issue Nov 14, 2021 · 1 comment
Labels

Comments

@darkgeek
Copy link

darkgeek commented Nov 14, 2021

Hi, all:

New to voidlinux here. I use Orange Pi 3 as my lightweight workstation, which is an aarch64 board, and I have the latest Armbian running there. Meanwhile, it has panfrost support to make hardware accelration (Mali T720) usable.

And then, I setup a voidlinux by following the official doc here, run it in a chroot with /dev,/proc,/sys,/tmp,/run etc binding. Everything works good except qt apps.

When I try to run qt apps as normal user in chroot, for example qutebrowser or keepassxc, they always say "Unable to query physical screen size":

~> ls -l /dev/dri/
total 0
drwxr-xr-x  2 root root        100 Nov 13 09:56 by-path
crw-rw----+ 1 root video  226,   0 Nov 13 09:56 card0
crw-rw----+ 1 root video  226,   1 Nov 13 09:56 card1
crw-rw----+ 1 root render 226, 128 Nov 13 09:56 renderD128

~> glxinfo | grep render
direct rendering: Yes
    GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, 
    GLX_MESA_query_renderer, GLX_MESA_swap_control, GLX_OML_swap_method, 
Extended renderer info (GLX_MESA_query_renderer):
OpenGL renderer string: Mali T720 (Panfrost)
    GL_EXT_multisampled_render_to_texture, 
    GL_EXT_multisampled_render_to_texture2, GL_EXT_occlusion_query_boolean, 
    GL_OES_fbo_render_mipmap, GL_OES_get_program_binary, GL_OES_mapbuffer,
    
~> DISPLAY=:0 keepassxc
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-justin'
Unable to query physical screen size, defaulting to 100 dpi.
To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).

~> DISPLAY=:0 keepassxc
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-justin'
Unable to query physical screen size, defaulting to 100 dpi.
To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters).

Then with those errors, both of them show apps' ui in fullscreen mode, without window manager's border, and unresponsive to any keyboard or mouse click events:
2021-11-14-224747_923x688_scrot

2021-11-14-224931_912x676_scrot

System

  • xuname:
    Void 5.10.60-sunxi64 aarch64 Unknown uptodate rFF
  • package:
    qutebrowser-2.4.0_1
    keepassxc-2.6.6_1

Expected behavior

They are expected to run without such issues. Both qutebrowser and keepassxc work well in alpinelinux or archlinuxarm chroot environment with same setup.

Actual behavior

They failed to run normally (full screen, not respond to any keyboard or mouse events) with the errors:

Unable to query physical screen size, defaulting to 100 dpi.
To override, set QT_QPA_EGLFS_PHYSICAL_WIDTH and QT_QPA_EGLFS_PHYSICAL_HEIGHT (in millimeters)

Steps to reproduce the behavior

Setup a voidlinux by following the official doc here, and run it in a chroot with /dev,/proc,/sys,/tmp,/run etc binding. Host may be a Debian distro, and my host is:

~> neofetch
OS: Armbian bullseye (21.08.3) aarch64 
Host: OrangePi 3 
Kernel: 5.10.60-sunxi64 
Uptime: 1 day, 4 hours, 43 mins 
Packages: 1452 (dpkg) 
Shell: fish 3.1.2 
Resolution: 1440x900 
DE: MATE 1.24.1 
WM: Metacity (Marco) 
Theme: Arc [GTK2/3] 
cons: Papirus [GTK2/3] 
Terminal: mate-terminal 
Terminal Font: Monospace 13 
CPU: sun50iw1p1 (4) @ 1.800GHz 
Memory: 1151MiB / 1989MiB 
@github-actions
Copy link

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant