| Summary: | [abrt] claws-mail-3.7.9-5.fc14: mimeview_start_drag: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pierre Ossman <ossman> | ||||
| Component: | claws-mail | Assignee: | Andreas Bierfert <andreas.bierfert> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 14 | CC: | andreas.bierfert, bugs.michael, tomspur | ||||
| Target Milestone: | --- | Keywords: | Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2529 | ||||||
| Whiteboard: | abrt_hash:fa3fdbee2cc7e30c9e5fa1186db0d41f020747fe | ||||||
| Fixed In Version: | claws-mail-plugins-3.7.10-12.fc16 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-26 19:17:36 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Pierre Ossman
2011-10-24 10:29:40 UTC
Created attachment 529776 [details]
File: backtrace
> Doesn't seem to reproduce just by following those steps though. Perhaps you could try harder to come up with a test-case? > 2. Expand the mail structure arrow (on the right) > 3. Delete the mail So far so good. I don't understand the next step: > 4. Collapse the mail structure again If you've deleted a message in step 3, in the next step you would work on a different message. >>> crash_function: mimeview_start_drag > #0 mimeview_start_drag (widget=0x1a12700 [GtkSCTree], button=1, > event=0x51f6910, mimeview=0x1c0fde0) at mimeview.c:1290 > context = <value optimized out> > partinfo = 0x0 This looks like you used drag'n'drop on any part in the expanded MIME view list. | 1289 partinfo = mimeview_get_selected_part(mimeview); | 1290 if (partinfo->disposition == DISPOSITIONTYPE_INLINE) return; The partinfo ptr for a selected part of the message was NULL here. One would need to find out when that could happen and if a damaged message could cause it. (In reply to comment #2) > > Doesn't seem to reproduce just by following those steps though. > > Perhaps you could try harder to come up with a test-case? > I'll give it another go, but claws is generally very stable so I'm not sure what I did to set it up for this crash. > > > 2. Expand the mail structure arrow (on the right) > > 3. Delete the mail > > So far so good. I don't understand the next step: > > > 4. Collapse the mail structure again > > If you've deleted a message in step 3, in the next step you would work on a > different message. > It works on a "blank" message at this point. > >>> crash_function: mimeview_start_drag > > > #0 mimeview_start_drag (widget=0x1a12700 [GtkSCTree], button=1, > > event=0x51f6910, mimeview=0x1c0fde0) at mimeview.c:1290 > > context = <value optimized out> > > partinfo = 0x0 > > This looks like you used drag'n'drop on any part in the expanded MIME view > list. > > | 1289 partinfo = mimeview_get_selected_part(mimeview); > | 1290 if (partinfo->disposition == DISPOSITIONTYPE_INLINE) return; > > The partinfo ptr for a selected part of the message was NULL here. One would > need to find out when that could happen and if a damaged message could cause > it. Hmm.. I opened the MIME view to do DnD, but that was a few messages before the crash. Could be related though. Ah! Found a way! 1. Select a mail 2. Open MIME view 3. Drag something out of it (to nautilus in my case) 4. Delete the mail 5. Try to drag something out of the blank MIME view Thank you very much! That's an odd scenario, but reproducible with Claws Mail 3.7.10, too: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2529 Upstream's fix is a simple NULL ptr check: http://www.colino.net/claws-mail/getpatchset.php?ver=3.7.10cvs47 Fix committed to Rawhide git. claws-mail-3.7.10-7.fc16,claws-mail-plugins-3.7.10-10.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/claws-mail-3.7.10-7.fc16,claws-mail-plugins-3.7.10-10.fc16 Package claws-mail-3.7.10-7.fc16, claws-mail-plugins-3.7.10-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing claws-mail-3.7.10-7.fc16 claws-mail-plugins-3.7.10-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-17063/claws-mail-3.7.10-7.fc16,claws-mail-plugins-3.7.10-10.fc16 then log in and leave karma (feedback). Package claws-mail-plugins-3.7.10-12.fc16, claws-mail-3.7.10-7.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing claws-mail-plugins-3.7.10-12.fc16 claws-mail-3.7.10-7.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-17063/claws-mail-3.7.10-7.fc16,claws-mail-plugins-3.7.10-12.fc16 then log in and leave karma (feedback). claws-mail-plugins-3.7.10-12.fc16, claws-mail-3.7.10-7.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |