Bug 972289 - [abrt] mysql-workbench-5.2.47-2.fc18: type: Process /usr/libexec/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] mysql-workbench-5.2.47-2.fc18: type: Process /usr/libexec/mysql-workbe...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mysql-workbench
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:97ac5486891a628a32d174f39ef...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-08 07:20 UTC by Knut Torgersen
Modified: 2014-02-05 21:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 21:43:43 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (56.45 KB, text/plain)
2013-06-08 07:20 UTC, Knut Torgersen
no flags Details
File: cgroup (128 bytes, text/plain)
2013-06-08 07:20 UTC, Knut Torgersen
no flags Details

Description Knut Torgersen 2013-06-08 07:20:39 UTC
Description of problem:
I merely started MySQL Workbenc and logged in to see/edit my databases and then it crashed AS USUAL. First time I log in that normally happens. Some times I can expand and see my tables listed in the lefthand tree and sometimes it dies at once.

Version-Release number of selected component:
mysql-workbench-5.2.47-2.fc18

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/mysql-workbench-bin
crash_function: type
executable:     /usr/libexec/mysql-workbench-bin
kernel:         3.9.4-200.fc18.x86_64
runlevel:       N 5
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 type at grtpp.h:238
 #1 grt::get_value_by_path at grtpp_util.cpp:188
 #2 grt::GRT::get at grtpp_grt.cpp:503
 #3 wb::WBContext::get_root at workbench/wb_context.cpp:3475
 #4 wb::WBContextSQLIDE::auto_save_workspaces at sqlide/wb_context_sqlide.cpp:539
 #5 boost::function0<bool>::operator() at /usr/include/boost/function/function_template.hpp:760
 #6 bec::GRTManager::Timer::trigger at grt/grt_manager.cpp:499
 #7 bec::GRTManager::flush_timers at grt/grt_manager.cpp:601
 #8 MainForm::fire_timer at main_form.cpp:1647
 #9 operator() at /usr/include/sigc++-2.0/sigc++/functors/slot.h:440

Potential duplicate: bug 730507

Comment 1 Knut Torgersen 2013-06-08 07:20:43 UTC
Created attachment 758479 [details]
File: backtrace

Comment 2 Knut Torgersen 2013-06-08 07:20:46 UTC
Created attachment 758480 [details]
File: cgroup

Comment 3 Knut Torgersen 2013-06-08 07:58:38 UTC
I merely started MySQL Workbenc and logged in to see/edit my databases and then it crashed AS USUAL. First time I log in that normally happens. Some times I can expand and see my tables listed in the lefthand tree and sometimes it dies at once.

reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        /usr/libexec/mysql-workbench-bin
crash_function: type
executable:     /usr/libexec/mysql-workbench-bin
kernel:         3.9.4-200.fc18.x86_64
package:        mysql-workbench-5.2.47-2.fc18
reason:         Process /usr/libexec/mysql-workbench-bin was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000
xsession_errors:

Comment 4 Fedora End Of Life 2013-12-21 13:55:03 UTC
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.

Comment 5 Fedora End Of Life 2014-02-05 21:43:43 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.