Catalogs with Moveable Paths

[grooveman]

Hi,

I am trying to get this to work. I have found no instructions in the AFS manual on this, but I did find these:
http://bibblelabs.com/products/bibble5/ ... alogs.html
http://product.corel.com/help/AfterShot ... index.html

They both refer to "Catalog Preferences", but I cannot find anything called "Catalog Preferences" on my copy of APS... There is a "Default Catalog Location"... so I am assuming they mean that.

They aren't the clearest instructions ever writtent, but I think I understand their point.

I have box A, a windows box which has a catalog I want to share to box B running Linux. So I:

0) Go to box A, share out d:\grooveman with full control
1) Click the library tab, then right-click on my catalog and choose "set Movable Paths"
2) Click "Add" and choose the folder containing the master files for that catalog: D:\grooveman\MyPictures\RawImagesDir and close ASP
3) Go to box B, make sure that I have mounted the share from Box A, and I have: D:\grooveman is mounted on /home/grooveman/APSDIR and I can read and write
4) Import the shared catalog
5) Still on box B, click the library tab, then right-click on my catalog and choose "set Moveable Paths"
6) Click "Set", and navigate to /home/grooveman/APSDIR/MyPictures/RAWImagesDir, and click "Choose", then I click "OK".
7) Still on box B, I go to "File"-"Preferences" and set "Default Catalog Location *" to /home/grooveman/APSDIR/MyPictures/APSCatalogs
8) Still on box B, Restart Aftershot pro
9) Browse the catalog.

Now, as long as APS is not running on Box A, I can navigate the catalog on box B, and view any picture I want. But -- I cannot make any changes to any of them. All attemps to make even the slightest change, to the image or to keywords results in a lockup, a crash or the pop-up window attached. And yes, I'm using APS, but the pop-window says "bibble". I guess they haven't gotten around to changing that yet.

I really need this to work. Am I doing something wrong, or is this a bug?

Thanks.

G

[afx]

Make sure you do have write permissions to the catalog (and to the image directory if you have XMP writing enabled).

Does the log file report anything useful?

cheers
afx

[grooveman]

I absolutely have read/write permissions to everything.

Does ASP have a log file option? I didn't see it in the preferences...

I checked the log file on the system, and there is nothing. I ran ASP on the command line, and I do get a lot of chatter there, but no complaints except for "Bibble encountered an error writing to the disk and will now close".

[afx]

Does ASP have a log file option? I didn't see it in the preferences...

Not an option.
Check the AfterShotPro.log file in your user folder.

Checking stdout/stderror could reveal more than that, so it looks like you already have it covered.
Next thing would be running it under strace on Linux boxes.

Code: Select all

strace -ff -o /tmp/as.log /usr/bin/AfterShotPro

and grep for the open/creat calls in the generated log files.

cheers
afx

[grooveman]

I appreciate the help, afx.

I ran ASP with strace. I find no "creat" Everything looks fine, until I make a change to a picture, then all of a sudden I get this in my log:

Okay, grepping for open, I find a lot of this:

Code: Select all

as.log.8552:open("i686/sse2/resolv.so", O_RDONLY)   = -1 ENOENT (No such file or directory)
as.log.8552:open("i686/resolv.so", O_RDONLY)        = -1 ENOENT (No such file or directory)
as.log.8552:open("sse2/resolv.so", O_RDONLY)        = -1 ENOENT (No such file or directory)
as.log.8552:open("resolv.so", O_RDONLY)             = -1 ENOENT (No such file or directory)
as.log.8552:open("/etc/ld.so.cache", O_RDONLY)      = 29
as.log.8552:open("/lib32/resolv.so", O_RDONLY)      = -1 ENOENT (No such file or directory)
as.log.8552:open("/usr/lib32/resolv.so", O_RDONLY)  = -1 ENOENT (No such file or directory)
as.log.8552:open("/opt/AfterShotPro/lib/libresolv", O_RDONLY) = -1 ENOENT (No such file or directory)
as.log.8552:open("tls/i686/sse2/libresolv", O_RDONLY) = -1 ENOENT (No such file or directory)
as.log.8552:open("tls/i686/libresolv", O_RDONLY)    = -1 ENOENT (No such file or directory)
as.log.8552:open("tls/sse2/libresolv", O_RDONLY)    = -1 ENOENT (No such file or directory)
as.log.8552:open("tls/libresolv", O_RDONLY)         = -1 ENOENT (No such file or directory)
as.log.8552:open("i686/sse2/libresolv", O_RDONLY)   = -1 ENOENT (No such file or directory)
as.log.8552:open("i686/libresolv", O_RDONLY)        = -1 ENOENT (No such file or directory)
as.log.8552:open("sse2/libresolv", O_RDONLY)        = -1 ENOENT (No such file or directory)
as.log.8552:open("libresolv", O_RDONLY)             = -1 ENOENT (No such file or directory)

