Thoughts for Linux beta testers


Posting rules: It shouldn't need saying, but... play nice. Please keep your discussions civil. You can disagree, just don't be disagreeable. And, of course, all of the usual stuff like no spamming. Tex adds: I'll be rigorously enforcing this as we go along. We're probably going to be a small community in a little lifeboat, so we can't have members at each others' throats. This is for the sake of the project as a whole. So when you post, pretend you're speaking in person with your very wealthy auntie who has always treated you wonderfully and currently lists you prominently in her will. I won't be tossing anyone out of the forums because we are all in this together (except spammers: immediate membership cancelation), but I'll delete suspect posts right away.


38 posts / 0 new
Last post
tex
Thoughts for Linux beta testers

These are essentially the same as those for the Windows people:

I'm not actually an experienced Beta Tester, but I'll throw out some thoughts for those of you doing this

1. You'll need to be able to document for us exactly what you are running: All Linux details about versions, & etc, and your machine's specs. You'll need to be a bit conscious of what programs you've got running in the background, if any.
2. What is your camera? If your are working with raws , make sure they are supported!
3. Do stuff you would normally do. If you have a light PP touch, that's fine. If you stomp on your photos, that's fine too. Pay attention to how long things take.
4. We are of course interested in all the aspects of the program, so those of you who do a lot of batch processing, please do that and note if there is a point at which LZ starts to bog down. Time your batch. If you do a lot of B+W conversions, do those. If you have your own templates, see if you can reproduce them, better yet import them, and apply them.
5. Please check the 1:1 view, and whether that bogs down, and under what circumstances.
6. My experience is that LZ began to get slow-ish when around a dozen tools were in play. That's been less true for me with more RAM.
7. If any of you are processing scans of film, especially large scans (MF or LF), see how LZ behaves. My experience is that things got dodgy once you passed the 160mb threshold.
8. Of course please note any changes from your previous version(s) of LZ. I believe there was some missing functionality in Lightcrafts versions for Linux. If you suddenly can't/can do something you used to be able to do/couldn't do, note that and how.
9. Obviously document your problems. Try to reproduce them. There is a log file which ought to be found in My Documents\LightZone. Look for it and save it for forwarding to the Dev Team, especially in crashes.
10. Please try printing if you are set up for that, bordered and borderless.

Anyone else with thoughts, please post them! Good Luck!

sgx2
Not starting on Fedora 18

I've tried the 64-bit and 32-bit rpms, and it seems to be looking for com.lightcrafts.platform.linux.LinuxLauncher which is not in /usr/share/lightzone (32-bit version) or /opt/lightzone (64-bit version)...

UsualUser
Linux Beta Test

Hi Tex,

Tried installing on Ubuntu 10.04 - it is dependent on java 7.0 which is not available in repository

Successfully installed on Ubuntu 12.04 - it choked as described by sgx2:

Starting LightZone version 3.9.1 ...
with options :
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/lightcrafts/platform/linux/LinuxLauncher : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: com.lightcrafts.platform.linux.LinuxLauncher. Program will exit.

Aries
UsualUser: Can you please try

UsualUser: Can you please try upgrading Java to version 7? It should work fine with it.

Apparently Java 6 is installed by default although it is officially unsupported by Oracle now.

flann4lz
No problems with starting

No problems with starting LightZone. K-ubuntu 13.04 64bit. At this time I don't use it only for short playing, more the next time ... I have to go to work now.

Aries
Could you please post the

sgx2: Could you please post the console output?

sgx2
After reading the other

After reading the other comments, I set my java version to OpenJDK 1.7.0 and things started -- now to test!

slocant
How did you do that please?

How did you do that please?

sgx2
First, I made sure I had that

First, I made sure I had that version installed, then I used the command:

alternatives --config java

to switch the default java version to the 1.7.x release

dmpop
No go on Kubuntu 12.10 LTS

I thought I'd give LightZone for Linux a quick try on my production machine running Kubuntu 12.10 LTS. The same issue here:

Starting LightZone version 3.9.1 ...
with options :
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/lightcrafts/platform/linux/LinuxLauncher : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:321)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
Could not find the main class: com.lightcrafts.platform.linux.LinuxLauncher. Program will exit.

