On Tue, Aug 15, 2017 at 9:28 AM, Dutch Ingraham <[email protected]> wrote:
> Hi all:
>
> I'm having a problem with Codeblocks not exiting cleanly when using the
> Awesome WM. I've filed a bug report[1] but the wrangler closed it almost
> immediately without any testing or attempt to confirm, so I'm asking for
> your help here.
>
I don't necessarily agree with the closure of the bug report. I
suspect such closures happen because the first responder does not know
how to troubleshoot the issue. However, the Gentoo developers care a
lot more than, say, the Mozilla developers. Every bug report I have
sent to Mozilla trackers has been ignored.
It seems like a tossup: Awesome might be launching Code::Blocks in a
way that leaves the process unable to close itself, but seeing as I
don't actually know how that would happen, you might have better luck
asking the Code::Blocks developers as they will know how to
troubleshoot their project. They then might be able to figure out that
it is something else's fault.
> 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, both 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.
>
> 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.
>
> This is likely not strictly an upstream issue. This is almost certainly a
> Gentoo
> issue, as issue I presented does not appear in Arch, Debian, or Fedora.
> All three have the exact 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.
>
> Any help or other insights in debugging this issue are appreciated.
>
When I encounter issues like this I try to find the newest version of
the project. In this case, it looks like 16.01 is the latest release
of Code::Blocks. You might try building from their repository. It will
take time to become acquainted with the different build systems
(automake, CMake, ...) but you can generally specify a custom
installation directory -- ~/.local is a good place. Add the binary
paths inside of that directory to your PATH.
You can also run a command to kill Code::Blocks after you exit, or use
another IDE (like Geany). Some example commands:
ps | awk '/codeblocks/ { print $1; }' | xargs kill
kill `pgrep codeblocks`
pkill codeblocks
Be careful that you don't kill processes that contain the name you
give but aren't the one you mean. The regex in the first command will
be easier to customize. Pkill and pgrep are nonstandard.
R0b0t1.
