Hide Forgot
abrt version: 1.1.17 architecture: i686 Attached file: backtrace, 31312 bytes cmdline: /usr/bin/claws-mail component: claws-mail Attached file: coredump, 16789504 bytes crash_function: IA__gtk_tree_model_get_valist executable: /usr/bin/claws-mail kernel: 2.6.35.11-83.fc14.i686 package: claws-mail-3.7.8-6.fc14 rating: 4 reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) How to reproduce: Clicked on 'define' when I was creating a new message rule time: 1299571691 uid: 500
Created attachment 482848 [details] File: backtrace
Package: claws-mail-3.7.8-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Define new filter rule. Reproduce... Select email, Tools menu, Create filter rule/ By subject Click Define for condition. Crash.
The important question you haven't answered is: Does it crash for you always? With the steps you've provided in comment 2, I cannot reproduce it. Can you reproduce with a fresh user account? The backtrace ends several steps into GTK+ (gtk2) and isn't directly within Claws Mail code.
Package: claws-mail-3.7.8-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Always happens. To reproduce... Tools menu / Create filter rule / Automatically Click 'Define...' for Condition Program then quits. Comment ----- Done yum update Reinstalled claws-mail Tried turning off Plugins.
Package: claws-mail-3.7.8-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Reproduce... Tools menu / Create filter rule / Automatically (or any other option here) Click 'Define...' for Condition Program quits. Comment ----- This always happens. Just started using Claws Mail. Created a new user account as suggested. Rebooted computer. Went through the Claws Mail setup once logged in as new user. Tried to reproduce and the program quits same as before.
Is there anything else that might be special about your setup of Fedora or Claws Mail? Do you use it with a US English locale or a different language? ( /etc/sysconfig/i18n ) Searching Fedora bugzilla for 'IA__gtk_tree_model_get_valist' gives the following list of crashes in other apps: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&short_desc=IA__gtk_tree_model_get_valist&bug_status=NEW&bug_status=ASSIGNED&short_desc_type=allwordssubstr&classification=Fedora
(In reply to comment #6) Help/About : System Information GTK+ 2.22.0 / GLib 2.26.0 Locale: en_GB.UTF-8 (charset: UTF-8) Operating System: Linux 2.6.35.11-83.fc14.i686 (i686) /etc/sysconfig/i18n : LANG="en_GB.UTF-8" SYSFONT="latarcyrheb-sun16"
Package: claws-mail-3.7.8-6.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open Claws mail 2. Go to tools >> create filter rule >> by subject 3. edit rule 4. click define 5. Crash
Is it reproducible after installing this scratch-build? http://koji.fedoraproject.org/koji/taskinfo?taskID=2922871
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