Aries
Hello dmpop,

Hello dmpop,
could you please upgrade major version of your Java? Java 7 should work fine.

dmpop
Problem fixed

Turned out that I had both OpenJDK 6 and 7 installed on my system. I've fixed the problem by switching to OpenJDK 7 using the following commands:

$ update-java-alternatives -l
java-1.6.0-openjdk 1061 /usr/lib/jvm/java-1.6.0-openjdk
java-1.7.0-openjdk-amd64 1051 /usr/lib/jvm/java-1.7.0-openjdk-amd64
$ sudo update-java-alternatives -s java-1.7.0-openjdk-amd64

Aries
That is great, thanks for

That is great, thanks for sharing the solution. :)

We should put that to FAQs.

UsualUser
Excellent dmpop! That fix

Excellent dmpop! That fix works for me too.

slocant
Worked for me too. Ubuntu 12

Worked for me too. Ubuntu 12.04 64bits. Although I also got a list of erros after entering that command.

update-alternatives: error: no alternatives for appletviewer.
update-alternatives: error: no alternatives for extcheck.
update-alternatives: error: no alternatives for idlj.
update-alternatives: error: no alternatives for jar.
update-alternatives: error: no alternatives for jarsigner.
update-alternatives: error: no alternatives for javac.
update-alternatives: error: no alternatives for javadoc.
update-alternatives: error: no alternatives for javah.
update-alternatives: error: no alternatives for javap.
update-alternatives: error: no alternatives for jcmd.
update-alternatives: error: no alternatives for jconsole.
update-alternatives: error: no alternatives for jdb.
update-alternatives: error: no alternatives for jhat.
update-alternatives: error: no alternatives for jinfo.
update-alternatives: error: no alternatives for jmap.
update-alternatives: error: no alternatives for jps.
update-alternatives: error: no alternatives for jrunscript.
update-alternatives: error: no alternatives for jsadebugd.
update-alternatives: error: no alternatives for jstack.
update-alternatives: error: no alternatives for jstat.
update-alternatives: error: no alternatives for jstatd.
update-alternatives: error: no alternatives for native2ascii.
update-alternatives: error: no alternatives for rmic.
update-alternatives: error: no alternatives for schemagen.
update-alternatives: error: no alternatives for serialver.
update-alternatives: error: no alternatives for wsgen.
update-alternatives: error: no alternatives for wsimport.
update-alternatives: error: no alternatives for xjc.
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/appletviewer
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/extcheck
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/idlj
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jarsigner
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jar
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/javac
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/javadoc
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/javah
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/javap
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jcmd
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jconsole
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jdb
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jhat
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jinfo
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jmap
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jps
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jrunscript
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jsadebugd
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jstack
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jstatd
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/jstat
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/native2ascii
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/rmic
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/schemagen
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/serialver
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/wsgen
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/wsimport
update-java-alternatives: jdk alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/bin/xjc
update-java-alternatives: plugin alternative does not exist: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
hansemann
Glibc problem on Debian

Hello,
tried to install on "Debian unstable" and got the same errors like "Usual User". Could fix it easily, but got now a problem with the used GLIBC_version.
Debian uses GLIBC_2.13 in moment and Lightzone is compiled and depends on GLIBC_2.14.So I can't see any Nef's , jpeg's or tif's in moment

java.lang.UnsatisfiedLinkError: /opt/lightzone/libJAI.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/lightzone/libJAI.so)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1935)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1860)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1850)
at java.lang.Runtime.loadLibrary0(Runtime.java:845)
at java.lang.System.loadLibrary(System.java:1084)
at com.lightcrafts.app.Application.verifyLibraries(Application.java:1707)
at com.lightcrafts.app.Application.main(Application.java:2163)
at com.lightcrafts.platform.linux.LinuxLauncher.main(LinuxLauncher.java:48)
java.lang.UnsatisfiedLinkError: /opt/lightzone/libLCJPEG.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/lightzone/libLCJPEG.so)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1935)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1860)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1850)
at java.lang.Runtime.loadLibrary0(Runtime.java:845)
at java.lang.System.loadLibrary(System.java:1084)
at com.lightcrafts.app.Application.verifyLibraries(Application.java:1707)
at com.lightcrafts.app.Application.main(Application.java:2163)
at com.lightcrafts.platform.linux.LinuxLauncher.main(LinuxLauncher.java:48)
java.lang.UnsatisfiedLinkError: /opt/lightzone/libLCTIFF.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/lightzone/libLCTIFF.so)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary1(ClassLoader.java:1935)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1860)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1850)
at java.lang.Runtime.loadLibrary0(Runtime.java:845)
at java.lang.System.loadLibrary(System.java:1084)
at com.lightcrafts.app.Application.verifyLibraries(Application.java:1707)
at com.lightcrafts.app.Application.main(Application.java:2163)
at com.lightcrafts.platform.linux.LinuxLauncher.main(LinuxLauncher.java:48)

