Scribus Forums

Scribus => Installation and Setup => Linux => Topic started by: Archibaldix on September 15, 2020, 06:16:44 pm

Title: Unable to start Scribus after an update
Post by: Archibaldix on September 15, 2020, 06:16:44 pm
Dear all,
Has anyone ever had the following problem:
After updating my system, I cannot launch Scribus.
I uninstalled it then reinstalled it 5 times : it doesn't work.
When I run the program the result is: nothing opens, not even a welcome image ...
I have searched on lots of places I can not find any solution...

I notice there is maybe something related with a bad font ? I did not venture in that direction, not knowing how to do it.

I also don't know which command line I have to indicate here to be able to find a help.
I run Linux Mint 19.2 Tina on a MacBook Pro i7 Mid-2010.

In advance Thank you very much for any help
A.
Title: Re: Unable to start Scribus after an update
Post by: dragonfly on September 15, 2020, 08:40:34 pm
Since you are running Linux (I am on Ubuntu 20.04) it should be easy to run through some troubleshooting tests.

First can you run in terminal

scribus -v

to read the version.

Next

scribus -h

to see the options.

Next since you mention fonts run

scribus -fi

to get font info.

And so on until you can pin down why scribus does not run.
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 16, 2020, 12:16:09 am
Hello & thank you very much for the fast reply :

When I write the codes there is already a problem :
Code: [Select]
root@gvp-MacBookPro:/home/gvp/.scribus# scribus -v
scribus: symbol lookup error: scribus: undefined symbol: _ZN12QApplication10commitDataER15QSessionManager

And same with scribus -h & scribus -fi. It's strange no ?

Looking at this strangeness I find a similar error in an old post here : https://forums.gentoo.org/viewtopic-t-438568-start-0.html
They talk about an error with QT but I don't know what it is.

The code ldd /usr/bin/scribus is giving me the followed result :

Code: [Select]
root@gvp-MacBookPro:/home/gvp/.scribus# ldd /usr/bin/scribus
linux-vdso.so.1 (0x00007ffc58ddd000)
libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007f89796d0000)
libQtGui.so.4 => /usr/local/lib/libQtGui.so.4 (0x00007f8978965000)
libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007f897871f000)
libQtNetwork.so.4 => /usr/local/lib/libQtNetwork.so.4 (0x00007f897840a000)
libQtCore.so.4 => /usr/local/lib/libQtCore.so.4 (0x00007f8977f29000)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x00007f8977c75000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x00007f8977a30000)
libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5 (0x00007f89777b9000)
libjpeg.so.8 => /usr/lib/x86_64-linux-gnu/libjpeg.so.8 (0x00007f8977551000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f8977334000)
libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x00007f89770a8000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f8976ea4000)
liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 (0x00007f8976c4c000)
libpodofo.so.0.9.5 => /usr/lib/libpodofo.so.0.9.5 (0x00007f89768a9000)
libhyphen.so.0 => /usr/lib/x86_64-linux-gnu/libhyphen.so.0 (0x00007f89766a3000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f897631a000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f8975f7c000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f8975d64000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f8975973000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f8975754000)
libpixman-1.so.0 => /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 (0x00007f89754af000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x00007f897527d000)
libxcb-shm.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-shm.so.0 (0x00007f897507a000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f8974e52000)
libxcb-render.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-render.so.0 (0x00007f8974c45000)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f8974a3b000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f8974703000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f89744f1000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f89742e9000)
/lib64/ld-linux-x86-64.so.2 (0x00007f897a854000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x00007f89740b7000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f8973e91000)
libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0 (0x00007f8973c83000)
libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f8973a38000)
libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f89736d2000)
libavahi-common.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-common.so.3 (0x00007f89734c6000)
libavahi-client.so.3 => /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 (0x00007f89732b5000)
libidn.so.11 => /lib/x86_64-linux-gnu/libidn.so.11 (0x00007f8973082000)
libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f8972bb4000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f89729b0000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f89727aa000)
libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f89724d4000)
libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f89722a2000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f897209e000)
libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f8971e93000)
libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007f8971b64000)
libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x00007f8971945000)
libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x00007f89715c7000)
libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f89713b4000)
libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x00007f897117e000)
libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x00007f8970f4a000)
libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f8970cc9000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f8970a7c000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x00007f8970867000)
libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f8970663000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f8970448000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f8970240000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f896ffbc000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f896fda0000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f896fa84000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f896f86f000)

