Greetings everyone...

 

I have searched around and I cannot find a solution for this.

 

When starting/restarting Krusader, the UI (noVNC) takes about 5mins to come up.

 

Also, when I connect/mount an external drive or network share, Krusader will not work with those items until it is restarted.

 

Any ideas on why that is happening?

 

Thanks!

Hi, 

 

If I mount a root share, with <my name> via Unassigned devices from my Mainserver to my Backupserver, or even the other way around, and using Krusader, even after restarting that docker, both Krusaders (the Mainserver or the Backupserver one) say that there is not enough disk space. The drives were empty!

I did not have this issue before, but for a while, I cannot use Krusader anymore to copy to the other server. 

 

MC does work so what is different from MC vs Krusader?

 

Could it be that Krusader is not able to work with datasets?

 

I have tried with a root share, <my name> and on both servers the same password for that account. 

I have tried to mount the shares separately, also no success.

 

What could be the reason for this behavior?

 

MAINSERVER:
Krusader config:

 

Pool config with zfs dataset and space available

 

Share mount to 'Backupserver' 

 

 

 

BACKUPERSERVER config:

 

 

I installed binhex-krusader. If I navigate to /media I can see my shares, however, I cannot look inside the folers, instead it asks me which application I want to use to open them:

23 minutes ago, neuronflow said:

I installed binhex-krusader. If I navigate to /media I can see my shares, however, I cannot look inside the folers, instead it asks me which application I want to use to open them:

That is because for some weird reason those are not folders they are files, what is the host path set to for /media for the container?

My host path is `/mnt/user`

I am using default settings for everything.

I believe this might be an access rights issue, somehow.

 

Edited November 30, 20241 yr by neuronflow

ich777 solved it: https://github.com/ich777/docker-krusader/issues/4

It seems I have to mount /mnt instead of /mnt/user because I am using exclusive shares.

does anyone have the step by step instructions on how to switch the date format to MM/DD/YYYY?

  

Quote

'binhex-shared' does NOT exist! Please check your mappings! Skipping it for now.

I get this log error every time Automatic Backup runs. This is related to binhex--krusader. Under "Volume Mappings (App to Host)" I see:

/1_Unraid_Shares <-> /mnt/user
/2_Unraid_Unassigned <-> /mnt/disks
/3_Unraid_Remotes <-> /mnt/remotes
/shared <-> binhex-shared
/config <-> /mnt/user/appdata/binhex-krusader

When I edit the binhex-krusader, I do not see this volume defined anywhere. I've checked both basic and advanced views. The only place I see the word shared is a predefined variable called, "SHARED_NETWORK", which is a yes/no option currently set to 'no'.

 

I could exclude this app from backups, but I'd rather fix the issue.

1 hour ago, Brona said:

  

I get this log error every time Automatic Backup runs. This is related to binhex--krusader. Under "Volume Mappings (App to Host)" I see:

/1_Unraid_Shares <-> /mnt/user
/2_Unraid_Unassigned <-> /mnt/disks
/3_Unraid_Remotes <-> /mnt/remotes
/shared <-> binhex-shared
/config <-> /mnt/user/appdata/binhex-krusader

When I edit the binhex-krusader, I do not see this volume defined anywhere. I've checked both basic and advanced views. The only place I see the word shared is a predefined variable called, "SHARED_NETWORK", which is a yes/no option currently set to 'no'.

 

I could exclude this app from backups, but I'd rather fix the issue.

ignore it, CA backup (or whatever its called now) does not know how to deal with docker volumes.

I just updated to 6.12.14 and now when I try to start krusaider it says execution error, server error and doesn't start. Any ideas?

42 minutes ago, downloadedskill said:

I just updated to 6.12.14 and now when I try to start krusaider it says execution error, server error and doesn't start. Any ideas?

delete cookies and cached data in your browser

Updated to the latest version and the docker no longer opens up the link for access

After the update I'm having a bizarre issue where the window doesn't auto-resize anymore and it's above the VLC window so you can't move it down or manage the tabs. Anyone else?

 

