Version-Release number of selected component: mysql-workbench-5.2.47-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/mysql-workbench-bin crash_function: release executable: /usr/libexec/mysql-workbench-bin kernel: 3.8.3-201.fc18.x86_64 uid: 1000 var_log_messages: Mar 18 09:01:19 localhost abrt[7229]: Saved core dump of pid 5723 (/usr/libexec/mysql-workbench-bin) to /var/spool/abrt/ccpp-2013-03-18-09:01:19-5723 (183775232 bytes) Truncated backtrace: Thread no. 1 (10 frames) #5 release at ../../library/grt/src/grtpp_value.h:149 #6 ~ValueRef at ../../library/grt/src/grtpp.h:225 #7 ~DictRef at ../../library/grt/src/grtpp.h:1589 #8 Mysql_sql_syntax_check::check_sql_statement(char const*, boost::function<Sql_parser_base::Parse_result (mysql_parser::SqlAstNode const*)>, Sql_syntax_check::ObjectType) at src/mysql_sql_syntax_check.cpp:174 #9 Mysql_sql_syntax_check::check_sql at src/mysql_sql_syntax_check.cpp:125 #10 Sql_editor::do_check_sql at sqlide/sql_editor_be.cpp:554 #11 boost::_mfi::mf2<grt::Ref<grt::internal::String>, Sql_editor, grt::GRT*, boost::weak_ptr<Sql_editor> >::operator() at /usr/include/boost/bind/mem_fn_template.hpp:280 #12 operator()<grt::Ref<grt::internal::String>, boost::_mfi::mf2<grt::Ref<grt::internal::String>, Sql_editor, grt::GRT*, boost::weak_ptr<Sql_editor> >, boost::_bi::list1<grt::GRT*&> > at /usr/include/boost/bind/bind.hpp:382 #13 operator()<grt::GRT*> at /usr/include/boost/bind/bind_template.hpp:32 #14 boost::detail::function::function_obj_invoker1<boost::_bi::bind_t<grt::Ref<grt::internal::String>, boost::_mfi::mf2<grt::Ref<grt::internal::String>, Sql_editor, grt::GRT*, boost::weak_ptr<Sql_editor> >, boost::_bi::list3<boost::_bi::value<Sql_editor*>, boost::arg<1>, boost::_bi::value<boost::weak_ptr<Sql_editor> > > >, grt::Ref<grt::internal::String>, grt::GRT*>::invoke at /usr/include/boost/function/function_template.hpp:132 Potential duplicate: bug 861684
Created attachment 711743 [details] File: backtrace
Created attachment 711744 [details] File: cgroup
Created attachment 711745 [details] File: core_backtrace
Created attachment 711746 [details] File: dso_list
Created attachment 711747 [details] File: environ
Created attachment 711748 [details] File: limits
Created attachment 711749 [details] File: maps
Created attachment 711750 [details] File: open_fds
Created attachment 711751 [details] File: proc_pid_status
Had opened a query editor but crashed instantly after it asked for password. It seems MySQL Workbench cannot store passwords in keyring properly on my Fedora 18 Gnome with KDM as default. It always asks me to store data in keyring even though I have previously stored it, and even after storing the connection password in keyring, I am prompted again when I start MySQL Workbench the next time around. backtrace_rating: 4 cmdline: /usr/libexec/mysql-workbench-bin crash_function: release executable: /usr/libexec/mysql-workbench-bin kernel: 3.8.4-202.fc18.x86_64 package: mysql-workbench-5.2.47-2.fc18 reason: Process /usr/libexec/mysql-workbench-bin was killed by signal 11 (SIGSEGV) uid: 1000 ureports_counter: 1
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.