Does this help?
Thanks,
A.
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 16, 2020, 12:31:28 am
which version of scribus did you install?

from where did you get it?

somehow, it looks like you're trying to start a scribus 1.5 on a system with qt4 or a scribus 1.4 on a system with qt 1.5...
Title: Re: Unable to start Scribus after an update
Post by: dragonfly on September 16, 2020, 12:34:26 am
I agree. A cursory comparison of my output using same ldd command gives this ..


libQt5Xml.so.5 => /lib/x86_64-linux-gnu/libQt5Xml.so.5 (0x00007f679bcc1000)
libQt5Network.so.5 => /lib/x86_64-linux-gnu/libQt5Network.so.5 (0x00007f679bb00000)
libQt5OpenGL.so.5 => /lib/x86_64-linux-gnu/libQt5OpenGL.so.5 (0x00007f679baa4000) libQt5PrintSupport.so.5 => /lib/x86_64-linux-gnu/libQt5PrintSupport.so.5 (0x00007f679ba2b000)


I have ignored the dependencies which are identical when comparing outputs.

It is clear that Qt5 dependencies are missing.

[P.S.] A further quick search found this which might help explain Qt4/Qt5 de[endencies for different versions of Scribus (I use version 1.5x)

http://lists.scribus.net/pipermail/scribus/2013-October/049425.html.

https://wiki.scribus.net/canvas/Building_SVN_versions_with_CMake#Version_1.5.x


Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 16, 2020, 09:13:42 pm
Okay, I surrender. Few hours spent finding the solutions but it doesn't work.
So i followed the page mentionned, this one : https://wiki.scribus.net/canvas/Building_SVN_versions_with_CMake#Package_Manager
I installed subversion, c++
I Installed QT
I think i installed cmake also but not sure
I downloaded the scribus files which is now on place
I installed the list of dependencies suggested

But then, when i wan't to run the following command in the scribus directory :
cmake ./

I have this result which show that there is errors, and scribus still doesn't install :
Code: [Select]
root@gvp-MacBookPro:/home/gvp/scribus14x# cmake ./
CMake Warning (dev) at CMakeLists.txt:744:
  Syntax Warning in cmake code at column 25

  Argument not separated from preceding token by whitespace.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- The CXX compiler identification is GNU 7.5.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Scribus 1.4.9.svn will be built to install into /usr/local
-- Machine: x86_64-linux-gnu, void pointer size: 8
-- Found target X86_64
-- Building for target x86_64-linux-gnu
CMake Deprecation Warning at CMakeLists.txt:293 (CMAKE_POLICY):
  The OLD behavior for policy CMP0005 will be removed from a future version
  of CMake.

  The cmake-policies(7) manual explains that the OLD behaviors of all
  policies are deprecated and that a policy should be set to OLD only under
  specific short-term circumstances.  Projects should be ported to the NEW
  behavior and not rely on setting a policy to OLD.


-- Using standard ApplicationDataDir. You can change it with -DAPPLICATION_DATA_DIR
CMake Error at /usr/share/cmake-3.13/Modules/FindQt4.cmake:1313 (message):
  Found unsuitable Qt version "5.9.5" from /usr/bin/qmake, this code requires
  Qt 4.x
Call Stack (most recent call first):
  CMakeLists.txt:669 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!
See also "/home/gvp/scribus14x/CMakeFiles/CMakeOutput.log".
See also "/home/gvp/scribus14x/CMakeFiles/CMakeError.log".

Any idea to get out from this ?
Before that i also try this process :
delete the folder named Scribus, and purge scribus completely, than i went into the Linux software manager, install Linux and than :
nothing appeared as mentioned.

I don't understand where all these problems are coming from whereas Scribus had previously worked wonderfully.
Thanks in advance for any track.
A.
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 16, 2020, 10:47:29 pm
hi archibaldix

there are a few things here...

the most important ones: you are following instructions for scribus 1.5 but got the code for scribus 1.4...

for 1.4 you need qt 4 which you will probably not get so easily on up to date linux distributions.

but you should probably compile scribus 1.5 anyway : - )

