search

linuxserver / docker-digikam

GNU General Public License v3.0
54 stars 5 forks source link

Blank screen, application never loads #4

Closed yllekz closed 3 years ago

yllekz commented 3 years ago

linuxserver.io

I can connect via the browser (Guacamole client) but digiKam never launches, you just get a black screen.

Expected Behavior

digiKam should launch.

Current Behavior

Guacamole loads, can connect, but I only get the bare Guacamole environment and no digiKam

Steps to Reproduce

  1. Deploy container
  2. Connect to instance via the browser
  3. Experience the darkness

Environment

OS: Raspberry Pi OS (Raspberry Pi 4B) CPU architecture: x86_64/arm32/arm64 arm64 How docker service was installed: OpenMediaVault/Docker/Portainer, official repo - linuxserver/digikam:arm32v7-latest

image

Command used to create docker container (run/create/compose/screenshot)

---
version: "2.1"
services:
  digikam:
    image: linuxserver/digikam:arm32v7-latest #the latest/specific version numbers/arm64 tags did not work on the Pi
    container_name: digikam
    network_mode: host
    environment:
      - PUID=998
      - PGID=100
      - TZ=America/New_York
    volumes:
      - /path/to/config/digikam:/config
      - /path/to/Photos:/Pictures:ro
    ports:
      - 3000:3000 #optional
    restart: unless-stopped

Docker logs

  RRScreenSizeSet ok 1,
pClientConGotConnection:,
rdpClientConGotConnection: g_sck_accept ok new_sck 7,
rdpClientConGotConnection: adding only clientCon,
rdpClientConProcessMsgVersion: version 0 0 0 1,
rdpClientConProcessScreenSizeMsg: set width 1344 height 843 bpp 16,
rdpClientConProcessScreenSizeMsg: shmemid 0 shmemptr 0xae382000,
rdpClientConProcessMsgClientInput: invalidate x 0 y 0 cx 1344 cy 843,
rdpClientConProcessMsgClientInfo:,
  got client info bytes 5732,
  jpeg support 0,
  offscreen support 0,
  offscreen size 0,
  offscreen entries 0,
  client supports glyph cache but server disabled,
  client can not do offscreen to offscreen blits,
  client can do new(color) cursor,
  client can not do multimon,
rdpRRSetRdpOutputs: numCrtcs 0 monitorCount 0,
rdpRRSetRdpOutputs: add output 0 left 0 top 0 width 1344 height 843,
rdpLoadLayout: keylayout 0x00000409 variant  display 10,
rdpkeybChangeKeyboardControl:,
rdpkeybChangeKeyboardControl: autoRepeat on,
rdpkeybChangeKeyboardControl:,
rdpkeybChangeKeyboardControl: autoRepeat on,
[20201229-22:15:54] [INFO ] starting xrdp with pid 317,
[20201229-22:15:54] [INFO ] listening to port 3389 on 0.0.0.0,
[20201229-22:16:38] [INFO ] Socket 11: AF_INET6 connection received from ::ffff:127.0.0.1 port 35710,
[20201229-22:16:38] [DEBUG] Closed socket 10 (AF_INET6 :: port 3389),
[20201229-22:16:38] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem,
[20201229-22:16:38] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem,
[20201229-22:16:38] [DEBUG] TLSv1.2 enabled,
[20201229-22:16:38] [DEBUG] TLSv1.1 enabled,
[20201229-22:16:38] [DEBUG] TLSv1 enabled,
[20201229-22:16:38] [DEBUG] Security layer: requested 3, selected 1,
ssl_tls_accept: TLS connection accepted,
colorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp),
[20201229-22:16:38] [INFO ] connected client computer name: Guacamole RDP,
postBeta2ColorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp 0xca02 15bpp 0xca03 16bpp 0xca04 24bpp),
highColorDepth 0x0010 (0x0004 4bpp 0x0008 8bpp 0x000f 15bpp 0x0010 16 bpp 0x0018 24bpp),
supportedColorDepths 0x0007 (0x0001 24bpp 0x0002 16bpp 0x0004 15bpp 0x0008 32bpp),
earlyCapabilityFlags 0x0021 (0x0002 want32),
got client client connection type 0x00000006,
xrdp_sec_process_mcs_data_CS_SECURITY:,
  client and server support none crypt, using none crypt,
