After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 661900 - claws-mail-3.7.10-5.fc16: closure_invoke_notifiers: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
claws-mail-3.7.10-5.fc16: closure_invoke_notifiers: Process /usr/bin/claws-ma...
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
2.24.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2011-10-16 11:52 UTC by Michael Schwendt
Modified: 2018-02-10 03:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Schwendt 2011-10-16 11:52:34 UTC
Backtrace: https://bugzilla.redhat.com/attachment.cgi?id=528074

Claws Mail devs think this looks like a GTK bug (or glib2 where the actual crash occurs). Since it is 100% reproducible (also for me) currently with F-15 and F-16, I'm available to collect more data if necessary.

Affected, Fedora 15 and 16 (both x86_64):

  gtk2-2.24.4-2.fc15.x86_64
  glib2-2.28.8-1.fc15.x86_64
  claws-mail-3.7.9-5.fc15.x86_64

  gtk2-2.24.6-1.fc16.x86_64
  glib2-2.30.0-2.fc16.x86_64
  claws-mail-3.7.10-5.fc16.x86_64

Not affected, Fedora 14 (i686), same Claws Mail as F-15:

  gtk2-2.22.0-2.fc14.i686
  glib2-2.26.0-2.fc14.i686
  claws-mail-3.7.9-5.fc14.i686

[...]

How to reproduce in Claws Mail:
1. tag a message (e.g. via message list context-menu)
2. select the tagged message
3. open menu "Configuration > Tags"
4. delete the tag
 -> crash  

Also reproducible immediately after starting Claws Mail and without selecting a
message:
1. open menu "Configuration > Tags"
2. add a tag "test123"
3. delete tag "test123"
 -> crash
Comment 1 Matthias Clasen 2018-02-10 03:27:54 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.