i also notice that you're compiling scribus as root. that's not really a good idea.

and running cmake in the main scribus directory: not so good either.

i have some compiling instructions that are now a bit older but should be good enough:

http://www.impagina.org/learn/development

good luck and do not hesitate to ask further questions!

ciao
a.l.e
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 17, 2020, 01:57:55 pm
Mmmh. Blocked again.
Wel i should first say thanks to the community for answers and to build such explaining pages like the one indicated by a.l.e
(...)
Ok indeed i was doing the install in the 1.4.8 version of Srcibus.
Now i tryed the 1.5 and not being in root,
But it seems there is a problem that stay in place
When i try to run the cmake command i got this erro message :
Code: [Select]
gvp@gvp-MacBookPro:~/scribus15/build$ cmake -DCMAKE_INSTALL_PREFIX:PATH=~/bin/scribus -DWANT_DEBUG=1 ..
-- CMake Version: 3.13.4
-- Shared Library Flags:
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Scribus 1.5.6.svn will be built and installed into /home/gvp/bin/scribus
-- Machine: x86_64-linux-gnu, void pointer size: 8
-- Found target X86_64
-- Building for target x86_64-linux-gnu
-- Using standard ApplicationDataDir. You can change it with -DAPPLICATION_DATA_DIR
-- Using standard ApplicationConfigDir. You can change it with -DAPPLICATION_CONFIG_DIR
-- Enabling C++11 compiler features
CMake Error at CMakeLists_Dependencies.cmake:8 (find_package):
  Could not find a configuration file for package "Qt5Core" that is
  compatible with requested version "5.11.0".

  The following configuration files were considered but not accepted:

    /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake, version: 5.9.5

Call Stack (most recent call first):
  CMakeLists.txt:380 (include)


-- Configuring incomplete, errors occurred!
See also "/home/gvp/scribus15/build/CMakeFiles/CMakeOutput.log".
gvp@gvp-MacBookPro:~/scribus15/build$

I delete and rebuild the Build directory few times but doesn't work. I also went to update the trunck-package as mentionned but same.

I will try again to find a solution. Any help welcome. Thank you so much.
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 17, 2020, 04:35:33 pm
that's simple and "in your face" : - )

as so often, errors are best read from the end and there it is: your qt is too old.
you need at least qt 5.11.

for ubuntu it should be pretty easy to add beineri's PPA...
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 17, 2020, 07:07:03 pm
Still difficult for me. Thanks anyway.

Well : sure now, i install QT version 15.4.0, means it' should works.
But it doesn't work when i try the cmake code.
I understand that maybe qmake don't recognize that i install an other version of QT or something like that.

The following code report :
Code: [Select]
gvp@gvp-MacBookPro:~$ qmake --version
QMake version 3.1
Using Qt version 5.9.5 in /usr/lib/x86_64-linux-gnu


So i tryed to change the QT version used, following this :
https://doc-snapshots.qt.io/qtcreator-4.0/creator-project-qmake.html
But doesn't work, qmake --version give me the same result.

I tryed also this :
https://unix.stackexchange.com/questions/116254/how-do-i-change-which-version-of-qt-is-used-for-qmake
but doesn't work.

How to make QT 15.4.0. operationnal ?
Still the Question. Thanks in advance for any tracks.
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 17, 2020, 10:48:33 pm
scribus does not use qmake but cmake...

