Recent posts

#1
Beginner Talk / Re: Why use DPI (not ppi)? (im...
Last post by Aleks100 - Today at 01:46:51 PM
DPI, for sure. Google dpi vs ppi
#2
Beginner Talk / Re: Why use DPI (not ppi)? (im...
Last post by yichuang驿窗 - Today at 12:39:24 PM
I also think the correct one should be ppi. but I see that both Content Properties and the Scribus wiki are dpi, so that creates confusion.
#3
Beginner Talk / Re: Why use DPI (not ppi)? (im...
Last post by Nermander - Today at 11:03:42 AM
PPI would be the correct term, but for digital media the PPI equals the DPI. I am not aware of any digital format where a pixel is made up of several dots.
#4
Beginner Talk / Why use DPI (not ppi)? (image ...
Last post by yichuang驿窗 - Today at 08:00:43 AM
The location labeled on the attached screenshot uses the DPI.
I looked at the wiki, and the WIKI also mentions that it should be DPI.
Why use DPI instead of PPI?

The screencapture is the Content Properties of image frame.
#5
Linux / Re: Scribus 1.6.2 was not able...
Last post by licheng - Today at 06:39:15 AM
I recompile Python 3.12.4 myself with the "-fPIC" option and install it on Debian 12, then recompile Scribus 1.16.2 and it works fine.

jghali, thanks for the tip, I really appreciate it.
#6
PDF Generation / Re: Signal #11 error on PDF ex...
Last post by buzdam - June 19, 2024, 06:44:04 AM
I'm also facing a similar problem. Let me know if you have fixed this error.
#7
PDF Generation / Re: Pages have a white line
Last post by pickaxen - June 19, 2024, 06:35:36 AM
Thanks for your solutions! I have fixed it.
#8
Linux / Re: Scribus 1.6.2 was not able...
Last post by licheng - June 19, 2024, 04:44:05 AM
Thanks a.l.e and jghali, you're right.

I have a self compiled version of Python (3.12.3), everything works as expected when I remove it.

I'm a long time Scribus user, I use it to make photo books, postcards, posters and zines. I'm used to compiling Scribus myself just to make sure I can use Scribus no matter what OS I have.



Thank you for your great help.
#9
Linux / Re: Scribus 1.6.2 was not able...
Last post by jghali - June 18, 2024, 03:17:08 PM
I installed a Debian 12 virtual machines yesterday and managed to build Scribus 1.6.2 on it successfully. But Debian 12 comes with Python 11, not 12, so I also suspect a custom Python, presumably built without -fPIC option.
#10
Linux / Re: Scribus 1.6.2 was not able...
Last post by a.l.e - June 18, 2024, 10:36:39 AM
sometimes, i wonder if people have lost the skill to copy paste text and only can do screenshots : - )

anyway, for the little that is visible in the screenshot, i would say that this is not a "typical" error due to missing dependencies.

i googled the error "against hidden symbol pkgcontext" and this is what i've found:

https://stackoverflow.com/questions/19768267/relocation-r-x86-64-32s-against-linking-error

since you're compiling a release version of scribus, instead of using a binary (packaged by your distribution or in the appimage), i wonder if you also have a self compiled python, with incompatible flags (as the stackoverflow answer hints).

another source for the issue, could be that you're mixing old and new compiled files, while having had an update of system installed libraries...
but you seem to use a "scribus-1.6.2" which seems to hint to a newly created directory.