Olav
Same here

I also had the Java version problem ("Unsupported major.minor version 51.0") that I could fix myself with the update-alternatives command. The openjdk-7-jre was pulled in automatically as a dependency when I installed LightZone with gdebi. After fixing Java I came upon exactly the same problem as Hansemann described. Only difference is that my OS is Debian 7 (since two days, it is the new stable release of Debian). This is the amd64 edition.

Perhaps I am being simplistic, but it seems to me the problem could perhaps be avoided by building the LightZone .debs against a conservative environment such as Debian 7. Am I correct in thinking that they could then be used in every Debian-based distribution that is more up-to-date?

No problems so far on another machine I tried which has Xubuntu 12.10 amd64. Unfortunately this is also one of my oldest and slowest computers, not suitable for anything more than very superficial testing. I.e. does it start, can it load a PEF or DNG picture? Of course so far, the answer is yes.

AsterixEtObelix
Hello,

Hello,

Thanks for the job.

Unfortunately I have the same problem as 2 others above (Olav and Hansemann) - The installation is OK (taking in account that I installed openjdk7 and update the java alternative)

When I launch LightZone I have some error messages stating that the GLIBC_2.14 is not found.

Lightzone application is correctly launch after acknowledging the error message but I can load any raw files.

I ve got DEBIAN WHEEZY (debian 7.0) with amd64 architecture
My camera is a CANON 40D

Aries
The problem really seems to

The problem really seems to be resolvable by building on Debian.

I will be able to do the build on Debian tomorrow.

If somebody is willing to make the build sooner, I can assist with instructions (actually there is documentation for building on Ubuntu, Debian build should be straightforward).

hansemann
great :)

while I expect, that my problem with the GLIBC would disappear in a few days by itself, cause after the new "Debian stable" is released, there would be very much updates coming to the unstable tree in the next days.But the problems for the users of a stable debian system will stay for a long time....
if there are problems with building on debian, I could try to help.
regards and thank you for all the good work!
UPDATE: The expected changes in Debian unstable happend :) and Lightzone is now working for me.It looks promising and seems to work very well...better in some aspects then my old instalation ever did.
Changing to 1:1 view is very fast now and some problems my old lightzone shows in the last year are gone.....fantastic !!!

Aries
Debian packages available

There are now Debian packages available, there is new "debian" folder on the link where you downloaded betas from. You can try them out.

Could you Debian users please tell me what version are you using to have overview where it works?

Olav
No dice

Did you mean the Dropbox link? It now says:

Nothing here
The file you're looking for has been deleted or moved.

(See http://i.imgur.com/QAhgDLt.png)

Looks like Dropbox ate your debs. Boo, Dropbox, bad dog.

Aries
Oh crab! :) I have renamed

Oh crab! :) I have renamed the folder and apparently it made link nonfunctional.
The folder is renamed back and link should work again.

Olav
Thank you, the link works

Thank you, the link works again.

I just downloaded and installed the debian/lightzone_3.9.0_amd64.deb.

The naming of the package is a bit confusing; it actually installs Lightzone 3.9.1, just like the Ubuntu package.

Help->About Lightzone says: Version 3.9.1 (5c2687a)

Installation was completely uneventful (which is good) and I can now open my pictures in LightZone (even better). More serious testing on my part will have to wait until the coming weekend.

Since you asked: my OS is still Debian 7 Wheezy/stable amd64.

UsualUser
LinuxMint Debian Edition