if you cannot remove the other version of Qt, you need to get cmake to find your version of Qt.
from what i've found online, you should add the path to Qt to  CMAKE_PREFIX_PATH
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 18, 2020, 10:56:06 am
(...) I remove all the version of QT, then reinstall QT 15.4.0.
The code result is this one (a bit different than previous):
Code: [Select]
gvp@gvp-MacBookPro:~/scribus15/build$ cmake -DCMAKE_INSTALL_PREFIX:PATH=~/bin/scribus -DWANT_DEBUG=1 ..
-- CMake Version: 3.13.4
-- Shared Library Flags:
-- Scribus 1.5.6.svn will be built and installed into /home/gvp/bin/scribus
-- Machine: x86_64-linux-gnu, void pointer size: 8
-- Found target X86_64
-- Building for target x86_64-linux-gnu
-- Using standard ApplicationDataDir. You can change it with -DAPPLICATION_DATA_DIR
-- Using standard ApplicationConfigDir. You can change it with -DAPPLICATION_CONFIG_DIR
-- Enabling C++11 compiler features
CMake Error at CMakeLists_Dependencies.cmake:8 (find_package):
  By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt5Core", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5Core"
  (requested version 5.11.0) with any of the following names:

    Qt5CoreConfig.cmake
    qt5core-config.cmake

  Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
  "Qt5Core_DIR" to a directory containing one of the above files.  If
  "Qt5Core" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  CMakeLists.txt:380 (include)


-- Configuring incomplete, errors occurred!
Means as you said, that i need indeed to add something to CMAKE_PREFIX_PATH
This is where it gets complicated for me. I just figured out how to change this for a few hours, reading tons of pages (but probably not the good one). I can't do it.
CMAKE_PREFIX_PATH >> Is this a text file to edit? Do i have to edit something? Where can i find it & what should be the command lines ?

Great Gratitude in advance for any help,
A.
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 18, 2020, 11:53:56 am
(...)
I could find here a way to do something with the CMAKE_PREFIX_PATH :
https://askubuntu.com/questions/633826/default-installation-prefix-qt5-qt5-widgets-ubuntu

I follow the process by doing the explaining detail here
$ CMAKE_PREFIX_PATH="{Path of gcc_64 under recently installed qt folder, example: $HOME/qt5/5.7/gcc_64}"

Between the {} i try first to point the gcc_64 folder as described,
I started the cmake code again but same error like before.
Then Between the {} I try to point the /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/ folder as described in the error
Code: [Select]
gvp@gvp-MacBookPro:~/scribus15/build$ cmake -DCMAKE_INSTALL_PREFIX:PATH=~/bin/scribus -DWANT_DEBUG=1 ..
-- CMake Version: 3.13.4
-- Shared Library Flags:
-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Scribus 1.5.6.svn will be built and installed into /home/gvp/bin/scribus
-- Machine: x86_64-linux-gnu, void pointer size: 8
-- Found target X86_64
-- Building for target x86_64-linux-gnu
-- Using standard ApplicationDataDir. You can change it with -DAPPLICATION_DATA_DIR
-- Using standard ApplicationConfigDir. You can change it with -DAPPLICATION_CONFIG_DIR
-- Enabling C++11 compiler features
CMake Error at CMakeLists_Dependencies.cmake:8 (find_package):
  Could not find a configuration file for package "Qt5Core" that is
  compatible with requested version "5.11.0".

  The following configuration files were considered but not accepted:

    /usr/lib/x86_64-linux-gnu/cmake/Qt5Core/Qt5CoreConfig.cmake, version: 5.9.5

Call Stack (most recent call first):
  CMakeLists.txt:380 (include)

-- Configuring incomplete, errors occurred!

I also noticed that the error report a bug considering the version (5.9.5), only after installing this package ; sudo apt install qtbase5-dev
If i purge this package than the error is speaking about a file that is no founded (this one : qt5core-config.cmake)

