Thread: core dump
View Single Post
Old 11-09-2017, 07:58 AM   #5
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,715
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Doitsu View Post
My home-built Sigil version runs fine on my Arch Linux machine.
I think Roger installed the community version (pacman -S sigil).

Quote:
Originally Posted by Doitsu View Post
I also got:

Code:
Warning: libpng warning: iCCP: known incorrect sRGB profile
but I didn't get:

Code:
Debug: using qt5ct plugin
Debug: D-Bus system tray: no
Debug: D-Bus global menu: no
@DiapDealer: Doesn't the Debug: prefix mean that the Arch Linux Sigil packager (incorrectly) used the command line parameter for debug builds?
I honestly don't know. I get those debug messages on my custom built Sigil, as well (and some other Qt apps). They're coming from the system-supplied Qt5 and its plugin.

As far as the original error message goes, I have experienced those kinds of segfaults when config files could not be read (be it from permissions problems or non-existence).
DiapDealer is online now   Reply With Quote