Bug 843463 - Segfault after label attempted deletion
Summary: Segfault after label attempted deletion
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-07-26 11:52 UTC by Petr Schindler
Modified: 2012-07-27 06:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-27 06:08:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 680682 0 None None None 2012-07-27 06:08:38 UTC

Description Petr Schindler 2012-07-26 11:52:28 UTC
Description of problem:
Evotution falls down when I try to delete my custom mail label. The label isn't deleted then. I have still some mails labeled with this label.

I can see this in /var/log/messages:
kernel: [78006.431506] evolution[27949]: segfault at 5 ip 0000003b28031275 sp 00007fffea30b780 error 4 in libgobject-2.0.so.0.3200.4[3b28000000+4b000]

When I run evolution from terminal I get this:
(evolution:28781): GLib-GObject-WARNING **: invalid uninstantiatable type `<unknown>' in cast to `EMailLabelListStore'
Segmentation fault

Version-Release number of selected component (if applicable):
evolution-3.4.3-2.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Go to Edit->Preferences
2. In Mail Preferences choose Labels tab
3. Choose some of your custom label (I have to create it if you have none)
4. Click on 'Remove'
  
Actual results:
Segfault

Expected results:
Label should be deleted

Additional info:

Comment 1 Milan Crha 2012-07-27 06:08:38 UTC
Thanks for a bug report. I can reproduce it too, even on the latest development version. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=680682


Note You need to log in before you can comment on or make changes to this bug.