Code: [Select]
gvp@gvp-MacBookPro:~/scribus15/build$ cmake -DCMAKE_INSTALL_PREFIX:PATH=~/bin/scribus -DWANT_DEBUG=1 ..
-- CMake Version: 3.13.4
-- Shared Library Flags:
-- Scribus 1.5.6.svn will be built and installed into /home/gvp/bin/scribus
-- Machine: x86_64-linux-gnu, void pointer size: 8
-- Found target X86_64
-- Building for target x86_64-linux-gnu
-- Using standard ApplicationDataDir. You can change it with -DAPPLICATION_DATA_DIR
-- Using standard ApplicationConfigDir. You can change it with -DAPPLICATION_CONFIG_DIR
-- Enabling C++11 compiler features
CMake Error at CMakeLists_Dependencies.cmake:8 (find_package):
  By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt5Core", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5Core"
  (requested version 5.11.0) with any of the following names:

    Qt5CoreConfig.cmake
    qt5core-config.cmake

  Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
  "Qt5Core_DIR" to a directory containing one of the above files.  If
  "Qt5Core" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  CMakeLists.txt:380 (include)


-- Configuring incomplete, errors occurred!

I'm lost...
Not easy not easy.
A.
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 18, 2020, 01:13:36 pm
just a short question that could speed up everything:

why are you compiling scribus?

ciao
a.l.e
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 18, 2020, 01:42:38 pm
Why I compile scribus ; I don't know myself, i followed the message from Dragonfly saying i need to go to this link :
https://wiki.scribus.net/canvas/Building_SVN_versions_with_CMake#Version_1.5.x

My goal is simply to use Linux as before updating my system, which version is used does not matter to me.
As stated at the beginning (and I just tried again & same result): when I install Scribus from the software manager ; the installation is successful, but then ; unable to launch the application. I click on the icon and there is nothing going on.

A.
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 18, 2020, 04:35:53 pm
sorry to tell you it only now but: you're on the wrong path.

you don't need to compile scribus. in the worst case, you should use the appimage.
in the best and most likely case, you should fix the state of your packages and install scribus 1.4 or 1.5 through the package manager.

i'm traveling right now, and since i have never used linux mint, it's hard for to me to make a real diagnose.

what is likely not to work: installing and uninstalling again and again the same version of scribus.

what you can do?

in you package manager you can check which version of scribus you have installed.
and which version of Qt4.

by pure chance, they are easy to compare:

- if you have scribus 1.4 you need Qt4
- if you have scribus 1.5 you need Qt5

if you have a mismatch you need to install the version of Qt that matches your scribus version.

with a 19.2 version, there are some chances that you can install both Qt4 and Qt5.
in a 20.x version the chances are big that Qt4 is not there anymore.

of course if mint 19.2 does not carry Qt4, you will need to upgrade to scribus 1.5 and install Qt 5.

hope that helps... without seeing your computer or installing mint there is not much more that i can do for you : - )

and if all this fails: just get the appimage... it's a bit slower, it uses more memory, but it (should) just works!
(you can take the appimage for  1.5.5 or the latest development 1.5.6 appimage).
i can provide the link if you don't find them (as soon as i'm not in a train anymore...)

ciao
a.l.e
Title: Re: Unable to start Scribus after an update
Post by: dragonfly on September 18, 2020, 05:02:06 pm
I suggested that link which gives lists of dependencies (since you started by listing ldd).
However a much easier route is to use Synaptic Package Manager (search scribus after opening GUI) to install the package of choice.
Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 18, 2020, 09:02:49 pm
OK.
Well.
I did this :
Check my version installed through the package manager, result : 1.4.8-ubuntu18.04-ppa
Than i install all things i could found related to QT4, means this :  sudo apt install qt4-default
Also these :
Code: [Select]
apt install libqt4-dbus libqt4-declarative libqt4-designer libqt4-dev libqt4-dev-bin libqt4-help libqt4-network libqt4-opengl libqt4-opengl-dev libqt4-qt3support libqt4-script libqt4-scripttools libqt4-sql   libqt4-sql-mysql libqt4-svg libqt4-test libqt4-xml libqt4-xmlpatterns libqtcore4 libqtdbus4 libqtgui4 qdbus qt-at-spi qt4-linguist-tools qt4-qmake qtcore4-l10nThis : apt-rdepends --build-depends --follow=DEPENDS qt4-qmake and this one : apt-rdepends --build-depends --follow=DEPENDS libqt4-dev

