1. My first recommendation, for people learning Scribus, would be to use the current stable version - currently 1.4.6 - rather than the latest development version. Development versions - while being mostly usable - can contain "hidden" bugs from changes or new features that haven't yet been properly integrated into the code. This can lead to the development software doing strange things that the stable version doesn't.
Also, development versions may contain features that don't make it into later stable versions of the software. In these cases it might mean that your documents can't be loaded into future versions of the software that don't contain those features. You would have to maintain multiple versions of Scribus while remembering which version to use on different documents.
Bottom line: Unless you're specifically doing development testing, and/or really know what you're doing, use the current stable version instead of a development version.
2. My second recommendation, for people wanting answers to problems, would be to give the forum members as much information about the problem as possible. I realise that it's difficult to know what information to give as you might not know what's relevant but, at the very least, let people see everything that you can see.
If you're providing a screen shot then it's best to give the whole screen - or failing that, the whole Scribus window. Just a portion of the screen may not give enough information. For instance, in the provided screen shot it looks like there's a two-column text frame being used and there looks to be something odd at the start of the second column but we can't see what's at the end of the first column. This means that we don't know what the full context of the problem is. In this instance, what's at the end of the first column may be important to figure out what's going on in the second column. It might not but we can't tell. Taking a screen shot of everything is as easy as it is for just a part of the screen so why restrict the information given?
Bottom line: If you want help then help the people you're asking help from by giving them as much help as you can.
Note: If your screen shot contains sensitive information that you don't want other people to see then you can use something like GIMP to quickly blur sections of the image.
3. The best way to give the forum members as much information as possible is to use the "File -> Collect For Output" function. By using this function you can create a new folder which will contain a copy of the document, copies of all of the images used, and - if you use the right check boxes - copies of all of the fonts and colour management information used in the document.
Once this new folder has been created you can ZIP it and post the ZIP on the forum (as long as the size of the ZIP doesn't break the forum limits, in which case you could add a link to some cloud storage instead). This provides people with a neat package of everything that you're using and makes it much easier to see what's going on. Essentially they're working with the same document that you are.
There is, however, one caveat that brings us back to my first point, and that is that if you collect your output from a development version of Scribus then you are restricting the number of people who can help you to only those that have the same development version installed on their machine that you're using.
For instance, if you collect the output from version 1.5.2 then the only people who can properly check your work are people who have 1.5.2 installed. Version 1.5.1 might not work the same way as 1.5.2, or 1.5.0, or any other development versions so whoever tries to find out what the problem is using a different version might not get the same results as you. To add to the problem, there will be many different versions of, for instance, 1.5.2 depending on when different individual's software was compiled and each version will work differently in different ways. This makes it more important that you stick with the stable version unless you really need something from a development version.
Bottom line: If you want someone to be able to really look at a problem properly then collect your output and post a ZIP but be aware that collecting the output from development versions can make things more awkward for people wanting to help.
Note: Be aware of the copyright situation of the images and fonts you collect for output. By collecting for output and posting a ZIP with them in you are essentially distributing them and could be doing so illegally if they have copyright restrictions. Just make sure that everything is okay before posting.
Epilogue. I hope I haven't scared anyone away from using the forum by saying all of this. I've tried to keep the tone light but they are important issues. No-one on the forum gets paid to help. We give our free time to help others so it's nice if people help us by not giving us too much extra work to do.
(AdeSmith, what I've said is relevant to your original post but it's not specifically targeted at yourself. It's just general information for anyone who reads the forum, I'm not "having a dig".)