Recent Posts

Pages: 1 2 3 4 5 6 [7] 8 9 10
I just wanted to thank you for the extremely fast and accurate answer.  I did not expect an answer for quite some time as it is in most forums I use.
Your suggestion solved my problem, so thanks a lot.
A++ for this forum.
Linux / Re: Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by scriber on August 09, 2017, 07:54:29 pm »

Ponce told me you are interesting to our magazine.
It's a 20/30 pages local journal that is published 3 or 4 times a year, in which  we report local events, main facts, old stories and photos related to the local little village, various ideas to contribute to the village and so on.

The magazine was produced by a friend of mine using ms publisher, then she asked if I could help the project and replace her in that task .
But I'm using Linux so I usually prepare images and text from the rest of the "staff" and then I use Scribus for the final layout and to export to PDF for the printing works.
Nothing special!  :)

I'd like to try the unstable version to see if there are some new features suitable for my needs. I was just curious.
I tried a little the AppImage version of Scribus 1.5.3 and I think it is very similar to my usual 1.4.6 version. Anyway I want to try it a little more...
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by GarryP on August 09, 2017, 03:05:00 pm »
You're welcome Derek.

You should be okay transferring Scribus documents from one OS to another but make sure you use "File -> Collect for Output" to gather all the images and fonts (and more) together in a ZIP so that the other people get everything. This is because a Scribus document doesn't - normally - contain images or things like that. Instead, it links to the things like images on the disk, which makes the SLA file smaller and lets you change the image without needing to change anything in Scribus.

It's worth pointing out - as a general point to anyone reading this - that one issue you might have when transferring documents is when someone uses fonts that have copyright issues. This is too big an area to explain here but if you make sure you only use fonts that are freely available on all OSes then you shouldn't have too much of a problem. If in doubt, use fonts from a reputable supplier of free fonts (a few examples are here: ) and you shouldn't go wrong.

I know that there are some 1.4.6 functions that don't work in some OSes - e.g. the colour picker doesn't work properly in OSX - but most of the usual stuff should work just fine on all systems. Also, a little while back there was an issue with colour management on Linux Mint (,2464.0.html ) but I don't know if this has since been resolved.

The stable version of Scribus can help you to produce lots of different things (some examples here: ) so, unless you have some specific requirements - RTL text, special PDF version, etc. - you can probably do whatever you want. You can also have a look at the "Showcase" section of this forum (,3.0.html ) for some more examples of what Scribus can produce. (All of the things produced by me were done with 1.4.6 - or earlier - in conjunction with other products such as GIMP and Inkscape.)

Can the contributor that uses Publisher give you output as PDF? If you don't need to edit what they give you then you can create page-sized image frames and import the PDF into those frames. Then set each each frame to display the correct page using the "Page Number" setting in the Properties Palette / Image tab. You can then add page numbers - or whatever - over the top of the image frames to make them fit your publication. (The PDF might look a bit fuzzy on-screen - even with the Preview Settings set to Full Resolution for some reason - but it should export just fine. Try it and see what you think.)

One other thing I might just mention is that Scribus has a Greyscale output function in "File -> Export -> Save as PDF / Colour / Output Intended For". You might like to experiment with this but I've not used it myself so I can't say how well it works. Just something that might be worth knowing.
Linux / Re: Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by a.l.e on August 09, 2017, 02:59:38 pm »
yep, i think that the best thing is now to see what the team thinks of the ticket.

as u told to ponce on irc, i fear that the problem is in slackware though.
Linux / Re: Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by scriber on August 09, 2017, 02:45:45 pm »
You can find  more details at:
Thanks to Ponce who is helping to test the software:

Moreover he tried the SVN version as you suggested, but reported the same issue with "segfault error".

Some other info at:
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by Derek on August 09, 2017, 12:40:49 pm »
Thank you. Garry and a.l.e. All very good points.

The one about handing over a file that'll only open in a development version of Scribus is, I think, the show-stopper. I have past experience with software design,  development and testing but, TBH, I'm not finding the learning curve for 1.5.3 easy and It would be unreasonable to expect others to be happy with it.  Given the exceedingly long history of the transition from 1.4 to 1.6 I cannot be confident that the next stable release will be launched any time in the next couple of years. Certainly not a complaint - just the way it is and what I have to plan around. I'll also need to test that what I produce in Linux also works in Windows (but I won't be able to test OS/X).

I'll be installing the current stable release today. I'll then need to see how it differs from 1.5.3 and see if it can do all I need to do. The magazine is probably not the most complex publication being produced in Scribus and, being greyscale due to printing limitations, simpler than most. I'd be surprised if the official current stable release can't cope.

