| Summary: | mysql-workbench crashes when performing any query | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Daniel McDonald <Dan.mcdonald> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | alien, balcaen.john, dmorganec, fundawang, juan.baptiste, luis.daniel.lucio, marja11, stormi-mageia |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mysql-workbench-5.2.33b-1.mga1.src.rpm | CVE: | |
| Status comment: | |||
More error messages, a bit more helpful, I think: terminate called without an active exception The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 12624 error_code 2 request_code 18 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'mysql-workbench-bin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 12625 error_code 16 request_code 28 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Samuel Verschelde
2011-10-01 13:29:42 CEST
CC:
(none) =>
balcaen.john, dlucio, dmorganec, fundawang, stormi I don't know who to assign the bug to, so I added those who touched the package in CC. (In reply to comment #2) > I don't know who to assign the bug to, so I added those who touched the package > in CC. two months later, now. ¡Ping! CC:
(none) =>
marja11 New 5.2.36 in Cauldron (2). It seems that works, verify. I wont update Mageia 1. 5.2.36 has special patch to let compile against new Gnome3 include policy. (In reply to comment #4) > New 5.2.36 in Cauldron (2). It seems that works, verify. I wont update Mageia > 1. 5.2.36 has special patch to let compile against new Gnome3 include policy. @ Daniel McDonald Did you see a chance to verify whether the problem is solved in Cauldron?
AL13N
2012-04-13 08:39:52 CEST
CC:
(none) =>
alien I have the same problem in Mageia 1 with connection to local databases too. I didn't understand comment #4 from Daniel Lucio. This is a major feature which is broken here. Any idea how to solve this? If mysql-workbench can't be updated, then we must find how to patch it.
Samuel Verschelde
2012-06-07 17:34:28 CEST
Summary:
remote mysql connections case crash when performing query =>
mysql-workbench crashes when performing any query I rebuilt the cauldron package locally on Mageia 1 and the resulting mysql-workbench doesn't crash anymore. This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad The problem is that as mysql-workbench repository isn't public, there's no easy way to create a patch that fixes this issue without updating to a newer version. CC:
(none) =>
juan.baptiste /me sighs: Oracle again... Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |
Description of problem: mysql-workbench allows a connection to a remote mysql server, but crashes whenever a query is attempted. Version-Release number of selected component (if applicable): 5.2.33b. I tried to rebuild the newer package from cauldron but I got errors after about 3 hours of compiling. How reproducible: Every time Steps to Reproduce: 1. [dmcdonald@convention ~]$ sudo urpmi mysql-gui-tools http://mirrors.mageia.org/api/mageia.1.i586.list: media/core/release/mysql-workbench-5.2.33b-1.mga1.i586.rpm installing mysql-workbench-5.2.33b-1.mga1.i586.rpm from /var/cache/urpmi/rpms Preparing... ############################################# 1/1: mysql-workbench ############################################# 2. [dmcdonald@convention ~]$ mysql-workbench Log levels '0111000' disabling log level 0 enabling log level 1 enabling log level 2 enabling log level 3 disabling log level 4 disabling log level 5 disabling log level 6 Ready. 3. add a connection to a remote server. 4. write a simple select query 5. observe error message when mysql-workbench crashes ** Message: Found auto-save workspace /home/dmcdonald/.mysql/workbench/sql_workspaces/legacy-1.autosave ** Message: query.explain built-in command is being overwritten pure virtual method called terminate called without an active exception