"Segmentation fault" after pressing a button on a website
Hi, while testing search engines, I found that on this particular site https://paulina.toolforge.org/, when you press the button to submit your search, Dillo crashes with the following message on the terminal: "Violación de segmento". Here are the logs I get:
Nav_open_url: new url='https://paulina.toolforge.org/' Dns_server [0]: paulina.toolforge.org is 2a02:ec80:a000:1::2bc 185.15.56.88 Connecting to [2a02:ec80:a000:1::2bc]:443 paulina.toolforge.org: TLSv1.3, cipher TLS_AES_256_GCM_SHA384 0: ecdsa-with-SHA384 256-bit EC: /CN=toolforge.org 1: sha256 384-bit EC: /C=US/O=Let's Encrypt/CN=E8 root: /C=US/O=Internet Security Research Group/CN=ISRG Root X1 NumPendingStyleSheets=1 NumPendingStyleSheets=2 NumPendingStyleSheets=3 Dns_server [0]: tools-static.wmflabs.org is 2a02:ec80:a000:1::1d 185.15.56.49 tools-static.wmflabs.org: TLSv1.3, cipher TLS_AES_256_GCM_SHA384 0: ecdsa-with-SHA384 256-bit EC: /CN=wmcloud.org 1: sha256 384-bit EC: /C=US/O=Let's Encrypt/CN=E8 root: /C=US/O=Internet Security Research Group/CN=ISRG Root X1
a_Nav_repush <<<< Nav_open_url: new url='https://paulina.toolforge.org/' a_Nav_expect_done: repush! Violación de segmento
It happens on both Dillo branches "master" and "match-prefix-exactly" $ dillo -v Dillo Libraries: fltk/1.3.11 jpeg/2.1.5 png/1.6.48 webp/1.5.0 zlib/1.3.1 OpenSSL/3.5.4 Features: +GIF +JPEG +PNG +SVG +WEBP -BROTLI +XEMBED +TLS +IPV6 -CTL
Hi, Juan M Sevilla <jumase+dillo@disroot.org> wrote:
Hi, while testing search engines, I found that on this particular site https://paulina.toolforge.org/, when you press the button to submit your search, Dillo crashes with the following message on the terminal: "Violación de segmento".
I believe the problem is related to this known issue: https://bug.dillo-browser.org/506/ It is possible to work around it for now by putting something like this in your ~/.dillo/style.css file: select { display: inline !important; } Regards, Alex
Hi, 9 mar. 2026 11:50:34 a1ex@dismail.de:
I believe the problem is related to this known issue:
https://bug.dillo-browser.org/506/
It is possible to work around it for now by putting something like this in your ~/.dillo/style.css file:
select { display: inline !important; }
Oh, I see, thank you! I should've checked the bug tracker —it was quite late last night. I'll try that workaround meanwhile, thanks! Kind regards
participants (2)
-
a1ex＠dismail.de -
Juan M Sevilla