On 3/13/2024 at 4:56 PM, wirenut said:

ok Done. Thank You binhex

Thanks for the suggestion, but its been there a few days with over 100 views showing and not one reply.

I see you mention a couple posts up about a new build coming. I guess i will wait for that and see if it changes anything for me.

13 hours ago, ph_ said:

unfortunately the update seems to have introduced some problems, see below logs. The app does not work any more, the WebUI shows another error. Help would be appreciated. 

this looks like the classic caching/cookies issue, try clearing down cookies/cache, try another browser, try incognito mode, one of those should get you going.

 

FWIW i can confirm the latest image is working for me

17 minutes ago, wirenut said:

Thanks for the suggestion, but its been there a few days with over 100 views showing and not one reply.

I see you mention a couple posts up about a new build coming. I guess i will wait for that and see if it changes anything for me.

sorry dude but there is nothing i can do about this as it's an unraid related issue, the image is accessible and for me i cannot reproduce the issue you are seeing.

you could try deleting the container completely, then re-create it, this may fix it *shrug*.

55 minutes ago, binhex said:

sorry dude but there is nothing i can do about this as it's an unraid related issue, the image is accessible and for me i cannot reproduce the issue you are seeing.

you could try deleting the container completely, then re-create it, this may fix it *shrug*.

Well... thanks again. I removed the container, deleted the app data folder and installed fresh. The whole process took about 10 minutes to complete but it installed and is no longer showing update ready. I'll see how goes it as time passes. Attached is the info from the install command window if it may be of some use to you?

And again, Thank You!

 

 

binhex-krusader install 2024.03.18.txt

I have the same issue.  Fresh install but multiple windows.

 

2024-03-18 07:25:25,214 DEBG 'start' stderr output:
tint2: xRandr: Found crtc's: 1

 

2024-03-18 07:25:25,214 DEBG 'start' stderr output:
tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96
tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'.
tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc

 

2024-03-18 07:25:25,215 DEBG 'start' stderr output:
tint2: real transparency on... depth: 32

 

2024-03-18 07:25:25,219 DEBG 'start' stderr output:
tint2: panel items: TSC
tint2: Systray composited rendering on
tint2: nb monitors 1, nb monitors used 1, nb desktops 4
tint2: panel 1 uses scale 1 

 

2024-03-18 07:25:25,236 DEBG 'start' stderr output:
tint2: Kernel uevent interface initialized...

 

2024-03-18 07:25:25,236 DEBG 'start' stderr output:
tint2: systray window 6291469
tint2: systray started

 

2024-03-18 07:25:25,918 DEBG 'start' stderr output:
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)

 

2024-03-18 07:25:25,918 DEBG 'start' stderr output:
glx: failed to create drisw screen

 

2024-03-18 07:25:25,918 DEBG 'start' stderr output:
failed to load driver: zink

 

2024-03-18 07:25:26,117 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 599

 

2024-03-18 07:25:26,117 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 600
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 601
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 602
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 603
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 604
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 605
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 606
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 607

 

2024-03-18 07:25:26,117 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 608
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 609
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 610
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 611
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 612
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 613
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 614

 

2024-03-18 07:25:26,117 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 615
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 616
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 617
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 618
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 619
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 620
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 621

 

2024-03-18 07:25:26,118 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 622
error 3: BadWindow (invalid Window parameter) request 2 minor 0 serial 642
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 643

 

2024-03-18 08:41:12,659 DEBG 'start' stderr output:
192.168.0.216 - - [18/Mar/2024 08:41:12] 192.168.0.216: Plain non-SSL (ws://) WebSocket connection

 

2024-03-18 08:41:12,659 DEBG 'start' stderr output:
192.168.0.216 - - [18/Mar/2024 08:41:12] 192.168.0.216: Path: '/websockify'
192.168.0.216 - - [18/Mar/2024 08:41:12] connecting to: localhost:5900

 

2024-03-18 08:41:12,665 DEBG 'start' stderr output:

 

Mon Mar 18 08:41:12 2024
 Connections: accepted: 127.0.0.1::53110

 

2024-03-18 08:41:12,675 DEBG 'start' stderr output:
 SConnection: Client needs protocol version 3.8

 

2024-03-18 08:41:12,679 DEBG 'start' stderr output:
 SConnection: Client requests security type VeNCrypt(19)

 

2024-03-18 08:41:12,687 DEBG 'start' stderr output:
 SVeNCrypt:   Client requests security type VncAuth (2)

 

 

15 hours ago, ph_ said:

Hi,

 

I just updated Krusader,

 

unfortunately the update seems to have introduced some problems, see below logs. The app does not work any more, the WebUI shows another error. Help would be appreciated. 

 

I am running Unraid 6.12.4.

 

text  error  warn  system  array  login  

int2: panel items: TSC

2024-03-18 01:28:15,361 DEBG 'start' stderr output:
tint2: Systray composited rendering on
tint2: nb monitors 1, nb monitors used 1, nb desktops 4
tint2: panel 1 uses scale 1 

2024-03-18 01:28:15,423 DEBG 'start' stderr output:
tint2: Kernel uevent interface initialized...

2024-03-18 01:28:15,424 DEBG 'start' stderr output:
tint2: systray window 8388621

2024-03-18 01:28:15,424 DEBG 'start' stderr output:
tint2: systray started

2024-03-18 01:28:15,666 DEBG 'start' stderr output:
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)