(edit)

As a work-around, I was able to at least modify the openbox config in the internal terminal by editing ~/.config/openbox/rc.xml and adding the following couple of lines:

 

<keybind key="Alt-Down">
    <action name="MoveRelative">
        <x>0</x>
        <y>10</y>
    </action>
</keybind>
<keybind key="Alt-Up">
    <action name="MoveRelative">
        <x>0</x>
        <y>-10</y>
    </action>
</keybind>

 

Then run this to refresh the keybinds:

 

> openbox --reconfigure

 

Then you can use Alt+Down to move the window down to at least grab the top bar. Even once you move it down if you try and maximize it, the window is stuck in a very odd position 2/3 of the way down the screen. So weird, but at least I can half-way manage the window now. Still have no idea why it exhibits this behavior.

 

(edit 2)

 

Apparently the margin for the window has a value set but it's completely invisible so I wasn't able to see it having a value and it looked completely blank. Double weird. See for yourself:

 

 

However, if you click into the field and just hit backspace and delete to ensure you remove the value, it fixed the issue. Still doesn't explain how it got set this way after the update. I definitely didn't set this value before. 

 

Edited January 4, 20251 yr by Dub

49 minutes ago, Dub said:

After the update I'm having a bizarre issue where the window doesn't auto-resize anymore and it's above the VLC window so you can't move it down or manage the tabs. Anyone else?

i see the exact same thing so its not just your config, trying to work out what config file to modify to fix the issue then i can include it in the image, thanks for your detailed post so far, its appreciated.

1 hour ago, Dub said:

However, if you click into the field and just hit backspace and delete to ensure you remove the value, it fixed the issue. Still doesn't explain how it got set this way after the update. I definitely didn't set this value before. 

how did you get to this window?

 

edit - figured it out.

Well that was super frustrating but i found a way of moving the window around:-

press and hold ALT then use left mouse button and you can then drag the window around and resize it correctly, once in the correct location and size then exit krusader (right click icon in taskbar) and then launch it again (right click desktop/krusader) and it should then be set correctly. 

10 hours ago, Seraphys said:

Updated to the latest version and the docker no longer opens up the link for access

going to need more info than this, 404? screenshots please.

Krusader new version, transfer speeds and ETA shown during transfers are refreshing far too frequently, looks like a bug in krusader, speeds do not seem to be affected so its a cosmetic bug.

Couldn't the window maximize itself?

 

Updated my container this morning to the latest version (2.9.0-1-01) clicked on the webgui link and got a blank page.  I then noticed on the docker page the container never gets assigned an IP address, the IP addresses are blank.  The container was up and running, using the console I can see all the directories but no way to access the GUI.  I manually set my IP for the container if that makes a difference.  I rolled back to 2.8.1-1-07 and everything works like before.

 

2.9.0-1-01

 

2.8.1-1-07

 

Minor request, please update the support link.  Looks like it is pointing to: "https://unraid.net/forums/topic/71764-support-binhex-krusader/" and needs to point to: "https://forums.unraid.net/topic/71764-support-binhex-krusader/".  Thanks!

 

6 hours ago, SShadow said:

I then noticed on the docker page the container never gets assigned an IP address, the IP addresses are blank.

this is an unraid bug which apparently is fixed in v7.xx:- 

bokmark the url instead in your browser or upgrade to v7.xx beta/rc.

1 hour ago, binhex said:

this is an unraid bug which apparently is fixed in v7.xx:- 

bookmark the url instead in your browser or upgrade to v7.xx beta/rc.

@binhex  Exactly like you said, bookmarking the url works fine.  I will do that for now.  Thanks!

Edited January 5, 20251 yr by SShadow

On 1/4/2025 at 9:50 AM, Jobine said:

Couldn't the window maximize itself?

 

 

That would have helped, but I don't get this prompt when clicking on the icon in any capacity. Also my icon also as at the bottom and not the top so I assume there's something different in your config than the default that might be exposing this.

 

