Red Hat Bugzilla – Full Text Bug Listing
|Summary:||evolution crash after "Backup Settings"|
|Product:||[Fedora] Fedora||Reporter:||chris snow <cs>|
|Component:||evolution||Assignee:||Matthew Barnes <mbarnes>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||9||CC:||mcrha, mike, mlists|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2009-07-14 11:59:57 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description chris snow 2008-04-15 12:04:11 EDT
Description of problem: After running Backup Settings, Evolution crashes - see screenshot. Version-Release number of selected component (if applicable): [snowch@ac ~]$ rpm -qa | grep evolution evolution-data-server-devel-2.22.1-1.fc9.i386 evolution-sharp-0.16.0-1.fc9.i386 beagle-evolution-0.3.5-2.fc9.i386 evolution-data-server-doc-2.22.1-1.fc9.i386 evolution-spamassassin-2.22.1-1.fc9.i386 evolution-data-server-2.22.1-1.fc9.i386 evolution-webcal-2.21.92-1.fc9.i386 evolution-2.22.1-1.fc9.i386 How reproducible: Steps to Reproduce: 1. In evolution: File > Backup Settings 2. Select location, click save 3. "Are you sure you want to close evolution?" - click Yes (tick restart option - although failure still happens if not ticked) 4. Error as per screen shot.
Comment 1 chris snow 2008-04-15 12:04:11 EDT
Created attachment 302486 [details] Evolution crash detection
Comment 2 Milan Crha 2008-04-15 12:55:49 EDT
If I get it right, there was no bug buddy or something similar, you just closed Evolution through that question and next start it showed this message, right? The message itself is a new feature to detect crashes and eventually allow user to disable preview panes, because most of crashers was caused by mails in preview. This seems like code missed one place to unset the flag. If that's the case, of course.
Comment 3 chris snow 2008-04-15 13:23:48 EDT
Yes, you are correct - no bug buddy, just the screen shot that I attached.
Comment 4 Mike Chambers 2009-03-07 09:30:59 EST
Does this problem still persist? Have you upgraded evolution and/or to Fedora 10? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Comment 5 Matěj Cepl 2009-05-18 07:48:05 EDT
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 6 Bug Zapper 2009-06-09 20:12:08 EDT
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 7 Bug Zapper 2009-07-14 11:59:57 EDT
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.