Aftershot crashes on …everything!

Bugs & Suggestions
Post Reply
okhanken
Posts: 4
Joined: Mon Sep 15, 2014 11:27 am
operating_system: Linux
System_Drive: N/A
32bit or 64bit: 64 Bit

Aftershot crashes on …everything!

Post by okhanken »

I have spent the last few weeks, including the Christmas and New Year holiday, rebuilding catalogues after frequent crashes. I have reinstalled Aftershot a couple of times, fixed errors in the OS; have been running Aftershot as root to be able to run it as user with my NVIDIA card… but only after fixing privileges that was altered during the root session. What ever I do, Aftershot is able to find a new and more insane way to crash.
Maybe this one is the best. It is during import of pictures shot today.

Code: Select all

Error - Unable to load setting created with a later version of Bibble.
Yes, I have been here since the early Bibbleical days, but I am for Bibble's sake running the latest AfterShotPro 3, not an early Bibble!

Code: Select all

exportXMP -  XMP Error  102 ,  Bad XML name
Error - Unable to load setting created with a later version of Bibble.
Error - Unable to load setting created with a later version of Bibble.

Code: Select all

exportXMP -  XMP Error  102 ,  Bad XML name
clFatal: status =  -4    "map failed"
Segmentation fault
I waited an eternity for Aftertshot to finnish an update after I asked it write Aftershot XML to that catalogue, and after that did I send nine day-fresh files to the JPEG Full Size batch:

Code: Select all

 "9 versions sent to JPEG Full Size batch"
TIFF Error:  /home/odd/foto/2017/01/2017-01-02/okh-2017-01-02-16-14-44_1.JPG "Not a TIFF file, bad magic number 55551 (0xd8ff)" 
How stupid of me to think a that jpg was a …hey! I never said it was a tiff file!

Code: Select all

exportXMP -  XMP Error  102 ,  Bad XML name
clFatal: status =  -4    "map failed"
Segmentation fault
I rebooted the computer, started Aftershot:

Code: Select all

Container __CATALOG_ROOT__/assets/home/odd/foto/2015/12
throw: VersionAsset::tileStack
terminate called after throwing an instance of 'Berror'
I restarted Aftershot, sent the file to the batch for umpteenth time – nothing happen

The batch I try to use, is not some strange thing I have made myself, but the standard Aftershot batch, and the only alteration I have done to the file, is sharping, vibrancy and lens correction. Non of them from suspect third part plugins; all standard pre installed functions in Aftershot.
Are we alpha testers and not customers? And not only unpaid apha testers, but a flock who are stupid enough to pay Corel for letting us use months of our time, trying to sort out Corel’s problems?

I am seriously considering a switch to Adobe


By the way: As I wrote this did the batch run, and only two of the files had 0 byte…!
Post Reply