Qosmic doesn't launch after building

[GoogleCodeExporter]

What steps will reproduce the problem?
1. ./build.sh
2. ./qosmic
3.

What is the expected output? What do you see instead?
Qosmic should launch. Instead, I see:

xxx@xxx-desktop:~/programmes/qosmic$ ./qosmic 
/usr/share/themes/tropical/gtk-2.0/gtkrc:89: Murrine configuration option
"highlight_ratio" will be deprecated in future releases. Please use
"highlight_shade" instead.
/usr/share/themes/tropical/gtk-2.0/gtkrc:90: Murrine configuration option
"lightborder_ratio" will be deprecated in future releases. Please use
"lightborder_shade" instead.
/usr/share/themes/tropical/gtk-2.0/gtkrc:105: Murrine configuration option
"style" is not supported and will be ignored.
/usr/share/themes/tropical/gtk-2.0/gtkrc:157: Murrine configuration option
"highlight_ratio" will be deprecated in future releases. Please use
"highlight_shade" instead.
error: parsing a double or int attribute's value.
error parsing flame element
Erreur de segmentation

What version of the product are you using? On what operating system?
qosmic 1.4.4 sources on Ubuntu 9.04 Jaunty 64bit

Please provide any additional information below.
Build seems to work correctly. But Qosmic doesn't launch

Original issue reported on code.google.com by chm...@gmail.com on 30 May 2009 at 12:43

Attachments:

• qosmic.pro
• qosmic

[GoogleCodeExporter]

Hi.  Can you attach the flam3 file you were trying to open?

Original comment by bit...@gmail.com on 31 May 2009 at 11:01

[GoogleCodeExporter]

I tried to launch without specifying any flam3 file but it doesn't work (error 
in my
first message).
And it doesn't work too with the flam3 file attached.
I send you the flam3-palettes.xml, could it help you.

Original comment by chm...@gmail.com on 1 Jun 2009 at 2:49

Attachments:

• 01.flame
• flam3-palettes.xml

[GoogleCodeExporter]

Those files look fine.  What are the versions of the flam3 and libxml2 libraries
installed on your system?

Original comment by bit...@gmail.com on 1 Jun 2009 at 8:43

[GoogleCodeExporter]

Flam3:  2.7.18
Libxml2: 2.6.32

Original comment by chm...@gmail.com on 2 Jun 2009 at 5:53

[GoogleCodeExporter]

I'm still not sure what is wrong here, and I haven't been able to reproduce your
problem an Ubuntu.  I'd like to see a backtrace if you can produce one.  The 
problem
with the backtrace is that it may not be useful if the package and it's 
dependencies
are compiled without symbols, and I don't want to ask you to recompile Qt.

You can try to recompile qosmic with debug enabled (in qosmic.pro).  There may 
be
something in the backtrace there that would help.

Original comment by bit...@gmail.com on 3 Jun 2009 at 6:59

[GoogleCodeExporter]

I just noticed that you may have the same problem as the one reported in issue 7
http://code.google.com/p/qosmic/issues/detail?id=7.  Does it run if you use a
different locale?  For example, try  'LC_ALL=C ./qosmic'

Original comment by bit...@gmail.com on 3 Jun 2009 at 7:30

[GoogleCodeExporter]

Yes, it works with an other locale !!!
Thanks
But do you know where it could come from ?

Original comment by chm...@gmail.com on 5 Jun 2009 at 10:11

[GoogleCodeExporter]

We're not sure why this happens, but you are the second person using a 
non-english
locale reporting this problem.  It's too bad that the program doesn't run with 
your
locale.  I was hoping that you might help with some of my translations.

If you're up to it, try version 1.4.2 with your default locale.  This is the 
version
immediately preceding the version containing support for translations.  This 
could
help determine if the problem is something Qt related, or if it's a flam3/libxml
problem.

Thank you for reporting this and following up, 

Original comment by bit...@gmail.com on 7 Jun 2009 at 6:53

• Changed state: Accepted
• Added labels: OpSys-Linux, Priority-High, Usability
• Removed labels: Priority-Medium

[GoogleCodeExporter]

I build version 1.4.2 and I have the same problem:

error: parsing a double or int attribute's value.
error parsing flame element
Erreur de segmentation

Original comment by chm...@gmail.com on 9 Jun 2009 at 5:19

Attachments:

• qosmic.pro

[GoogleCodeExporter]

This may help you:
Icons and translations are not installed in
usr/share/translations
and
usr/share/pixmaps
So, it could be a problem with qosmic.pro

Original comment by chm...@gmail.com on 9 Jun 2009 at 5:46

[GoogleCodeExporter]

Okay.  Now I'm fairly sure it's a problem with flam3/libxml2.   Version 1.4.2 
doesn't
have pixmaps or translations to install.

Can you try to download and run 'flam3-render <simple.flam3' with the attached 
file? 
You should see the same error if this is truly flam3/libxml2 related.

Thank you for trying this.  I'll forward this problem to the flam3 developers.

Original comment by bit...@gmail.com on 9 Jun 2009 at 11:39

Attachments:

• single.flam3

[GoogleCodeExporter]

I meant to say that you should run 'flam3-render <single.flam3'.

Original comment by bit...@gmail.com on 9 Jun 2009 at 11:41

[GoogleCodeExporter]

Bad news: I got no error. The flam3 picture was correctly rendered without any 
error.

Original comment by chm...@gmail.com on 10 Jun 2009 at 3:09

[GoogleCodeExporter]

I was finally able to reproduce your error with qosmic, and you are right.  The 
locale
issue doesn't appear when using the flam3 tools on the command line.  There is
something different about the way Qt handles locales that is causing this.

I've attached a patch for you to try.   After applying the patch and you'll 
need to
run 'make && lrelease ts/*.ts && make install' to regenerate the translations 
before
installing.

Original comment by bit...@gmail.com on 10 Jun 2009 at 5:47

Attachments:

• qosmic-1.4.4-fix-locale.patch

[GoogleCodeExporter]

Great !!!
It works and I can use french locale. Thanks.

Original comment by chm...@gmail.com on 10 Jun 2009 at 7:55

[GoogleCodeExporter]

Nice.  Thank you for testing.

Original comment by bit...@gmail.com on 10 Jun 2009 at 11:16

• Changed state: Fixed

[GoogleCodeExporter]

Issue 13 has been merged into this issue.

Original comment by bit...@gmail.com on 13 Jul 2009 at 7:26

[GoogleCodeExporter]

Issue 14 has been merged into this issue.

Original comment by bit...@gmail.com on 13 Jul 2009 at 7:27