[Users] [Bug 4372] New: Crash after "Send later" without recipient and then "Close"
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Wed Aug 12 21:34:26 CEST 2020
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4372
Bug ID: 4372
Summary: Crash after "Send later" without recipient and then
"Close"
Product: Claws Mail
Version: 3.17.6
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: UI/Compose Window
Assignee: users at lists.claws-mail.org
Reporter: deweloper at wp.pl
claws-mail-3.17.6-1.fc32.x86_64 crashes after following steps:
1. Open a draft message with empty recipients by double-clicking it
2. Click "Send later"
3. An error shows up saying that the e-mail has no recipient
4. Click "Close"
Thread 1 "claws-mail" received signal SIGSEGV, Segmentation fault.
(gdb) bt
#0 0x00007ffff705d925 in __strlen_avx2 () at /lib64/libc.so.6
#1 0x00007ffff6f6960e in __vfprintf_internal () at /lib64/libc.so.6
#2 0x00007ffff6f7b68a in __vsnprintf_internal () at /lib64/libc.so.6
#3 0x00005555556a2d92 in alertpanel_error ()
#4 0x00005555556b7298 in compose_send_later_cb ()
#5 0x00005555556c6a4f in compose_toolbar_cb ()
#6 0x00007ffff72db742 in g_closure_invoke () at /lib64/libgobject-2.0.so.0
#7 0x00007ffff72ef604 in signal_emit_unlocked_R () at
/lib64/libgobject-2.0.so.0
#8 0x00007ffff72f83ae in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0
#9 0x00007ffff72f8fc9 in g_signal_emit_by_name () at
/lib64/libgobject-2.0.so.0
#10 0x00007ffff72db742 in g_closure_invoke () at /lib64/libgobject-2.0.so.0
#11 0x00007ffff72ef604 in signal_emit_unlocked_R () at
/lib64/libgobject-2.0.so.0
#12 0x00007ffff72f83ae in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0
#13 0x00007ffff72f89d3 in g_signal_emit () at /lib64/libgobject-2.0.so.0
#14 0x00007ffff7b8356e in gtk_real_button_released (button=0x555556c29bf0) at
gtkbutton.c:1712
#15 0x00007ffff72db742 in g_closure_invoke () at /lib64/libgobject-2.0.so.0
#16 0x00007ffff72ef749 in signal_emit_unlocked_R () at
/lib64/libgobject-2.0.so.0
#17 0x00007ffff72f83ae in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0
#18 0x00007ffff72f89d3 in g_signal_emit () at /lib64/libgobject-2.0.so.0
#19 0x00007ffff7b82153 in gtk_button_button_release (event=<optimized out>,
widget=0x555556c29bf0) at gtkbutton.c:1604
#20 gtk_button_button_release (widget=widget at entry=0x555556c29bf0,
event=<optimized out>) at gtkbutton.c:1596
#21 0x00007ffff7c3f19d in _gtk_marshal_BOOLEAN__BOXED
(closure=0x555555b341c0, return_value=0x7fffffffd380,
n_param_values=<optimized out>, param_values=0x7fffffffd3e0,
invocation_hint=<optimized out>, marshal_data=<optimized out>)
at gtkmarshalers.c:84
#22 0x00007ffff72db742 in g_closure_invoke () at /lib64/libgobject-2.0.so.0
#23 0x00007ffff72eed84 in signal_emit_unlocked_R () at
/lib64/libgobject-2.0.so.0
#24 0x00007ffff72f7a21 in g_signal_emit_valist () at /lib64/libgobject-2.0.so.0
#25 0x00007ffff72f89d3 in g_signal_emit () at /lib64/libgobject-2.0.so.0
#26 0x00007ffff7d745ed in gtk_widget_event_internal
(widget=widget at entry=0x555556c29bf0, event=event at entry=0x5555566ad4b0) at
gtkwidget.c:5017
#27 0x00007ffff7d748c9 in IA__gtk_widget_event
(widget=widget at entry=0x555556c29bf0, event=event at entry=0x5555566ad4b0) at
gtkwidget.c:4814
#28 0x00007ffff7c3cd6c in IA__gtk_propagate_event (widget=0x555556c29bf0,
event=0x5555566ad4b0) at gtkmain.c:2503
#29 0x00007ffff7c3d17b in IA__gtk_main_do_event (event=0x5555566ad4b0) at
gtkmain.c:1698
#30 IA__gtk_main_do_event (event=<optimized out>) at gtkmain.c:1503
#31 0x00007ffff7a87670 in gdk_event_dispatch (source=<optimized out>,
callback=<optimized out>, user_data=<optimized out>) at gdkevents-x11.c:2425
#32 0x00007ffff71f1570 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#33 0x00007ffff71f1900 in g_main_context_iterate.isra () at
/lib64/libglib-2.0.so.0
#34 0x00007ffff71f1bf3 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#35 0x00007ffff7c3c112 in IA__gtk_main () at gtkmain.c:1270
#36 0x0000555555686e3c in main ()
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list