Description of problem: Another attempt at properly reporting difficulties I have with mysql-workbench simply quitting on me. It happens from time to time, but is difficult to reproduce reliably. This particular instance is exactly like Bug 857148. I attempt a query, hit the lightning bolt icon, and the mysql-workbench window just vanishes. If I immediately re-launch and try the same query, mysql-workbench quits again. But if I immediately re-launch and try a different query, mysql-workbench does not quit. My first guess was that there was some data-related weirdness. But trying the "death query" at arbitrary points in the future (e.g.: The next day--after logging out and in again, after lunch--without logging out and in again) tend not to produce the same error, even if table data has not changed. 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: glibmm_unexpected_exception executable: /usr/libexec/mysql-workbench-bin kernel: 3.8.3-201.fc18.x86_64 uid: 1000 var_log_messages: Mar 18 08:34:02 aschmidt abrt[18310]: Saved core dump of pid 17929 (/usr/libexec/mysql-workbench-bin) to /var/spool/abrt/ccpp-2013-03-18-08:33:59-17929 (145985536 bytes) Truncated backtrace: Thread no. 1 (7 frames) #2 glibmm_unexpected_exception at exceptionhandler.cc:71 #3 Glib::exception_handlers_invoke at exceptionhandler.cc:150 #4 Glib::DispatchNotifier::pipe_io_handler at dispatcher.cc:464 #5 operator() at /usr/include/sigc++-2.0/sigc++/functors/slot.h:515 #6 Glib::IOSource::dispatch at main.cc:1162 #7 Glib::Source::dispatch_vfunc at main.cc:956 #12 gtk_main at gtkmain.c:1257 Potential duplicate: bug 706544
Created attachment 712107 [details] File: backtrace
Created attachment 712108 [details] File: build_ids
Created attachment 712109 [details] File: cgroup
Created attachment 712110 [details] File: core_backtrace
Created attachment 712111 [details] File: dso_list
Created attachment 712112 [details] File: environ
Created attachment 712113 [details] File: limits
Created attachment 712114 [details] File: maps
Created attachment 712115 [details] File: open_fds
Created attachment 712116 [details] File: proc_pid_status
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.