abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 14314 bytes cmdline: /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=22 component: gnote Attached file: coredump, 11833344 bytes crash_function: boost::throw_exception<boost::filesystem2::basic_filesystem_error<boost::filesystem2::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem2::path_traits> > >(boost::filesystem2::basic_filesystem_error<boost::filesystem2::basic_path<std::basic_string<char, std::char_traits<char>, std::allocator<char> >, boost::filesystem2::path_traits> > const&) executable: /usr/bin/gnote kernel: 2.6.35.12-90.fc14.i686 package: gnote-0.7.3-4.fc14 rating: 4 reason: Process /usr/bin/gnote was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) How to reproduce: init level 5, yum update running time: 1304464454 uid: 500
Created attachment 496667 [details] File: backtrace
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. activated evolution for the first time 2. attempted to send an email via gmail POP 3. evolution, gnote and dconf-service all crashed The mail is still in the evolution outbox. Comment ----- This is a new FC14 installation.
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.initial login after boot init level 5
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- startup gnote death
Package: gnote-0.7.2-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.go to system -> administration -> users and groups 2.change current user name and home folder 3.log out and login back
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- First login after boot. Comment ----- login
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- boot to runlevel 5, login. Abrt
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- startup to init 5, login, crash
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.no clue 2. 3.
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. no clue 2. 3.
Package: gnote-0.7.3-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- At startup to init 5, login boom.
*** Bug 652101 has been marked as a duplicate of this bug. ***
*** Bug 655272 has been marked as a duplicate of this bug. ***
*** Bug 650552 has been marked as a duplicate of this bug. ***
*** Bug 668321 has been marked as a duplicate of this bug. ***
*** Bug 663511 has been marked as a duplicate of this bug. ***
*** Bug 692850 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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