topic title: [Solved] Dillo won't start: Segmentation fault
Posts: 64
reverseDog
Joined: 13 Jul 2016
#1
Hi everybody,

I'm not a frequent user of Dillo, but when today I wanted to look up something in the antiX FAQ I found Dillo wouldn't start anymore. Trying to run Dillo from the terminal I get:

Code: Select all

$ dillo
Domain: Default accept.
dillo_dns_init: Here we go! (threaded)
Disabling cookies.
Segmentation fault
$
dsmeg returned:

Code: Select all

$ dmesg | grep dillo
[  210.961664] dillo[3291]: segfault at 0 ip b7167db1 sp bfc5ba7c error 4 in libc-2.19.so[b70ee000+16e000]
$
Strange enough I can still run Dillo as root without any problems.

Debugging Dillo with gdb gives me an output I'm not expert enough to understand:

Code: Select all

(gdb) run
Starting program: /usr/bin/dillo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library"/lib/i386-linux-gnu/libthread_db.so.1".
Domain: Default accept.
dillo_dns_init: Here we go! (threaded)
Disabling cookies.

Program received signal SIGSEGV, Segmentation fault.
0xb7a09db1 in strlen () from /lib/i386-linux-gnu/libc.so.6
(gdb) backtrace
#0  0xb7a09db1 in strlen () from /lib/i386-linux-gnu/libc.so.6
#1  0xb7e8dd19 in Fl::set_fonts(char const*) ()
   from /usr/lib/i386-linux-gnu/libfltk.so.1.3
#2  0x0809f86e in ?? ()
#3  0x0809fbd5 in ?? ()
#4  0x0805050f in ?? ()
#5  0x0804f4ec in ?? ()
#6  0xb79a9723 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6
#7  0x08050165 in ?? ()
(gdb)
Well, this really isn't tragic, since I can get along pretty well without Dillo, but maybe someone does have an idea how to make it run again.
Last edited by reverseDog on 20 Jan 2017, 00:51, edited 1 time in total.
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#2
No problems here. I launch dillo surprisingly often. FWIW, just now I successfully tested:
launching via gexec (and gksu)
launching from roxterm (and sudo)
launching from lxterminal (and sudo)

I would check whether the problem persists across logout/login (and shutdown/reboot).
If it does, I would uninstall (or purge, your choice) then reinstall dillo package and retry.
#1 0xb7e8dd19 in Fl::set_fonts(char const*) ()
another troubleshooting idea:
run lxappearance and select a different font.
Who knows, maybe the segfault is due to dillo choking with one particular fontfile?
Posts: 64
reverseDog
Joined: 13 Jul 2016
#3
skidoo wrote:
#1 0xb7e8dd19 in Fl::set_fonts(char const*) ()
another troubleshooting idea:
run lxappearance and select a different font.
Who knows, maybe the segfault is due to dillo choking with one particular fontfile?
Thanks a lot, skidoo, that hint of yours finally put me on the right track – even though selecting a different font in LXAppearance had no effect (I didn't really expect it would, because LXAppearance only sets GTK fonts, whereas Dillo is based on FLTK). But your calling my attention to fonts made me remember that I recently had installed some new fonts in ~/.local/share/fonts. After removing them, Dillo surprisingly lets itself be launched again!
Posts: 1,445
skidoo
Joined: 09 Feb 2012
#4
good ol' dillo, don't setup basecamp without it __{{emoticon}}__


If you can recall ( or, check /var/log/dpkg.log ) which fontsets were problematic, mentioning them here will be helpful future searchers.
Posts: 64
reverseDog
Joined: 13 Jul 2016
#5
skidoo wrote:If you can recall ( or, check /var/log/dpkg.log ) which fontsets were problematic, mentioning them here will be helpful future searchers.
First I had removed the whole bunch of eleven fonts that resided in my ~/.local/share/fonts. Now I have one by one copied them back and found: it's Consolas Dillo disagrees with. Well, I can very well live without that Microsoft font and don't hold it against ol' Dillo. I'm just glad Dillo graciously accepts Ubuntu (which I use as my default font via LXAppearance) and
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.latofonts.com/lato-free-fonts/"
linktext was:"Lato"
====================================
(simply one of my favourites). __{{emoticon}}__

Still the whole issue remains somewhat mysterious, since I never had asked Dillo to use any other fontset besides the preset DejaVu. __{{emoticon}}__
Posts: 119
wildstar84
Joined: 31 May 2014
#6
You might want to file a bug against the Dillo project to alert them of your findings.
Posts: 64
reverseDog
Joined: 13 Jul 2016
#7
Before filing a bug I felt like trying once more to establish a friendship between Dillo and Consolas. And finally I did succeed.

Originally I simply had copied some Microsoft font files from an old (Lubuntu) backup to my antiX system. That apparently did work out – except for the Consolas fontfamily which maybe was/got broken (even though I could use it with Leafpad or LibreOffice). Anyway, today I installed Microsoft’s ClearType fonts anew, following this instruction:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.pcworld.com/article/2863497/how-to-install-microsoft-fonts-in-linux-office-suites.html"
linktext was:"http://www.pcworld.com/article/2863497/ ... uites.html"
====================================
. And now Dillo and Consolas seem to be getting along just fine.

So I guess there is no need for a bug report. __{{emoticon}}__