The real attraction to 1.5.3, for me, was the possibility of being able to open Publisher files but, TBH, that doesn't appear to be working well for me at the moment. I seem to be gravitating to creating the magazine from scratch, which gets me through the learning curve quicker. I have a contributor who sends copy in Publisher format but that's only a bit over 2 pages a month. I'm not about to push her into the Scribus learning curve. In the worst case - open it in Publisher and copy/paste the components out or save it as an image.

Linux / Re: Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by a.l.e on August 09, 2017, 11:57:42 am »
with so little details on what's installed in your computer and what exactly is the error (if you run scribus inside of a debugger (gdb) you might get more details).

what you can try is to get the current trunk sources (from the team's svn or from github community mirror), compile that code and see if it works.
this might or not be different than what slackbuild is doing.
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by a.l.e on August 09, 2017, 11:55:11 am »
garry is right.

one small complement from my side: start with 1.4.

if you're happy with stick with it.

if you miss something important, try 1.5 and see if it's fixed / implemented there.

at the end judge what you prefer. keeping in mind that 1.5 is a moving target. it moves slowly, but it moves (in big leaps if you stick to the development releases and don't use the latest snapshots)
General Discussion / Re: Another Possible New Scribus User Looking For A Path
« Last post by GarryP on August 09, 2017, 11:23:13 am »
Welcome to the forum Derek.

Personally I would advise that you use the current stable 1.4.6 version of Scribus rather than any developmental version. There are various reasons for this, some of which are listed below:

The stable version has been around - without changes - for at least 18 months. This means that almost all of the usual bugs and weirdness have already been encountered and fixes/work-arounds are known. Because of this, if you come up against a problem it's likely that someone else has already been in the same situation and can advise on what to do. Also, more people are using the stable version so, even if you have a unique issue that's not been seen before, there are more people that are likely to be able to help and get you back up-and-running quicker (very handy if you have deadlines).

Some people are not comfortable with using developmental versions of software. Because of this, if you expect that someone else will take over the reins of editorship, using the stable version will mean that more people could be potential candidates. I.e. If you use 1.5.x and try and pass it on to someone who will only use 1.4.6 then they're not going to be able to edit the document as 1.4.6 cannot open 1.5.x documents. Best to keep to the version that most people will be comfortable using.

While the Scribus team frequently suggests that the core of the developmental versions is pretty stable for most users, if you are coming to Scribus afresh then it will be practically impossible for you to know which functions are core functions and which are not. This means that you will have no way of knowing which functions you should stay away from because they could cause trouble. As you don't know which functions are experimental you could end up having a lot more problems than you would wish for.

It can also be more difficult to get the latest developmental version of Scribus up-and-running. There are usually builds for Windows and OSX but I've heard that it can be difficult to get 1.5.x running on Linux depending on which version of which flavour of Linux you're using. And any future editor may not want to change Linux flavour just to use Scribus.

Also, the latest developmental version can change significantly from time to time which means that the developmental version that you use could be very different from one that someone else is using. Because of this, you could encounter problems where some functions either no longer exist or work in very different ways. Passing documents between people using different developmental versions could be a nightmare (especially if you have deadlines).

In addition to this, documentation for Scribus is patchy at best, and that's for the latest stable version. Most of the documentation that exists was written prior to 1.4.6 but is still pretty relevant to 1.4.6. A lot of the UI for 1.5.x has changed quite considerably and so most of the current documentation would have to be interpreted - rather than just followed - and that will make the learning experience much harder than it needs to be. Documentation for the developmental versions of Scribus - especially the new functionality - may not be around for a long time (if ever), so experimentation may be required.

So, all said, I would stick with 1.4.6 if I was you. It's been around for ages, how it works is well-known, and it's more accessible to more people.

As for your longer-term goal of importing content into Scribus, that's something that could well be possible but it really depends on specifics and how much you want to automate things. Probably best not to think about this until you need to go down that road. Once you need to think about it I'm sure there will be people who can help.

I hope what I've said has made it easier for you to decide on your next steps.
Linux / Scribus-1.5.3 Segfault on Slackware-14.2
« Last post by scriber on August 08, 2017, 08:36:23 pm »
Hi all,
I'd like to try scribus 1.5, but my seems to be just a 1.4.6 package for linux distribution: Slackware 14.2 64 bit.
I finally found a "Slackbuild" script to create a package of 1.5.3 scribus version, so I prepared the building directory and then launched the compile. All seemed working for the best: no errors returned and a new package installed.

But... when I launch "scribus" from the shell it return "segmentation fault". Why?
How could I know what's the problem?

Is there some slackware user that work with a working 1.5.x Scribus version?

Thanks a lot in advance!
Pages: 1 2 3 4 5 6 [7] 8 9 10