Description of problem: Attempting to post a multipart file to usenet. System crashed twice while attempting. Working through stunnel. Version-Release number of selected component: pan-0.139-4.fc19 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/pan crash_function: _M_dispose executable: /usr/bin/pan kernel: 3.14.8-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (10 frames) #5 _M_dispose at /usr/include/c++/4.8.0/bits/basic_string.h:249 #6 ~basic_string at /usr/include/c++/4.8.0/bits/basic_string.h:539 #7 pan::TaskUpload::prepend_headers at task-upload.cc:205 #8 pan::TaskUpload::use_nntp at task-upload.cc:255 #9 pan::Task::give_nntp at task.cc:44 #10 pan::Queue::check_in at queue.cc:753 #11 pan::Task::check_in at task.cc:59 #12 pan::TaskUpload::on_nntp_done at task-upload.cc:371 #13 pan::NNTP::fire_done_func at nntp.cc:65 #14 pan::NNTP::on_socket_response at nntp.cc:246
Created attachment 918019 [details] File: backtrace
Created attachment 918020 [details] File: cgroup
Created attachment 918021 [details] File: core_backtrace
Created attachment 918022 [details] File: dso_list
Created attachment 918023 [details] File: environ
Created attachment 918024 [details] File: limits
Created attachment 918025 [details] File: maps
Created attachment 918026 [details] File: open_fds
Created attachment 918027 [details] File: proc_pid_status
Created attachment 918028 [details] File: var_log_messages
Even after reconfiguring to not use stunnel, Pan would crash while attempting to post multipart articles to usenet. It would post some articles and then crash. If I selected 1 binary article, then it would post. Problem is when you are posting over 100 files one at a time, it is a major headache. Binary file size was 15M per rar file. I was limiting the upload to 4 threads and it may be threads causing the issue. When posting a single article, there was only one thread. Using a different program, it worked as expected with no issues.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.