I'm running Slackware 14.1 (x86_64) with KDE and using the Claws 3.11.1 build from slackbuilds.org Claws starts up on and will run OK unless a message contains an https link. Initially I didn't have glib-networking installed and Claws complained about missing TLS/SSL support and I should install glib-networking. I installed this and now claws crashes whenever it attempts to open a message with https links in it. I've duplicated this on two similar machines (both slackware) I caught the following output from gdb: ============================================================================== [New Thread 0x7fffdfaa2700 (LWP 23209)] [New Thread 0x7fff8bffd700 (LWP 23210)] [New Thread 0x7fff8aeda700 (LWP 23211)] (claws-mail:23184): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy' is not installed Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007fffec69723d in g_logv () from /usr/lib64/../lib64/libglib-2.0.so.0 ==============================================================================
I don't know what it was that complained about glib-networking, but it wasn't Claws Mail, since it does not even know what glib-networking is. If Claws Mail complained about missing TLS support, it was because of missing Gnutls (or its -devel package for Claws Mail compilation, if Slackware has such packages).
Can you run claws-mail in a terminal in gdb with --debug switch, and get a full backtrace? See http://www.claws-mail.org/faq/index.php/Debugging_Claws in case you need more guidance.
That doesn't sound possible at all. A message is just a bunch of text. Just perhaps you are talking about an html message part, which you are opening by default, and you use the fancy plugin. This plugin depends on libsoup, which has glib-networking as a dependency. If this is the case, try unloading the fancy plugin and see if it helps. Anyway, it's a bug in a dependency (of a dependency) and not in Claws. You say you've duplicated on 2 additional machines. I assume that these all have the same setup.
Created attachment 1503 [details] Screenshot of Claws message view showing problem. Attached is the screenshot showing the error message I see in Claws when I click an https link. This is where it shows the glib-networking message. I accept that this could be due to the Fancy plugin, however if I install the glib-networking package, Claws will not even start correctly (or it starts then crashes immediately) if the message contains an https URL. Fancy seems to work fine and displays HTML messages so long as no https URLs are included.
(In reply to comment #2) > Can you run claws-mail in a terminal in gdb with --debug switch, and get a > full backtrace? See http://www.claws-mail.org/faq/index.php/Debugging_Claws > in case you need more guidance. I'll try gdb again later with the --debug switch and post results.
OK, here is the relevant output from gdb run --debug =============================================================== imap.c:1518:message 85934 has been already fully cached. message/rfc822 (offset:0 length:6051 encoding: 6) multipart/mixed (offset:1465 length:4586 encoding: 6) multipart/alternative (offset:1609 length:4400 encoding: 6) text/plain (offset:1743 length:1212 encoding: 4) text/html (offset:3089 length:2878 encoding: 4) mimeview.c:842:text/html fancy_viewer.c:863:fancy_viewer_create [New Thread 0x7fffdfaa2700 (LWP 3591)] [New Thread 0x7fff8bffd700 (LWP 3592)] fancy_viewer.c:81:fancy_get_widget: 0x1701ca0 fancy_viewer.c:81:fancy_get_widget: 0x1701ca0 summaryview.c:3650:TIMING summary_display_msg_full : 0s358ms fancy_viewer.c:231:filename: /home/jammer/.claws-mail/mimetmp/000000f0.mimetmp.html fancy_viewer.c:247:using utf-8 charset fancy_viewer.c:250:zoom_level: 100 fancy_viewer.c:383:navigation requested to file:///home/jammer/.claws-mail/mimetmp/000000f0.mimetmp.html [New Thread 0x7fff8acd8700 (LWP 3593)] fancy_viewer.c:442:Starting request of 61 file:///home/jammer/.claws-mail/mimetmp/000000f0.mimetmp.html (claws-mail:3507): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy' is not installed Program received signal SIGTRAP, Trace/breakpoint trap. 0x00007fffec69723d in g_logv () from /usr/lib64/../lib64/libglib-2.0.so.0 (gdb)
So to progress this issue, do I need to start digging around inside fancy_viewer.c or do you think the issue is within the libsoup/glib-networking code ? If so, is it likely to be a library version issue with either libsoup or glib-networking ?
Created attachment 1504 [details] Backtrace following crash gdb backtrace from run --debug and thread apply all bt
From what I can see, the crash happens in libsoup, called from deep within webkit-gtk. Maybe try by getting the debug symbols for all the involved libraries, and good luck in digging.