Couldn't open Scribus anyway.
So I decided to update my whole computer.
I did it and i'm now on Linux Mint 19.3.
I tryed again to start srcibus but doesn't work.
As i say "tryed to", it means, i can see in the Menu that Scribus is there like before. But clicking on it nothing appears.
I tryed to find a way to start it from the terminal but i found nothing.
I also deleted the Scribus15 folder that was from the compilation.
Finally completely purged scribus.

Of course I saw that I could use the APP image. I had a bug with version 1.5.3 so I took image 1.5.1. It works well with this one and i can open my files like before.
But why is it no longer possible to have Scribus installed stably as before? Are we definitely forgetting the previous system?
No difference on the horizon with this Appimage? I will not have a bug or other when i save file or exporting PDF ? (I use scribus all the time)

It is an honor for me to imagine that someone on a train on the planet is guiding me through my problems. Thank you very much for the attention. As far as I'm concerned, I'm at the center of Europe in a country called Belgium.
To be continued pending your feedback on the stability of the Appimage. And then I'll wait for version 1.5. appear in the software manager to reinstall it from there ?

A.

 
Title: Re: Unable to start Scribus after an update
Post by: a.l.e on September 19, 2020, 07:39:50 am
well, all feel to be at the center of europe : - )
except those who feel forgotten at its borders.

first, 1.4.8 is not compatible with 1.5.x (this means that if you had 1.5.x in the past, you won't be able to open your files with 1.4; of course 1.5.x can open files from 1.4.8)

if you use an appimage, you should use the latest one. 1.5.5. not 1.5.3 nor 1.5.1. if you have a bug that affects you, you should go for the latest 1.5.6svn and update it regularly.

also: you don't seem to be specially comfortable with the command line: you should probably install your software with a GUI tool...
this link https://community.linuxmint.com/tutorial/view/1525 suggests that linux mint has a "software manager". you might want to use it.
apt is very powerful but it also gives you more chances to screw up everything.

further one: why aren't you installing mint 20?
ok, it's not a good number, but trying to be behind it's mostly the source of hassle.

ok, the fact that gimp might not be available is a bit scary... https://en.wikipedia.org/wiki/Linux_Mint_version_history

finally, in order to start scribus from a terminal (and getting a clue of why it does not start) you simply type scribus and then return in a terminal.

there is one last information that could help sort out the issue: if you type "which scribus" in a terminal, what does it spit out?
Title: Re: Unable to start Scribus after an update
Post by: Nermander on September 19, 2020, 12:15:52 pm
As i say "tryed to", it means, i can see in the Menu that Scribus is there like before. But clicking on it nothing appears.

That menu item is kind of a shortcut created by an installer. So the shortcut may be pointing to something that no longer exists.

The best way to test if scribus is installed is to start it from the command line.

Title: Re: Unable to start Scribus after an update
Post by: Archibaldix on September 19, 2020, 01:49:49 pm
well, all feel to be at the center of europe : - )
except those who feel forgotten at its borders.
I Respect this sentence thank you.

All my files are with 1.4.x scribus
Ok thanks for the App image info , I'll pay attention.
Thanks for the link to the tutorial for command lines, will be very helpfull.
Indeed loose Gimp is an scary prospect...

Here the result of the command line :
Code: [Select]
gvp@gvp-MacBookPro:~$ scribus
scribus: symbol lookup error: scribus: undefined symbol: _ZN12QApplication10commitDataER15QSessionManager

Code: [Select]
gvp@gvp-MacBookPro:~$ which scribus
/usr/bin/scribus

Thanks Nermander, with all this reply it's getting slowly clearer.
(...)
A.