Description of problem: Installed Scribus, launched and it crashed with Signal # 11. Then ran fron terminal, output: ~]$ scribus ReaderWriterTF::writeObject sizeof(TrkHeader)=1000 pathForIcon: Unable to load icon /usr/share/scribus/icons/1_5_1/lab.png: File not found pathForIcon: Unable to load icon /usr/share/scribus/icons/1_5_1/spot.png: File not found pathForIcon: Unable to load icon /usr/share/scribus/icons/1_5_1/register.png: File not found Scribus Crash ------------- Scribus crashes due to Signal #11 Calling Emergency Save Version-Release number of selected component (if applicable): 1.5.8-7 Additional information: Confirming these three .png files are not in /icons/1_5_1/ but they are in /icons/1_5_0/
Thank you for this unambiguous report. Assigning it globally as Scribus is committed by different packagers.
Summary: Scribus - crashing due to Signal # 11 => Scribus - crashing due to wrong icons directory: it is 1_5_0, it wants 1_5_1Assignee: bugsquad => pkg-bugs
The crash is not due to the icon message or path. There is something more involved regarding edwards machine. This message about the icon path is a known cosmetic issue which is common for all distributions which ships scribus (can easily be found by googling). Signal 11 SIGSEGV (segmentation violation) means that the application made an invalid memory reference and the Linux kernel killed it. You should do a gdb backtrace to get some informations about the root cause on your machine... Informations how to do a backtrace: https://wiki.mageia.org/en/Debugging_software_crashes Scribus starts fine on my cauldron machine even with the (only informative) message about the icon path... I tested this one two different plasma installations: - one installation is a mga8 to cauldron upgrade: scribus starts fine (with the icon message) - the other installation is the from latest cauldron netinstall image: scribus starts fine (with the icon message)
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
I have experience with coredumpctl. I'll see what it shows, if anything.
It is also easy to verify that it is not related to the icon path by simply (as root): cp /usr/share/scribus/icons/1_5_0/register.png /usr/share/scribus/icons/1_5_1/register.png cp /usr/share/scribus/icons/1_5_0/spot.png /usr/share/scribus/icons/1_5_1/spot.png cp /usr/share/scribus/icons/1_5_0/lab.png /usr/share/scribus/icons/1_5_1/lab.png
This is what appeared: ~]$ gdb /usr/share GNU gdb (GDB) 12.1-3.mga9 (Mageia release 9) Copyright (C) 2022 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... /usr/share: Is a directory. (gdb) file scribus Reading symbols from scribus... Reading symbols from /usr/lib/debug/usr/bin/scribus-1.5.8-7.mga9.x86_64.debug... (gdb) bt full No stack. scribus-1.5.8-7.mga9.x86_64.debug is over 237 MB in size. If it will not run on this machine, then I probably should uninstall it.
You need to run: gdb /usr/bin/scribus
(In reply to sturmvogel from comment #6) > You need to run: > > gdb /usr/bin/scribus I did. Scribus was *not* in /usr/bin/. I found it in /usr/share/. I've already uninstalled it anyway. It was installed in one of my Cauldron VirtualBoxes on different hardware and it runs fine.
Your installation is totally broken then as /usr/share/scribus is only a directory and doesn't contain any executable files. This can also be found by looking into the file list: http://sophie.zarb.org/rpms/fb1c56c2e69a80c056d2bd00ed0f43db/files (In reply to Edward from comment #7) > It was installed in one of my Cauldron > VirtualBoxes on different hardware and it runs fine. Based on all of the above... Closing as INVALID.
Resolution: (none) => INVALIDStatus: UNCONFIRMED => RESOLVED