Known bug in Dolphin Viewer 3.1

There is a bug in all versions of Dolphin Viewer 3.1 that makes the viewer crash whenever you import an AO notecard by dropping it on the AO Floater.

As a workaround you can set up the AO manually. I’m working on a fix but it is slow going right now, for reasons outlined as follows:

As some of you might know I use the openSUSE build service to work on the Dolphin Viewer.

With the recent release of openSUSE 12.1, the build service is so totally swamped with everybody scrambling to get last fixes in their projects, that it currently takes about two days to build a viewer there. Whereas before, it used to take two hours. Just a little example: a package of the latest firestorm that I was trying to buid took twelve hours to go from 76% to 90%…

With such turnaround times there’s not much I can do right now.

Since I have a couple of to do items that I have to address before I can release the next Dolphin Viewer 3 (which will be based on 3.2 sources and Marine Kelley’s latest RLV, and have a couple of other shiny things that you will like a lot), I’ll postpone the next releases until the build service has a bit more breathing room.

Besides, I gotta update mine and Lapis’ laptops to 12.1 first anyway.

Why am I not building at home you ask?

My linux build environment at home is a Debian 5 in a VirtualBox VM on a Mac Mini. Good enough to crunch out release packages over night, but for a development cycle? Forget it.

So stay tuned.

5 thoughts on “Known bug in Dolphin Viewer 3.1

  1. I’m not sure if it is just me or if this is happening to other people but on the latest version of dolphin viewer 3 if i open build or try to edit item, I crash.
    This did not happen until i updated to the newest version of Dolphin 3.
    And it does not happen in the newest sl viewer of dolphin 2.

  2. I cant post on the forum because i am having trouble with the registration. It says i need to enter the confirmation code. Instead of a code in the box next to it all i get is this. ‘An internal error occurred: 4B21C4C9842B0.A0D7D11.12AA’

Comments are closed.