Hello the SFTP protocol is missing again. i know there is something with kio workers but i have no idea how to install that. how can i downgrade to the prev version so i can get sftp back?

Howdy, just updated to the latest version. worked just fine beforehand but now getting this ->

 

Other docker containers are working as usual. Have disabled and enabled docker service. same. have turned the server off and on again. same.

 

am getting some errors on the logs ->

 

tried removing the container and the image and reinstalling from the previous apps template.

seemed to make no difference, but slightly different info in logs:>

 

2025-01-06 22:38:05,313 INFO Included extra file "/etc/supervisor/conf.d/novnc.conf" during parsing
2025-01-06 22:38:05,314 INFO Set uid to user 0 succeeded
2025-01-06 22:38:05,342 INFO supervisord started with pid 7
2025-01-06 22:38:06,352 INFO spawned: 'start' with pid 94
2025-01-06 22:38:06,354 INFO reaped unknown pid 8 (exit status 0)
2025-01-06 22:38:06,706 DEBG 'start' stderr output:
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

2025-01-06 22:38:06,708 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2025-01-06 22:38:06,710 DEBG 'start' stderr output:

Xvnc TigerVNC 1.13.1 - built May 25 2024 17:13:24
Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
See https://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12101013


Mon Jan  6 22:38:06 2025
 vncext:      VNC extension running!
 vncext:      Listening for VNC connections on all interface(s), port 5900
 vncext:      created VNC server for screen 0

2025-01-06 22:38:07,667 DEBG 'start' stderr output:
[mi] mieq: warning: overriding existing handler (nil) with 0x55d6487ab6e0 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x55d6487ab6e0 for event 3

2025-01-06 22:38:07,966 DEBG 'start' stderr output:
WebSocket server settings:

2025-01-06 22:38:07,968 DEBG 'start' stderr output:
  - Listen on :6080
  - Web server. Web root: /usr/share/webapps/novnc
  - No SSL/TLS support (no cert file)
  - proxying from :6080 to localhost:5900

2025-01-06 22:38:07,975 DEBG 'start' stdout output:
ObRender-Message: Unable to load the theme 'Adwaita Revisited Dark'

2025-01-06 22:38:07,976 DEBG 'start' stdout output:
ObRender-Message: Falling back to the default theme 'Clearlooks'

2025-01-06 22:38:08,456 DEBG 'start' stderr output:

ERROR: openbox-xdg-autostart requires PyXDG to be installed

2025-01-06 22:38:10,551 DEBG 'start' stdout output:
[info] tint2 not running

2025-01-06 22:38:10,597 DEBG 'start' stderr output:
tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes

2025-01-06 22:38:10,611 DEBG 'start' stderr output:
tint2: xRandr: Found crtc's: 1

2025-01-06 22:38:10,611 DEBG 'start' stderr output:

2025-01-06 22:38:10,612 DEBG 'start' stderr output:
[1;34mtint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96

2025-01-06 22:38:10,614 DEBG 'start' stderr output:
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc

2025-01-06 22:38:10,619 DEBG 'start' stderr output:
tint2: real transparency on... depth: 32

2025-01-06 22:38:10,626 DEBG 'start' stderr output:
t
2025-01-06 22:38:10,627 DEBG 'start' stderr output:
int2: panel items: TSC
tint2: Systray composited rendering on
tint2: nb monitors 1, nb monitors used 1, nb desktops 1
tint2: panel 1 uses scale 1 

2025-01-06 22:38:10,730 DEBG 'start' stderr output:
tint2: Kernel uevent interface initialized...

2025-01-06 22:38:10,746 DEBG 'start' stderr output:
tint2: systray window 8388621

2025-01-06 22:38:10,747 DEBG 'start' stderr output:
tint2: systray started

2025-01-06 22:38:13,278 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 142 minor 6 serial 501

2025-01-06 22:38:13,279 DEBG 'start' stderr output:
error 9: BadDrawable (invalid Pixmap or Window parameter) request 139 minor 4 serial 502
error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0 serial 524

 

any help would super cool. thanks for looking.