2024-03-18 01:28:15,667 DEBG 'start' stderr output:
glx: failed to create drisw screen

2024-03-18 01:28:15,667 DEBG 'start' stderr output:
failed to load driver: zink

2024-03-18 01:28:16,020 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 434

2024-03-18 01:28:16,024 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 435
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 436
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 437
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 438

2024-03-18 01:28:16,029 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 439

2024-03-18 01:28:16,029 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 440

2024-03-18 01:28:16,030 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 441

2024-03-18 01:28:16,030 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 442

2024-03-18 01:28:16,031 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 443

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 444

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 445

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 446

2024-03-18 01:28:16,032 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 447

2024-03-18 01:28:16,033 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 448

2024-03-18 01:28:16,033 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 449

2024-03-18 01:28:16,034 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 450

2024-03-18 01:28:16,034 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 451

2024-03-18 01:28:16,035 DEBG 'start' stderr output:
error 3: BadWindow (invalid Window parameter) request 2 minor 0 serial 471
error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 472

2024-03-18 01:32:13,289 WARN received SIGTERM indicating exit request
2024-03-18 01:32:13,290 DEBG killing start (pid 70) with signal SIGTERM
2024-03-18 01:32:13,295 INFO waiting for start to die
2024-03-18 01:32:13,303 DEBG 'start' stderr output:
Signal: 15
X connection to :0 broken (explicit kill or server shutdown).
Signal: 15
In exit

2024-03-18 01:32:13,305 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23117275914576 for <Subprocess at 23117276021584 with name start in state STOPPING> (stdout)>
2024-03-18 01:32:13,306 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23117275846800 for <Subprocess at 23117276021584 with name start in state STOPPING> (stderr)>
2024-03-18 01:32:13,307 WARN stopped: start (exit status 143)
2024-03-18 01:32:13,310 DEBG received SIGCHLD indicating a child quit

** Press ANY KEY to close this window ** 

 

 

Best,

ph

 

On 3/16/2024 at 8:08 PM, binhex said:

I have not built the base in a while due to an ongoing issue, so i will take a look at it and see if i can fix it up and then kick off a new build of this image which should result in a reduction in the image size (nothing to update).

 

I'm not sure what you did, but the latest update dropped about 1.3GB in size.

 

Again, I wasn't opposed to a container getting bigger. I was only trying to be diligent about the possibility of something having gotten added to one of the supporting images that may not have been above board.

 

Thanks for looking into it.

1 hour ago, draeh said:

I'm not sure what you did, but the latest update dropped about 1.3GB in size.

i fixed up the broken github action for the base (it was on my todo list) which then kicked off the intermediate image builds, once done then i re-crated the krusader image, and due to the fact there were no updates as the base image is now up to date, the size of the image was dramatically reduced.

 

from now on we should be back to more frequent automated base image builds, which should help alleviate any large increases in image size due to update churn.

10 hours ago, binhex said:

this looks like the classic caching/cookies issue, try clearing down cookies/cache, try another browser, try incognito mode, one of those should get you going.

 

FWIW i can confirm the latest image is working for me

 

 

Hi @binhex ,

 

I tried another browser .... it works there instantly. In the initial browser clearing cached images and files and did the trick there. I did not know that a vnc could not appear to work because of some cookie / cash issue. Will keep it in mind. 

 

Many thanks,

ph

Edited March 19, 20242 yr by ph_

On 3/12/2024 at 5:38 AM, binhex said:

i didn't knowingly include or remove sftp, there has been no alterations to the code, it was simply a re-triggered build from a upstream change.

 

Can you detail how you previously used sftp in this container, that way i can then investigate why it got removed and how to add it back in.

@binhex

i use sftp to move files from one unraid server to my main unraid server. so i use the connect option and use the drop down to chose sftp and put in my details. 

 

i have seen that sftp is back and thank you for that. i am sorry that it has taken me a while to respond but i have had some cardiac issues.

7 hours ago, Nicon4454 said:

i use sftp to move files from one unraid server to my main unraid server. so i use the connect option and use the drop down to chose sftp and put in my details.

OK thanks for that, so it looks like the package 'kio' includes sftp and it looks like the package version has now bumped up to 'kio5' which once included in the build meant that sftp was available again (amongst other additional functionality).

 

7 hours ago, Nicon4454 said:

i have seen that sftp is back and thank you for that. i am sorry that it has taken me a while to respond but i have had some cardiac issues.

Hey no worries, everyone has stuff going on in their lives, i hope you are ok.

  On 3/18/2024 at 8:41 AM, binhex said:

sorry dude but there is nothing i can do about this as it's an unraid related issue, the image is accessible and for me i cannot reproduce the issue you are seeing.

you could try deleting the container completely, then re-create it, this may fix it *shrug*.

 

 

