FS#29147 - [oxygen-gtk3] codeblocks does not start

Attached to Project: Arch Linux
Opened by Sebastian Ziebarth (voeck) - Wednesday, 28 March 2012, 11:55 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 05 September 2012, 14:23 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrea Scarpino (BaSh)
Bartłomiej Piotrowski (Barthalion)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Code::Blocks 10.05-2 fails with an X error after the splash screen and the selection of the default compilier.

Additional info:
The exact error is:
The program 'codeblocks' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 12078 error_code 3 request_code 155 minor_code 3)
(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 full output is attached.

Steps to reproduce:
1. Execute "codeblocks"
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 05 September 2012, 14:23 GMT
Reason for closing:  No response
Comment by Kevin (anonymous_user) - Wednesday, 28 March 2012, 18:07 GMT
It works for me on x86_64.
Comment by Sebastian Ziebarth (voeck) - Wednesday, 28 March 2012, 18:28 GMT
The error occurs for me on i686 and x86_64. Maybe some more information about my systems:
Both run KDE and the nvidia driver (if that's relevant). And I have an up to date installation.

Rebuilding codeblocks or wxgtk from ABS does not help either.
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 28 March 2012, 20:51 GMT
Unable to reproduce on x86_64.

Please try gathering more information with strace or gdb by using our step by step debugging guide:
https://wiki.archlinux.org/index.php/Step_By_Step_Debugging_Guide
Comment by Bartłomiej Piotrowski (Barthalion) - Thursday, 29 March 2012, 07:34 GMT
And same here; I can't reproduce it on i686 and x86_64.
Comment by Sebastian Ziebarth (voeck) - Thursday, 29 March 2012, 10:03 GMT
I found a possible reason. I was using oxygen-gtk on both machines. When I select a different GTK theme Code::Blocks starts nicely. So this seems to be a conflict between the oxygen-gtk and Code::Blocks. Probably it is an upstream bug in either oxygen-gtk or Code::Blocks.
Comment by Alexander F. Rødseth (xyproto) - Friday, 30 March 2012, 01:16 GMT
Nice find. Please report upstream to the code::blocks developers.
Comment by Evgeniy (DrJackilD) - Monday, 02 April 2012, 00:36 GMT
I have same error, when try use CodeBlocks with oxygen-gtk theme. Works fine with other theme.
Comment by Sebastian Ziebarth (voeck) - Monday, 02 April 2012, 10:27 GMT Comment by Alexander F. Rødseth (xyproto) - Monday, 02 April 2012, 15:36 GMT
Thanks for reporting it upstream.
Comment by Bartłomiej Piotrowski (Barthalion) - Friday, 08 June 2012, 06:19 GMT
And upstream is stupid enough to close bug without reason.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 17 July 2012, 06:02 GMT
Hah, that response is golden! Probably a Mint/Kubuntu bug... Yeah.
Comment by Teodor Petrov (obfuscated) - Tuesday, 17 July 2012, 08:38 GMT
I'm the upstream dev, which closed the bug.
Probably, I've missed that the bug happens on ArchLinux box, but we have pretty similar bug reports comming from Kubuntu/mint users.
Their problems have be resolved by updating their systems. Probably the version of oxygen-gtk have been changed.

Here are some links from our forum:
http://forums.codeblocks.org/index.php/topic,16256.0.html
http://forums.codeblocks.org/index.php/topic,16232.0.html

Can you provide some backtraces?
No Archlinux around, nor do we have any fellow dev who runs it, so we cannot test on it.
Comment by Alexander F. Rødseth (xyproto) - Wednesday, 18 July 2012, 10:19 GMT
According to obfuscated on irc, this stopped being a problem after upgrading oxygen-gtk. (Thanks obfuscated). Changing subject to oxygen-gtk3 instead.
Comment by Andrea Scarpino (BaSh) - Wednesday, 18 July 2012, 10:28 GMT
I'm uploading oxygen-gtk3 1.1.0 now.
Comment by Andrea Scarpino (BaSh) - Tuesday, 24 July 2012, 08:23 GMT
status?

Loading...