Bug 843463 - Segfault after label attempted deletion
Segfault after label attempted deletion
Product: Fedora
Classification: Fedora
Component: evolution (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthew Barnes
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-07-26 07:52 EDT by Petr Schindler
Modified: 2012-07-27 02:08 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-07-27 02:08:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 680682 None None None 2012-07-27 02:08:38 EDT

  None (edit)
Description Petr Schindler 2012-07-26 07:52:28 EDT
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):

How reproducible:

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:

Expected results:
Label should be deleted

Additional info:
Comment 1 Milan Crha 2012-07-27 02:08:38 EDT
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.