Hide Forgot
Description of problem: unknown Version-Release number of selected component: ekiga-4.0.1-6.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 3 cmdline: ekiga crash_function: (anonymous namespace)::__freelist::~__freelist executable: /usr/bin/ekiga kernel: 3.11.10-301.fc20.x86_64 runlevel: 3 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #2 (anonymous namespace)::__freelist::~__freelist at ../../../../../libstdc++-v3/src/c++98/mt_allocator.cc:50 #3 __cxa_finalize at cxa_finalize.c:56 #4 __do_global_dtors_aux at /lib64/libstdc++.so.6 #5 ?? #6 _dl_fini at dl-fini.c:252
Created attachment 838437 [details] File: backtrace
Created attachment 838438 [details] File: cgroup
Created attachment 838439 [details] File: core_backtrace
Created attachment 838440 [details] File: dso_list
Created attachment 838441 [details] File: environ
Created attachment 838442 [details] File: exploitable
Created attachment 838443 [details] File: limits
Created attachment 838444 [details] File: maps
Created attachment 838445 [details] File: open_fds
Created attachment 838446 [details] File: proc_pid_status
Created attachment 838447 [details] File: var_log_messages
Christian, were you quitting ekiga when this crash appeared? Is it reproducible 100% or not?
No, it's not reproducible so far. And I don't know if I was quiting ekiga when the crash appeared, but I don't think I was.
Another user experienced a similar problem: How to reproduce -- just use it often enough and it will crash sometimes with no obvious reason. reporter: libreport-2.1.12 backtrace_rating: 3 cmdline: ekiga crash_function: (anonymous namespace)::__freelist::~__freelist executable: /usr/bin/ekiga kernel: 3.12.9-301.fc20.x86_64 package: ekiga-4.0.1-6.fc20 reason: ekiga killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Hum, difficult to investigate, somehow a memory corruption somewhere in the program... I suggest waiting until the next major ekiga release (or its preliminary releases) will appear, hopefully it has been fixed during this rich development cycle.
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.