bosswaz Posted March 22, 2022 Share Posted March 22, 2022 I had digikam running beautifully...then I went headless on unraid and rebooted...now digikam throws the error Failed to close file descriptor for child process (operation not permitted) The headless unraid may not be relevant im not sure. I have removed the app several times and removed the appdata. Each time I re-install the digikam app I get the same error. I even created a new docker and reinstalled digikam into the new docker...SAME ERROR! This is interesting: When I install the new digikam container, I edit appdata path and ADD custom photo path (standard procedure) however in the path popup window MY OLD PATHS (from previous digikam installs) show up in the drop downs...like they still exist somewhere on the unraid system even though I have removed the app...and even started a different docker! It seems this data is being stored somewhere on the unraid system and is LOCKED up somehow. Where is this data stored? How can I flush it? Is it causing this child process permission issue? Im on RC4 (this problem occurred on RC2 RC3 and RC4 so that does not seem to be relevant) Any Ideas? Here are the logs from the digikam app: rdpkeybControl: what 1 rdpkeybDeviceOn: rdpDeferredRandR: rdpResizeSession: width 1024 height 768 calling RRScreenSizeSet rdpRRScreenSetSize: width 1024 height 768 mmWidth 271 mmHeight 203 rdpRRGetInfo: screen resized to 1024x768 RRScreenSizeSet ok 1 rdpResizeSession: width 1920 height 975 calling RRScreenSizeSet rdpRRScreenSetSize: width 1920 height 975 mmWidth 508 mmHeight 258 rdpRRGetInfo: screen resized to 1920x975 RRScreenSizeSet ok 1 rdpClientConGotConnection: rdpClientConGotConnection: g_sck_accept ok new_sck 7 rdpClientConGetConnection: idle_disconnect_timeout set to non-positive value, idle timer turned off rdpAddClientConToDev: adding first clientCon 0x55c93ebdb330 rdpClientConProcessMsgVersion: version 0 0 0 1 rdpClientConProcessScreenSizeMsg: set width 1920 height 975 bpp 16 rdpClientConProcessScreenSizeMsg: shmemid 0 shmemptr 0x14f4a4d70000 rdpClientConProcessMsgClientInput: invalidate x 0 y 0 cx 1920 cy 975 rdpInDeferredRepeatCallback: rdpkeybChangeKeyboardControl: rdpkeybChangeKeyboardControl: autoRepeat off (EE) Failed to open authorization file ".Xauthority": No such file or directory rdpRRGetInfo: rdpClientConProcessMsgClientInfo: got client info bytes 7072 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 numOutputs 0 monitorCount 0 rdpRRSetRdpOutputs: add output 0 left 0 top 0 width 1920 height 975 rdpLoadLayout: keylayout 0x00000409 variant display 12 rdpkeybChangeKeyboardControl: rdpkeybChangeKeyboardControl: autoRepeat on rdpkeybChangeKeyboardControl: rdpkeybChangeKeyboardControl: autoRepeat on fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first fuse: device not found, try 'modprobe fuse' first guacd[437]: INFO: Accepted format: 16-bit PCM with 2 channels at 44100 Hz guacd[437]: INFO: Accepted format: 16-bit PCM with 2 channels at 22050 Hz guacd[437]: INFO: Connected to RDPDR 1.12 as client 0x111d41ee guacd[437]: INFO: RDPDR user logged on rdpInDeferredRepeatCallback: rdpkeybChangeKeyboardControl: rdpkeybChangeKeyboardControl: autoRepeat off rdpInDeferredRepeatCallback: rdpkeybChangeKeyboardControl: rdpkeybChangeKeyboardControl: autoRepeat off guacd[437]: INFO: User "@73c204b4-33b1-4856-9dee-20a8aae9ce71" disconnected (0 users remain) guacd[437]: INFO: Last user of connection "$bdf5adb5-c637-4914-9d07-5f57a5818c4c" disconnected [2022-03-22 09:34:02] [Connection 1] Closing connection with error: Error: not opened at WebSocket.send (/gclient/node_modules/ws/lib/WebSocket.js:218:38) at ClientConnection.send (/gclient/node_modules/guacamole-lite/lib/ClientConnection.js:125:24) at GuacdClient.sendBufferToWebSocket (/gclient/node_modules/guacamole-lite/lib/GuacdClient.js:172:35) at GuacdClient.processReceivedData (/gclient/node_modules/guacamole-lite/lib/GuacdClient.js:163:14) at Socket.emit (node:events:527:28) at addChunk (node:internal/streams/readable:324:12) at readableAddChunk (node:internal/streams/readable:297:9) at Socket.Readable.push (node:internal/streams/readable:234:10) at TCP.onStreamRead (node:internal/stream_base_commons:190:23) [2022-03-22 09:34:02] [Connection 1] Closing guacd connection [2022-03-22 09:34:02] [Connection 1] Client connection closed guacd[437]: INFO: Internal RDP client disconnected guacd[410]: INFO: Connection "$bdf5adb5-c637-4914-9d07-5f57a5818c4c" removed. rdpClientConRecv: g_sck_recv failed(returned 0) rdpClientConRecvMsg: error rdpClientConCheck: rdpClientConGotData failed rdpClientConDisconnect: rdpRemoveClientConFromDev: removing clientCon 0x55c93ebdb330 Closing all connections and exiting... ** Press ANY KEY to close this window ** Quote Link to comment
bosswaz Posted March 22, 2022 Author Share Posted March 22, 2022 in the logs there is an error: fuse: device not found, try 'modprobe fuse' first When I went headless, I also removed the keyboard...is this relevant? Quote Link to comment
bosswaz Posted March 22, 2022 Author Share Posted March 22, 2022 ok found this in the xorg log : dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory) seems like my nvdia conf file is messed up...so im totally lost (so perhaps going headless was a bad idea)... Perhaps I should completely start over from scratch... Quote Link to comment
hackerman Posted April 8, 2022 Share Posted April 8, 2022 @bosswazI think it's an issue with the latest container. Use the tag 7.6.0-ls63 and see if that works for you. Quote Link to comment
bosswaz Posted April 14, 2022 Author Share Posted April 14, 2022 Thanks for your reply...and sorry i have been away from this issue for awhile... I dont know what you mean or how to do this: Use the tag 7.6.0-ls63 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.