I am using Codeblocks-16.01 (the only unmasked version, which is keyworded unstable) on both a full-unstable installation and on a mostly-stable installation, with only the 'contrib' use flag set. On both installations, Codeblocks, when started from a menu in the Awesome WM, will not exit cleanly. Specifically, when exiting in any manner, the GUI will disappear, but the Codeblocks process continues to run. This prevents Codeblocks from "starting" again as only one running instance is permitted. However, when started from a terminal, Codeblocks does not show this behavior, i.e., it does shut down completely and cleanly. Additionally, this behavior does not present when using either the Plasma desktop or the Fluxbox WM, i.e., Codeblocks will shutdown cleanly whether started from a menu or from a terminal. If further information is needed, please let me know.
Created attachment 488480 [details] emerge --info
Thank you for your report. To me it sounds like a bug in the software provided upstream or a misconfiguration in your system [3]. Does the same source work for you on another distribution? I suggest to discuss this problem on a related mailing list, forum or IRC channel. I have had very good experience on the gentoo IRC [1], of course there are also forums and mailing lists. [2] I will close this bug here, because I do not see a relation to the gentoo ebuild or the way gentoo handles this special software package. Please provide more information, if I am wrong. [1] https://www.gentoo.org/get-involved/irc-channels/ [2] https://www.gentoo.org/support/ [3] look up the upstream forums search in their bugtracker
Thanks for your response. However, this is likely not an upstream issue, this is almost certainly a Gentoo issue, presuming I haven't been able to mis-configure two systems (one stable and one unstable) in the exact same way. The issue I presented does not appear in Arch, Debian, or Fedora. All three have the same version of Codeblocks as Gentoo. All three have similar versions of Awesome (all in the 4.x branch) and Arch is using the exact same version of Awesome (4.2) that I am using on both Gentoo installations noted above. Can you explain how these three other Linux distributions, with the exact same or similar software and versioning, do not present this problem but Gentoo does, without this being a Gentoo issue? Thanks.
After looking at the definition of "RESOLVED UPSTREAM" it appears as though this was closed as the problem is deemed with an upstream package and not Gentoo. May I ask which upstream? Codeblocks? Codeblocks is going to say "Our program exits cleanly on every other distro, plus it exits cleanly when you are using KDE and Fluxbox on Gentoo, so this is an Awesome WM problem." Awesome? Awesome is going to say "No other program has a problem cleanly exiting using our software. This is a Codeblocks problem." So, which upstream would you advise I file against?
