You are not logged in.
- Topics: Active | Unanswered
#1 2016-06-23 12:40:07
- jonnybarnes
- Member
- From: Manchester, UK
- Registered: 2011-05-11
- Posts: 129
- Website
Sourcing the cause of a weird bug with gitflow
I’m running GNOME 3.20. I have an application called redshift installed also.
I have a git helper package installed from the AUR called gitflow.
When I run the command `git flow version` it gives weird output, I think. See:
$ git flow version
Startup finished in 101ms.
^CReceived SIGINT.
Received SIGRTMIN+24 from PID 8631 (kill).
0.4.2-preWhat appears to be happening is a new instance of redshift is started, then when I press Ctrl-C the new instance is quit, and finally the version of gitflow is printed.
Even weirder, everytime I do this, without fail, I am no longer able to start any new applications. All currently open apps seem to continue to work fine.
Any idea what’s going on? Where might the bug be? In gitflow or redshift, or both? Or neither and the bug is somewhere else?
Last edited by jonnybarnes (2016-06-23 12:44:31)
Offline
#2 2016-06-23 17:55:05
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: Sourcing the cause of a weird bug with gitflow
Not a Sysadmin issue, moving to NC...
Offline