xrdp_sec_out_mcs_data: using no security,
xrdp_load_keyboard_layout: keyboard_type [4] keyboard_subtype [0],
xrdp_load_keyboard_layout: model [] variant [] layout [us] options [],
[20201229-22:16:38] [INFO ] TLS connection established from ::ffff:127.0.0.1 port 35710: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384,
xrdp_caps_process_order: not enough orders supported by client, using painter.,
xrdp_caps_process_pointer: client supports new(color) cursor,
xrdp_process_offscreen_bmpcache: support level 1 cache size 7864320 MB cache entries 2000,
xrdp_caps_process_surface_cmds:,
  cmdFlags 0x00000052,
xrdp_caps_process_frame_ack:,
  max_unacknowledged_frame_count 2,
xrdp_caps_process_confirm_active: not enough orders supported by client, client wants off screen bitmap but offscreen bitmaps disabled,
yeah, up_and_running,
xrdp:xrdp_bitmap [2962429701]: xrdp_bitmap_create: noorders,
[20201229-22:16:38] [DEBUG] xrdp_0000016b_wm_login_mode_event_00000001,
xrdp:xrdp_mm [2962429725]: xrdp_mm_create: bpp 16 mcs_connection_type 6 jpeg_codec_id 0 v3_codec_id 0 rfx_codec_id 0 h264_codec_id 0,
[20201229-22:16:39] [INFO ] Loading keymap file /etc/xrdp/km-00000409.ini,
[20201229-22:16:39] [WARN ] local keymap file for 0x00000409 found and doesn't match built in keymap, using local keymap file,
xrdp_wm_login_mode_changed: login_mode is 0,
in xrdp_wm_init: ,
out xrdp_wm_init: ,
xrdp_wm_login_mode_changed: login_mode is 2,
[20201229-22:16:40] [DEBUG] xrdp_wm_log_msg: connecting to sesman ip 127.0.0.1 port 3350,
connecting to sesman ip 127.0.0.1 port 3350,
[20201229-22:16:40] [INFO ] xrdp_wm_log_msg: sesman connect ok,
sesman connect ok,
[20201229-22:16:40] [DEBUG] xrdp_wm_log_msg: sending login info to session manager, please wait...,
sending login info to session manager, please wait...,
[20201229-22:16:40] [DEBUG] return value from xrdp_mm_connect 0,
xrdp_wm_login_mode_changed: login_mode is 3,
[20201229-22:16:41] [INFO ] xrdp_wm_log_msg: login successful for display 10,
login successful for display 10,
loaded module 'libxup.so' ok, interface size 7616, version 3,
[20201229-22:16:41] [DEBUG] xrdp_wm_log_msg: started connecting,
started connecting,
lib_mod_connect: connected to Xserver (Xorg or X11rdp) sck 20,
[20201229-22:16:41] [INFO ] lib_mod_log_peer: xrdp_pid=363 connected to X11rdp_pid=367 X11rdp_uid=998 X11rdp_gid=100 client_ip=::ffff:127.0.0.1 client_port=35710,
[20201229-22:16:42] [DEBUG] xrdp_wm_log_msg: connected ok,
github-actions[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the issue template!

montagesepp commented 3 years ago

Pretty much the same here. Would be great to get arm64 support!

aptalca commented 3 years ago

There is currently no support for arm32 or arm64 support in this image. What the op pulled is a really old image that was accidentally pushed, and it doesn't work because even though it is using the arm32 baseimage, the digikam binary is the amd64 version.

The latest image is not multi arch and is x86_64 only, simply because we use the digikam appimage to pull the binary out of, which is x86_64 only.

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

mjl42 commented 3 years ago

The download link in Dockerfile seems to be broken. It should be https://download.kde.org/stable/digikam/${DIGIKAM_VERSION}/digiKam-${DIGIKAM_VERSION}-x86-64.appimage instead of https://download.kde.org/stable/digikam/${DIGIKAM_VERSION}/digikam-${DIGIKAM_VERSION}-x86-64.appimage. I'm wondering, if the Jenkins build can find such issues.

github-actions[bot] commented 1 year ago

This issue is locked due to inactivity