Description of problem: I was trying to move an account on the left pane (doesn't work), then it crashed. Version-Release number of selected component: claws-mail-3.10.1-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: claws-mail crash_function: folder_get_identifier executable: /usr/bin/claws-mail kernel: 3.15.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 folder_get_identifier at folder.c:1366 #1 folder_item_get_identifier at folder.c:1380 #2 notification_popup_msg at notification_popup.c:127 #3 notification_new_unnotified_do_msg at notification_core.c:449 #4 notification_new_unnotified_msgs at notification_core.c:431 #5 my_folder_item_update_hook at notification_plugin.c:179 #6 hooks_marshal at hooks.c:108 #7 g_hook_list_marshal at ghook.c:676 #8 hooks_invoke at hooks.c:126 #9 folder_item_update_func at folder.c:4542
Created attachment 936288 [details] File: backtrace
Created attachment 936289 [details] File: cgroup
Created attachment 936290 [details] File: core_backtrace
Created attachment 936291 [details] File: dso_list
Created attachment 936292 [details] File: environ
Created attachment 936293 [details] File: exploitable
Created attachment 936294 [details] File: limits
Created attachment 936295 [details] File: maps
Created attachment 936296 [details] File: open_fds
Created attachment 936297 [details] File: proc_pid_status
Created attachment 936298 [details] File: var_log_messages
Did you try to move an "account" (a mailbox) or a folder? Mailboxes are moved via the "File" menu, whereas folders may be moved within the left list. > #0 folder_get_identifier (folder=0x6f64202a21215055) at folder.c:1366 > type_str = <error reading variable type_str > (Cannot access memory at address 0x6f64202a21215055)> 0x6f64202a21215055 isn't a valid address here and looks much like (ASCII-)text fragments as a result of either heap corruption or an overflow of local buffers/variables. Earlier the backtrace refers to a notification popup, so perhaps there's a race condition between "moving something" and a notification of new messages. > #2 0x00007f537efaaa8e in notification_popup_msg > (msginfo=msginfo@entry=0x3d60e00) at notification_popup.c:127 > #3 0x00007f537efa9f94 in notification_new_unnotified_do_msg (msg=0x3d60e00) at notification_core.c:449 > #4 notification_new_unnotified_msgs (update_data=update_data@entry=0x7fffbfee1010) at notification_core.c:431
Yeah, I was trying to rearrange accounts and in the end I've googled there's the File→Change mailbox order option. I don't know whether me trying to move accounts around even had anything to do with the crash, it was simply the last thing I've tried just a few seconds prior.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.