Description of problem: I execute vidalia from a script. I change the $HOME var to something else. Vidalia keeps its lock files etc in the new $HOME. Thats all that is unique to its invocation. It works perfectly except for this crash. Version-Release number of selected component: vidalia-0.2.20-3.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: vidalia crash_function: QString::free executable: /usr/bin/vidalia kernel: 3.13.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 QString::free at tools/qstring.cpp:1235 #6 ~QString at /usr/include/QtCore/qstring.h:880 #7 node_destruct at /usr/include/QtCore/qlist.h:433 #8 QList<QString>::free at /usr/include/QtCore/qlist.h:757 #9 QList<QString>::~QList at /usr/include/QtCore/qlist.h:732 #10 ~QStringList at /usr/include/QtCore/qstringlist.h:66 #11 TorControl::getConf at /usr/src/debug/vidalia-0.2.20/src/torcontrol/TorControl.cpp:824 #12 TorControl::useMicrodescriptors at /usr/src/debug/vidalia-0.2.20/src/torcontrol/TorControl.cpp:951 #13 TorControl::getRouterDescriptor at /usr/src/debug/vidalia-0.2.20/src/torcontrol/TorControl.cpp:977 #14 NetViewer::loadNetworkStatus at /usr/src/debug/vidalia-0.2.20/src/vidalia/network/NetViewer.cpp:322
Created attachment 869651 [details] File: backtrace
Created attachment 869652 [details] File: cgroup
Created attachment 869653 [details] File: core_backtrace
Created attachment 869654 [details] File: dso_list
Created attachment 869655 [details] File: environ
Created attachment 869656 [details] File: limits
Created attachment 869657 [details] File: maps
Created attachment 869658 [details] File: open_fds
Created attachment 869659 [details] File: proc_pid_status
Created attachment 869660 [details] File: var_log_messages
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.