has jre-1.6.0 installed, 1.7 is available.
lightzone_3.9.0-2_i386.deb installs with no problems.
great job.

Chris

Blaze
Where does it go?

I just installed on my Fedora (KDE) box, but I don't see it listed in the menu anywhere. Should it appear in the "graphics" section, or do we need to go find it by hand?

Aries
Hello Blaze,

Hello Blaze,
the LightZone installs into /opt/lightzone. There should be also launch script /usr/bin/lightzone.

For starting try command lightzone in console.

andr345
Hello Blaze,

Hello Blaze,

menu and starticon are considered as "bells and whistles" to me. They will come, but they have not priority for the beta phase.

Olav
Perhaps not everyone realises

Perhaps not everyone realises this, but when testing software on a Linux system it is almost always better to start it from a terminal. That way, one can catch the errors and other messages that are usually emitted by the programme during use.

Blaze
This is one of the reasons

This is one of the reasons that Linux isn't gaining market share: Devs expect everyone to be "advanced users". In an Alpha test, I expect the command line to be used frequently. In a Beta test, that should not be required unless there is a significant problem. It should certainly not be standard procedure to launch from the CL.

The phrase "open a terminal" pretty much guarantees that you've alienated 99.44% of the general market. It's acceptable--even expected--in an Alpha test. But a Beta test is about working out the kinks, not digging into the CL to figure out how to execute basic functions.

Olav
Are you saying one has to be

Are you saying one has to be an "advanced user" in order to type a simple command? That is a sad state of affairs if it is true. One would hope that most computer users pick up a few skills on the way.

Blaze
menu and starticon are
menu and starticon are considered as "bells and whistles" to me. They will come, but they have not priority for the beta phase.

I'm sorry to be blunt, but... "how do I make the program start" is not "bells and whistles". In an Alpha release, sure. In a Beta? No. Absolutely not.

You've fallen into the most common trap for coders: "It's all about the code". As someone who's spent 30+ years working in customer service (in one form or another), I can tell you, with absolute confidence, that "make it easy to start the program" is the #2 priority (after "make sure it doesn't crash in the middle of something important). And.. even that is debatable.

You are marketing a product. If it is not blatantly obvious how to use that product, you will fail. I don't care how great your product is; if it's not easy to use, it will fail.

Look at Linux: It's more powerful, it's more configurable, it's more secure, and it's FREE. Why hasn't it taken over the world? Because the first words out of the mouths of geeks is "open the command line..."

Would you open a coffee shop in the basement of an abandoned building Dane, Wisconsin and tell everyone "I expect you to just find me"?

When you buy a media center from IKEA, and you're presented with a box full of unidentified parts, do you consider the assembly instructions to be "bells and whistles"?

If "make it work" doesn't have priority, you won't get any customers. Remember: This isn't about coding, this is about marketing.

greerd
Where be the log files??

Or is starting from the terminal the only way to see whats going on?

yknot
Never got any emails about Linux Beta

Hi,

I am interested in doing a Linux Beta trial. I am currently running two Gentoo boxes and a Ubuntu 12.04.2 LTS on DUAL and Quad core AMD processors. I also do some programming and would be interested in the source code.

Thanks
PS
I am a forum member and my email is correct. But I am not receiving any email messages from the lightzone project.

baggy
Installed on Puppy Precise and PCLinux OS

Installed OK with help from the above 'hints' thanks! The main problems were getting JRE to the correct version and that Lightzone could locate it. Really great to get this on Puppy Linux as there's the potential to have Lightzone running in RAM from a bootable USB pendrive!!

treedragon
PCLinux OS

Can you offer any hints on how you got it going on PCLinux?
Many thanks

blackmaxphoto
Linux Mint 13 and UBS 12.04

Running LZ 3.9 on both OSs w 3.9 Linux kernel and Oracle Java 8, built LAUNCHERS for each desktop.
Both are running on SINGLE CORE Pentium IV chips with 1 or 1.5G of PC3200, old slow chips and RAM

Mint Maya - Mate desktop
UBS - xfce desktop

... no problems with either install, yet

augras
error java.lang

Hi,

I have got this error as many users with the 4.1.4 and now 4.1.7.

For this error you just need to install javahelp2, without any dependances.

Philippe