MediaVault releases

@ddni

Could there be a third version of the library lurking somewhere possibly being loaded instead of the one in SYS:Libs?

What is listed with "which LIBS:oo.library ALL"?

Best regards,

Niels

@walkero

1.2.1 working great so far

@nbache @walkero

Hi,

My earlier proclamation that all was fixed has now proven to be false. Today, mediavault displays the same issue with just the libs in sys:libs.
It worked well last night…
So far today I have seen it start just once and work. All other attempts following hard restarts result in no output.
Apologies, I know that these inconsistent bug reports are annoying.


No third oo.library floating about:
"New Shell process 10
10.System:> which LIBS:oo.library ALL
System:Libs/oo.library"

Versions of oo.library in mediavault and my sys:Libs are both 1.13.

@ddni
No worries at all.. You help me a lot to try and figure out where the problem is.
Do you have any clean partition with only AmigaOS 4.1 FE update2 installed, so to try if it works there? This way we could see that it is not a specific problem with your machine.

@ddni
@walkero

I'm on X1000 as well, no crashes here though.

I don't think it has to do with library loading, rather with classes and gadgets.
It seems to try and load the needed gadgets but for some reason bugs out because there may be one or two it doesn't like (probably either faulty install or differing version).

Those are mine


you can use this script to check and compare, just put it where the MediaVault binary is)


Since not even the main window comes up it's freezing while creating or drawing the window...or so i suspect.


edit. There's a bug in the script, utility.library is resident, so get rid of the "file" switch

@Raziel

Thanks, I will test and list my versions.

edit:
All my versions match those shared by you.

@ddni

OK.

Does MediaVault stop at your posted snoopy log already?

Because on my system it starts to open the gadgets and bitmaps it needs for the window...together with locking and accessing TBIMAGES:..both aren't to be found in your log.

Something quits early

Yes, mediavault stops and snoopy shows no attempt to load assets.
I will capture a serial output of the crash. Not sure if it will add anything though.

Hi all tested on a fresh AOS4 u2 install - mediavault works fine.
I installed ESP on top of the fresh AOS u2 replacing all core components with AEON - mediavault works fine.

Definitely something wrong with my daily OS4 install.
Have tried disabling all wbstartup items, but no joy. Will try disabling user startup too. Any others tips?

@ddni

I don't know how much stuff you added to your daily os4 install, but wouldn't it be easier to add the stuff you use back to that working fresh install...one by one?

I suspect one of the core parts in your daily install is causing it...which one is the hard part to find, probably was overwritten some time back.

@Raziel

Yes, it would be a way to get Mediavault working. Although my daily driver is set just right ;)
However, not knowing the cause is irritating so adding one by one would be a useful bug finding exercise.

@ddni

Yeah, that is soooooo annoying.
I had the same experience with a Hollywood app that crashed accessing a certain library...but only for me.
I wasted months, then I was forced to reinstall the OS and the crash was gone.

I'd still love to know what was causing it though...but, meh

@ddni

Quote:The serial log you mentioned earlier - did you get around to making it? I'd think that could give some clues about what makes it crash on one system and not the other, and especially where it crashes.

Best regards,

Niels

Thanks everyone for testing this and trying to find the cause. Unfortunately, this seems to come from oo.library, and since we don't have access to it's code it is hard to find what causes the problems. It's like searching needle in haystack.

@ddni
MediaVault worked on the new installation with oo.library v1.13 or the one I sent you?
Also, have you tried to check the new installation partition with your daily one with a diff app and see the differences and if something helps you find something that could cause the problems?

@nbache @walkero

Will post the serial output this afternoon.
Need to check oo library version…

Thanks all.

Edit, I have added the full serial output from a hard reset, maybe something is wrong here? - The last section after "No Envy24 found!" is the output when running Mediavault from it's icon, running from shell has same result.

Serial debug is set after boot to 20 with run >NIL: kdebug "debuglevel 20"

The version of oo.library is 1.13 (result the same with a beta 1.14 version).

Thanks again.

Edited above post.

@ddni

Say, what version of amissl do you have installed?

@Raziel
AmiSSL Version 4.9
Have you a theory?

@ddni

Not really, I heard from another user that he had similar problems with amissl pre 4.9, but that doesn't fit here, then.

@Raziel,@ddni
Don't hangup with oo.library a more likely candidate is Jansson.library i would suggest to look into that if you have duplicates or an older version than the requested 2.12.1