Package: davmail Version: 4.8.0.2479-3 Severity: minor Tags: confirmed workaround
This bugreport is about a known bug. Purpose of this B.R. is document two workarounds: starting as SWT_GTK3=0 davmail having in the properties file davmail.server=true Below text from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879146#39 On Wed, Nov 22, 2017 at 06:56:10PM +0100, Alexandre Rossi wrote: > >> FYI, I would be happy to move on with this but I'm stuck with the > >> program segfaulting when used with the proposed patch. It works > >> correctly if launched like this : > >> SWT_GTK3=0 davmail > >> > >> I'm still investigating as to why. > >> > >> Alex > >> > >> ---- > >> (SWT:24928): GLib-GObject-WARNING **: cannot register existing type > >> 'GdkDisplayManager' > >> (SWT:24928): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' > >> failed > >> (SWT:24928): GLib-GObject-CRITICAL **: g_object_new_with_properties: > >> assertion 'G_TYPE_IS_OBJECT (object_type)' failed > >> (SWT:24928): GLib-GObject-WARNING **: invalid (NULL) pointer instance > >> (SWT:24928): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion > >> 'G_TYPE_CHECK_INSTANCE (instance)' failed > > > > > > Because I expect that those SWT messages wouldn't happen with > > > > davmail.server=true > > > > in davmail.properties, I'm about to upload 4.8.0.2479-3 > > > > Main reason is preventing davmail being removed from testing. > > Okay now users of the GUI version must set the envvar for davmail not > to crash. I'll search for a fix. Groeten Geert Stappers -- Leven en laten leven
