Recent posts

#61
MacOS / Re: Scribus 1.6.3 does not run...
Last post by lexfiend - February 08, 2025, 04:56:15 PM
Just tried installing Scribus on an M1 Mac mini running Monterey, which has never seen Scribus before. Same steps as before, but this error dialog sheds a bit more light on the problem. Still trying to figure out how to upload the screenshot, but the subtext in the error dialog reads (emphasis mine):

You have macOS 12.6.5. The application requires macOS 15.0 or later.

Sorry, but that looks like a build config issue to me.
#62
MacOS / Re: Scribus 1.6.3 does not run...
Last post by lexfiend - February 08, 2025, 04:41:36 PM
Sidenote: I've been installing Scribus via Homebrew for quite some time now, and never had any issues until the 1.6.3 update. That's when I tried the manual download and got the same result (which I was already half-expecting since Homebrew uses the same DMG, but I decided to try the manual way just in case).
#63
MacOS / Re: Scribus 1.6.3 does not run...
Last post by lexfiend - February 08, 2025, 04:36:50 PM
OK, here's what I did on my M2 MacBook Air (Mac14,2) running Sonoma:

1. Use AppCleaner to remove all traces of Scribus, including the preferences and app support directories.
2. Double-click on scribus-1.6.3-arm64.dmg, dated 2025-01-08 when downloaded from SF.
3. Drag the Scribus icon to the Applications folder icon.
4. file /Applications/Scribus/Contents/MacOS/Scribus reports Mach-O 64-bit executable arm64 as expected.
5. Double-click the Scribus app icon in /Applications folder in Finder, immediately get the "you can't use this version of the application" error dialog that dragginDaybrake posted.
#64
MacOS / Re: Scribus 1.6.3 does not run...
Last post by MrB - February 08, 2025, 01:40:29 PM
I'll try another build and uploaded to SourceForge later.
#65
MacOS / Re: Scribus 1.6.3 does not run...
Last post by MrB - February 08, 2025, 01:26:38 PM
It works for me on M1 and M4 Mac Minis. Drag the app from the dmg and open it. You'll need to provide permissions for the OS to run the app considering it was downloaded. open -a works after that.

I got this:
open -a ~/Downloads/scribus-1.6.3-arm64.dmg
The application /Users/craig/Downloads/scribus-1.6.3-arm64.dmg cannot be opened, error=Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"

Then, when I run it from the icon, it opens, I provide permissions to open as I redownloaded it.
After that, open -a works fine.

Otherwise, you're going to have to provide system details. Either way, my M1 and M4 systems are running Sonoma. My M1 Mac mini is a Macmini9,1 and the oldest OS compatible is Big Sur, which is the minimum OS set for the App. Make sure you've dragged the app out of the dmg.

#66
MacOS / Re: Scribus 1.6.3 does not run...
Last post by dragginDaybrake - February 08, 2025, 12:14:36 PM
Quote from: lexfiend on February 08, 2025, 09:35:14 AMThe issue seems to be a packaging error for the ARM64 app bundle, which is something the Scribus developers will have to fix. This problem is definitely NOT solved.

Thanks for digging a bit deeper on this issue. I definitely have Rosetta installed.
I have unmarked the post as solved.
#67
MacOS / Re: [SOLVED] Scribus 1.6.3 doe...
Last post by lexfiend - February 08, 2025, 09:38:16 AM
Quote from: MrB on January 25, 2025, 10:08:37 PMI downloaded it again from SF and it works for me

I downloaded it again from SF and it didn't work for me:

% open -a /Applications/Scribus.app
The application /Applications/Scribus.app cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10825 "kLSIncompatibleSystemVersionErr: The app cannot run on the current OS version" UserInfo={_LSLine=4127, _LSFunction=_LSOpenStuffCallLocal}

but I can run the binary directly:

% /Volumes/Scribus/Scribus.app/Contents/MacOS/Scribus
Path = /Volumes/Scribus/Scribus.app
"scpaths: bundle at /Volumes/Scribus/Scribus.app"
"scpaths: doc dir=/Volumes/Scribus/Scribus.app/Contents/share/doc/scribus/"
"scpaths: icon dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/icons/"
"scpaths: font dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/fonts/"
"scpaths: sample dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/samples/"
"scpaths: script dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/scripts/"
"scpaths: template dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/templates/"
"scpaths: lib dir=/Volumes/Scribus/Scribus.app/Contents/lib/"
"scpaths: plugin dir=/Volumes/Scribus/Scribus.app/Contents/lib/"
"scpaths: QML dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/qml/"
"scpaths: qtplugins=/Volumes/Scribus/Scribus.app/Contents/PlugIns:/Volumes/Scribus/Scribus.app/Contents/MacOS"
qt.qpa.fonts: Populating font family aliases took 62 ms. Replace uses of missing font family "Helvetica Regular" with one that exists to avoid this cost.
Fontconfig error: Cannot load default config file: No such file: (null)

