Most frames all black after reinstall

Previous topic - Next topic

ulfa

During windows update recently I had to install scribus. Most text frames are all black but the text is visible in the editor window. In properties window the colors is showing black in left column. I have installed 1.5.4 and gs 9.23. windows 10 latest version. What have happened? What can I do to get back to normal?

a.l.e

I've never heard of such an issue...

Can you share a file where you see all black?

ulfa

I begin with a screen cut

[attachment deleted by admin]

ulfa

Looks like all background colors are set to black. If none is used it will be tranparent but in all other cases black. My partner have the same problem after windows update now in april 2018. We are using the same styles.

ulfa

UPDATE:
When I am making a new document and a frame I can set background colours as expected. Copy paste a frame from the "black and wrong" document adding a number of colours to select from. All these new colours have regular colour-names but shows black. They are all marked as a type "L in a square". What is the meaning of this L-type? Looks like the problem is there.

The work around is to make a new document and hope to stay away from "L-type" colours. My fear is however that this misbehaviour is ralated to the windows update in april. Both my fresh install of 1.5.4 and my collegues present 1.5.3 shows the same symtom after latest win 10 update.

[attachment deleted by admin]

a.l.e

can you please share one of the documents?

thanks
a.l.e

ulfa

How can I sent it: I dont want it public.

utnik

hi ulfa

i have never seen this in scribus 1.5.4. but when i open a file from scribus 1.5.4 with 1.5.3 this is the usual behavior – at least with my files.
the way scribus deals with colors has changed in some way between 1.5.3 and 1.5.4 – there's no backward campatibility.

do you really see this in scribus 1.5.4?

utnik

ulfa

My collegue made the document in version 1.5.3. It is a regular four page information document. Each version starts with a copy of last and reworks with new content. I was not involved at all. In the meantime my PC went down during an update of win 10. After a repair of win 10 i installed latest scribus 1.5.4 and gs923w64.exe. My collegue made the same win 10 update and got the black frames when loading the document again in 1.5.3 and requested help. The same black frames showed up in my pc with 1.5.4. 

a.l.e

ulfa,

you can send me a private message with a link where i can download a file or ask me for my email address where you can send the .sla file.

but i'm more and more thinking that people who are not ready to upload a file for inspection (because they fear being stolen?) should send me 10 units of a common currency (dollars, euros, franks, pounds, ...) per post mail...

or i should setup a tipping account somewhere? : - )
i have to think about it...

now, you already have set me a private message and you just got a reply from with instructions...

ciao
a.l.e

a.l.e

i got the .sla and all the colors are defined as almost black...

do you have a backup of a file that still has the "correct" colors?

ciao
a.l.e

ulfa

The backup file is much older and not with the final content. The colours looks however ok in that file. As you don't have a simple answer that explains the behaviour I believe the best way is to start with a earlier version next time and hope the black frames were created by our mistake and not something in the program code. Next issue is in the end of june. If this occur again I will be back. So far many thanks for your engagemant.

a.l.e

ulfa, it's about finding out what has happened and trying to identify the bug.

all colors in your .sla are in LAB format and the L and A values are zeroed.

it would be interesting to know if you always had the colors in LAB format or if they originally were RGB.
since most colors come from SVG files, i would guess that they used to be RGB...

that's way it would be interesting to see an older .sla and know from you if you did change any color setting inbetween.

a.l.e

i got jean to have a look at this thread and he noticed what is the likely issue:

"you" seem to have opened a 1.5.4 file with 1.5.3...
that might have triggered the issue!

please be aware that:

- there is no promise of compatibility between development branches (it mostly works ok, but there is no promise made! on the other side, much more effort is done for the upgrades from a stable version to the next...)
- it's not "possible" to add a warning in 1.5.3 when opening a file created with 1.5.4 (1.5.3 is a "dead" branch that does not get any updates anymore)

hth
a.l.e

ulfa

#14
I have sent a file from March 2018 to a.l.e . That file was the base for next issue edited in May 2018. It is important to say that the error occured in 1.5.3 but in connection with the windows 2018-03 update.