There are no entries for "creat".

So... am I missing libraries? If so, what? I know that the rpm installer was missing the libsdtc++ library, and I had to download and install that by hand... You think this is another missing library (or libraries...)?

Or is this all just worthless chatter?

Thanks again.

-G

[afx]

Looks strange. Why would AS need the resolver library? All the network stuff should happen under the hood.

But I think the real problem is elsewhere. Could you please make all of the strace logs available? And name the file / path that you where working on when the crash happened.

cheers
afx

[grooveman]

Thanks afx,

Why would AS need the resolver library? All the network stuff should happen under the hood.

Yeah, I couldn't agree more... but I likewise never understood why bibble couldn't handle a cifs mount from a win7 machine without the 'noserverino' option either... why should it care? So who can say what it is doing under there... But anyway...

Could you please make all of the strace logs available? And name the file / path that you where working on when the crash happened.

I'm working in this path:
/home/chris/win7/My Pictures/2005_Pics - Copy/acclaim

/home/chris/win7 is the mountpoint.

Thanks again.

*Please note, that the paths mentioned in my original post were used just for the sake of brevity, and the paths from this point on are actual.

[afx]

Yeah, I couldn't agree more... but I likewise never understood why bibble couldn't handle a cifs mount from a win7 machine without the 'noserverino' option either...

Ask Nokia.
AS with a newer QT version does not have that problem

Hmmm,
I do not see any attempts to write to the catalog or an XMP in this log.
That is probably in another thread, that's why I asked for all of them.

cheers
afx

[grooveman]

AS with a newer QT version does not have that problem

Hey! That's great... I fixed my fstab, and you are correct -- it is no longer needed. Unfortunately, it made no difference with my current problem...


That is all of them, concatenated into 1. There were 8, and you can only have 3 attachments, so I concatenated them. I have tested it several times over, I never see any attempts to write. Not in the standard out, not in the logs and not in the strace output...

Here is another shot, with all the files kept separate.

[afx]

That is all of them, concatenated into 1. There were 8, and you can only have 3 attachments, so I concatenated them. I have tested it several times over, I never see any attempts to write. Not in the standard out, not in the logs and not in the strace output....

Ooops, did not realize you had them all in one.

Hmm, no open/write attempt to an XMP seems to be an indication that the crash happens before it even tries that.
Nothing else seems to be an indication of the crash in the trace, but I must admit, I am not the greatest strace reader.

No clue what causes the crash then;-(
Time to open up a bug report me thinks.

cheers
afx

[grooveman]

Me too. Thank you though for helping me look at it before filing the report.

[grooveman]

Posted... but I really hate their method of bug "tracking"... I cannot even tell if the bug submitted correctly...

[Jeff Stephens]

We did get your submission...

First, default catalog location doesn't have anything to do with 'movable catalogs'. The only thing that does is control where new catalogs are created.

On your steps above (and thanks for including those), #4 is "Import the shared catalog" - what specifically do you mean here? Do you mean A) Open the Catalog that I already imported my images into (from step 2), or do you mean B) import shared images into a new catalog? Hint: you want 'A'.

I think that's what you're doing, but I just want to be sure. Only one ASP instance can open a Catalog at a time, attempts to open a second will pop up a message saying 'sorry, this catalog is locked.'

I suspect that the necessary file locking over cifs isn't supported. The fact that the catalog is opened over the cifs network is odd, but any change that would need to be committed to the catalog seem to be what is failing....

[grooveman]

Thank you for posting Jeff. Glad to know it got through. Now to your questions...

First, default catalog location doesn't have anything to do with 'movable catalogs'. The only thing that does is control where new catalogs are created.

Great, that's cleared up then. But, then what does "Catalog Preferences" mean in the directions here? I couldn't find anything on the interface called "Catalog Preferences"....

Do you mean A) Open the Catalog that I already imported my images into (from step 2)

Exactly.

I think that's what you're doing, but I just want to be sure. Only one ASP instance can open a Catalog at a time, attempts to open a second will pop up a message saying 'sorry, this catalog is locked.'

Understood (and acknowledged above). Definitely not the problem here.

I suspect that the necessary file locking over cifs isn't supported. The fact that the catalog is opened over the cifs network is odd, but any change that would need to be committed to the catalog seem to be what is failing....

I don't see why it is odd. It was clearly intended to do this. The whole point of "Moveable Paths" is to be able to open a catalog that resides on another computer. The only way to reach another computer is through a network, and the most ubiquitous protocol for file sharing over a network is CIFS. If "Moveable Paths" isn't supported over CIFS, then under what protocol is it supported? CIFS is how things are done now days, and the directions clearly use MS shares (CIFS) as evidenced by the usage of mapped drives...