so something's wonky with the ARM64 app bundle, at least for folks outside Scribus HQ.
#68
MacOS / Re: [SOLVED] Scribus 1.6.3 doe...
Last post by lexfiend - February 08, 2025, 09:35:14 AM
Quote from: dragginDaybrake on January 29, 2025, 05:16:38 PMIt turns out that the Arm build and the Intel builds of 1.6.3 of mixed up.

Sorry, but no, the DMGs are the right way round.

# after mounting scribus-1.6.3.dmg
% file /Volumes/Scribus/Scribus.app/Contents/MacOS/Scribus
/Volumes/Scribus/Scribus.app/Contents/MacOS/Scribus: Mach-O 64-bit executable x86_64

# after mounting scribus-1.6.3-arm64.dmg
% file /Volumes/Scribus/Scribus.app/Contents/MacOS/Scribus                                                                                               
/Volumes/Scribus/Scribus.app/Contents/MacOS/Scribus: Mach-O 64-bit executable arm64

# I can't start the ARM64 app in the usual way...
% open -a /Volumes/Scribus/Scribus.app
The application /Volumes/Scribus/Scribus.app cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10825 "kLSIncompatibleSystemVersionErr: The app cannot run on the current OS version" UserInfo={_LSLine=4127, _LSFunction=_LSOpenStuffCallLocal}

# ...but I can run the binary directly
% /Volumes/Scribus/Scribus.app/Contents/MacOS/Scribus
Path = /Volumes/Scribus/Scribus.app
"scpaths: bundle at /Volumes/Scribus/Scribus.app"
"scpaths: doc dir=/Volumes/Scribus/Scribus.app/Contents/share/doc/scribus/"
"scpaths: icon dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/icons/"
"scpaths: font dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/fonts/"
"scpaths: sample dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/samples/"
"scpaths: script dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/scripts/"
"scpaths: template dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/templates/"
"scpaths: lib dir=/Volumes/Scribus/Scribus.app/Contents/lib/"
"scpaths: plugin dir=/Volumes/Scribus/Scribus.app/Contents/lib/"
"scpaths: QML dir=/Volumes/Scribus/Scribus.app/Contents/share/scribus/qml/"
"scpaths: qtplugins=/Volumes/Scribus/Scribus.app/Contents/PlugIns:/Volumes/Scribus/Scribus.app/Contents/MacOS"
qt.qpa.fonts: Populating font family aliases took 62 ms. Replace uses of missing font family "Helvetica Regular" with one that exists to avoid this cost.
Fontconfig error: Cannot load default config file: No such file: (null)

I suspect the reason downloading and installing the Intel app bundle worked for you is that you have Rosetta installed. For someone else who hasn't installed Rosetta, it'll fail miserably.

The issue seems to be a packaging error for the ARM64 app bundle, which is something the Scribus developers will have to fix. This problem is definitely NOT solved.
#69
PDF Generation / Re: Scribus File Not Opening U...
Last post by utnik - February 07, 2025, 09:56:31 AM
hi cdjr398

Quote from: cdjr398 on February 07, 2025, 04:53:19 AMI had several versions that I had done in Scribus. I cut and pasted from there mostly. I was hoping not to have to start from scratch.

when i had to clean your file, i would just do that: starting from scratch.
the structure of the file is unbelievably complex. the last page contains 54 text frames. i would either make it one or two. (as a side effect, texts on the same line would be exactly at the same height, not more or less near the same height...)
you didn't use paragraph styles and character styles. everything is set with direct formatting. this makes the file almost not editable.
i would place the page numbers on the master pages. then they would be at the same plage on every page. (if you really need this unusual pagination with odd numbers on the left page, you can define this in 'file' → 'document setup' → 'sections'.)

i tried to find the reason of this acrobat-reader-issue. but the complex structure of the file would make this harder than rebuilding the layout in a sane way.

if this was my file and my job to make it work, i would use the .pdf file on a background layer (maybe with 30% opacity) and rebuild the whole layout on top of it. maybe with one layer for the images and one for the rest, but not more... (after rebuilding you can just delete the background layer.)
i would do all the formatting with paragraph styles and character styles to keep it editable and clean.

i'm sorry, not to tell you an easier way. but it's a bit of a project for a first layout work in scribus. there is always some learning curve.

here you find a good scribus manual. it's not based on the newest version of the program, but the basics still work.
maybe you don't need to read the whole manual. on the left you find the themes you need. (i.e. styles)
the most important change between tis manual and the actual scribus versions ist the 'content properties' palette. in earlier versions the properties of content of a frame (image, text...) have been edited on a tab of the 'properties' palette of the frame. that's what the manual still suggests.
but if you know about the 'content properties' palette, this is not a big problem.

utnik
#70
PDF Generation / Re: Scribus File Not Opening U...
Last post by cdjr398 - February 07, 2025, 04:53:19 AM
I had several versions that I had done in Scribus. I cut and pasted from there mostly. I was hoping not to have to start from scratch.