An FYI, with the update last night the situation has returned. Interestingly it also now effects your preclear docker for me.

Over 200 views in my docker engine post, but unfortunately no help. For what its worth, I have updated to unraid 6.12.9.

If you have any other ideas I could try, suggestions appreciated.

 

Trying to use the dark theme for months, without success, now I need it to use with the new OLED monitor

How can I enable it?

Hi there, newbie Unraid user here!

 

I'm currently backing up a 4TB external drive to my Unraid server, but the transfer stalls every few minutes and all my CPU cores are maxed at 100%. It's not doing any copying/reads from my external drive, yet one of the drives in my array are doing a lot of reads. It's making the server slow and unresponsive, has anyone encountered a similar issue?

52 minutes ago, agik said:

newbie

Attach Diagnostics to your NEXT post in this thread 

On 12/5/2018 at 6:35 AM, tillkrueger said:

tried both of those ways of formatting the date, but no change when restarting Krusader.

I have USA as us already.

I'll put this on the back-burner for the moment, as it's not a show-stopper, but will come back to it when I have to.

thanks, binhex!

 

Since I have not seen a reply that this was resolved yet, to change the date to US format, add a variable "LC-TIME" with value "en_US.UTF8 && krusader".

 

Edited June 9, 20242 yr by TopQuark

@binhex Any idea if we'll never get seamless copy/paste like in KasmVNC?

14 hours ago, sdballer said:

@binhex Any idea if we'll never get seamless copy/paste like in KasmVNC?

looks like it maybe possible in novnc in the future, but its tricky, for the gory details:- https://github.com/novnc/noVNC/pull/1347

On 3/17/2024 at 1:08 AM, binhex said:

the base os i use is arch linux, this is a rolling distro which means i need to update all packages if i want to pick up the latest versions of packages pushed to arch linux repository and because docker images are built in immutable layers this can lead to larger image sizes depending on when the base image was last built, so the size will vary somewhat, this is compounded for this image as it requires a lot of packages due to the fact its running a gui.

I have not built the base in a while due to an ongoing issue, so i will take a look at it and see if i can fix it up and then kick off a new build of this image which should result in a reduction in the image size (nothing to update).

Hey, not sure I understand all this correctly, but nevertheless krusader is currently my largest container with around 2.6 GB.

 

Quite suprising for such a tool that certainly looks and feels "lightweigth". Is there anything I can do to reduce this size? Or are there similar NC type options that anyone would recommend that have a smaller footprint?

14 hours ago, sir_storealot said:

similar NC type options that anyone would recommend that have a smaller footprint?

mc at the console?

On 7/8/2024 at 5:28 AM, binhex said:

looks like it maybe possible in novnc in the future, but its tricky, for the gory details:- https://github.com/novnc/noVNC/pull/1347

@binhex Have you seen this yet?

https://github.com/kasmtech/KasmVNC

6 hours ago, sdballer said:

@binhex Have you seen this yet?

https://github.com/kasmtech/KasmVNC

Yes and I even had a little play with it, yes it does give your clipboard integration, but it adds size to what is already a large image and the pull out configuration pane has some graphical issues, not too mention it does require coding changes to integrate, so for now I won't be switching.

Selecting icon and Support directs you to https://unraid.net/forums/topic/71764-support-binhex-krusader/ which gives me a 404 error.  I believe the correct link should be https://forums.unraid.net/topic/71764-support-binhex-krusader/

 

1 hour ago, snusnu1987 said:

Selecting icon and Support directs you to https://unraid.net/forums/topic/71764-support-binhex-krusader/ which gives me a 404 error.  I believe the correct link should be https://forums.unraid.net/topic/71764-support-binhex-krusader/

 

Thanks!, i have been revamping all the templates and typo's and copy/paste mistakes are bound to creep in, now corrected.

 

On 9/15/2018 at 11:58 PM, Karyudo said:

How can I set Krusader to use ISO 8601 dates (i.e. YYYY-MM-DD) instead of whatever legacy format it's using now?

Sorry for necroing the thread, but I am new to Unraid, and stumbled across this issue today.  After spending several hours on this, I was able to come up with a solution for my use case that may lead others on the right path.  Editing docker container variables was the only thing that worked for me (editing kdeglobals, bashrc, locale.conf and messing with locale-gen were dead ends).  Here is what I did to make it work for me (as a user based in the US):

 

1.  Edit the docker container.
2.  Click on "Add another Path, Port, Variable, Label or Device"
3.  Edit Configuration should look like this:

Config Type: Variable
Name: Variable:LC_TIME
Key:LC_TIME
Value: en_US.UTF-8

 

The above settings will show dates in MM-DD-YY AM/PM format in the "modified" file listing.    FWIW, I tried en_DK.UTF-8 as an LC_TIME variable (which is supposed to list files in YYYY-MM-DD format), but files were incorrectly displayed in DD-MM-YYYY format on my end.  Not sure if you or others outside the US will have the same result, but it might be worth a try.

Is there a way to view pictures under krusader ?

I post this same question some years ago but seems the answer I got is not valid now.


Thankyou