BNode Lock()/Unlock() not implemented

[umccullough@…]

It appears that when Vision tries to load the VisionSettings file from /boot/home/config/settings/Vision/ it fails (and then clears it as a result).

It would appear that the failure may be Haiku's inability to properly unflatten the BMessage.

It has also been reported that a VisionSettings file from Zeta also fails.

If necessary, I will attach a VisionSettings file that fails.

[axeld]

Thanks for the example! Can you provide one from Zeta as well? Haiku is supposed to understand both message formats.

[umccullough@…]

flattened BMessage VisionSettings file from R5

[mmlr]

I've now tested the attached file both from my test environment and under Haiku itself (both with a stream and a buffer based unflatten) and I can't reproduce the problem. The message unflattens fine and returns B_OK in both cases. Are you sure that it is Unflatten that failes? Or is it possible that there is a problem with the Vision setup or with reading / writing the message?

[umccullough@…]

It did occur to me after posting this that mabye it's not the Unflatten() that is causing the problem, but possibly the BFile?

If someone has a chance to download the Vision source (from bebits) - the SettingsFile class is where the problem appears.

I added some debug statements to determine that the proper path for the file was being used, but I realize now that I never actually checked that the file was being read properly.

I will dig in a bit deeper - I apologize that I'm not terribly familiar with the BeAPI and still learning.

[umccullough@…]

One thing of note - it appears that Vision is calling Unflatten(&file) where file is a BFile - I see some mention of being supported in the bebook on beunited.org - is that possibly the problem?

[mmlr]

That's a quite usual way to use Unflatten actually. The BFile represents also a BDataIO which can be read like a stream. I'm rather suspecting the BFile.Lock() or something before that failing.

[koki@…]

I have been using/testing Vision in Haiku, and for the most part it works well.

I do not know the technicalities, but what happens is that in Haiku Vision seems unable to save any settings, nor is it able to use settings migrated from a Vision installation in BeOS R5 or ZETA.

In other words, although it is possible to set IRC servers and channels, and set Vision preferences, but once you close Vision, all the settings are gone.

Maybe this is all obvious to those looking at this bug, but thought I would post this anyway. FWIW.

[mmlr]

Yes, it's the file.Lock() that fails. Should this bug be closed as invalid and another one be opened instead or shall I reassign back to you Axel and leave it?

[umccullough@…]

Maybe we just change the Summary and re-assign to Axel?

[umccullough@…]

It would appear that the issue goes back to the kernel (vfs.cpp I believe) where common_lock_node() and common_unlock_node() are not yet implemented.

If I remove failing file.Lock() calls from Vision's SettingsFile.cpp, it works great!

[axeld]

The Vision part is fixed now, the functions pretend to be successful since hrev17505. I keep this bug open since they still don't work as expected (ie. they still do nothing).

[axeld]

Implemented in hrev17697.