Choosing hsv and hsv2 truecolor incoloring and outcoloring mode XaoS screen goes black.

Bug #224705 reported by Sergio Zanchetta
2
Affects Status Importance Assigned to Milestone
XaoS
Unknown
Unknown
xaos (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xaos

XaoS version 3.2-7ubuntu1 on Hardy.

HSV Truecolor modes show Xaos screen all black.
Other incoloring and outcoloring modes show something on the screen.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Strange thing.
If I select "reset to defaults" in Fractal menu, color reappear correctly for two seconds, then XaoS closes.

Changed in xaos:
status: New → Confirmed
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

Other test.
If I select "reset to defaults" not just after starting but waiting some minutes, XaoS show correct colors, and settings are "black" for incoloring and outcoloring Truecolor modes.
But If I select manually "black" for both after starting, screen remains black.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

I forgot to say that when selecting "reset to defaults" after some minutes, XaoS shows correct colors and remains opened.

Revision history for this message
J.B. Langston III (jb-langston) wrote :

@Sergio:

Please check your home directory for a .XaoSrc file, and delete or
rename it if it is there. XaoS should not be using hsv coloring modes
by default. Most likely you have unintentionally chosen "Save
configuration" from the file menu, which will save your current
fractal settings to .XaoSrc, which is read and reapplied every time
you start XaoS.

Revision history for this message
Sergio Zanchetta (primes2h) wrote :

@J.B.
Yes, it's right.
Probably I saved configuration some time ago and I forgot.
Now it starts nice.
Thanks.

description: updated
Revision history for this message
LaserJock (laserjock) wrote :

Marking as Invalid since it seems to just be a user config issue. Feel free to reopen if I misunderstood the above comments.

Changed in xaos:
status: Confirmed → Invalid
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

@ Jordan
You misunderstood last comments.
The config issue was related to facing this bug on xaos start.

Changed in xaos:
status: Invalid → Confirmed
Revision history for this message
J.B. Langston III (jb-langston) wrote :

This is now fixed in upstream the subversion repository. See upstream bug: http://code.google.com/p/gnuxaos/issues/detail?id=8.

Revision history for this message
Scott Balneaves (sbalneav) wrote :

we're now at 3.4. Marking as fix released.

Changed in xaos (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.