[MacPorts] #52682: gpredict @1.3.2: Runnin 100% CPU after `killall`
#52682: gpredict @1.3.2: Runnin 100% CPU after `killall` -----------------------------+-------------------------------- Reporter: rubendibattista | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: gpredict -----------------------------+-------------------------------- Hello, I installed gpredict on my MBP (10.11.6). It was working fine. Then I created a new visualization module and filled it with satellites. It froze (don't know the actual reason, maybe wrong parameters of the ground station). So I killed gpredict {{{killall -KILL gpredict}}}. Now everytime I run {{{gpredict}}} it runs 100% CPU and the GUI is not showing up. What I tried: 1) Uninstall, Clean, Install 2) Reboot 3) Update X11 (2.7.10) 4) Update Ports Could be that there is some file where the visualization module is saved and it keeps trying to load it. Where does gpredict save visualization modules? -- Ticket URL: <https://trac.macports.org/ticket/52682> MacPorts <https://www.macports.org/> Ports system for OS X
#52682: gpredict @1.3.2: Runnin 100% CPU after `killall` ------------------------------+-------------------------------- Reporter: rubendibattista | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gpredict | ------------------------------+-------------------------------- Changes (by rubendibattista): * Attachment "Schermata 2016-10-23 alle 16.50.55.png" added. Screenshot -- Ticket URL: <https://trac.macports.org/ticket/52682> MacPorts <https://www.macports.org/> Ports system for OS X
#52682: gpredict @1.3.2: Runnin 100% CPU after `killall` ------------------------------+-------------------------------- Reporter: rubendibattista | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: gpredict | ------------------------------+-------------------------------- Comment (by rubendibattista): Ok, Solved. Gpredict is storing configuration file in {{{~/.config/Gpredict}}}. Removing the directory made {{{gpredict}}} great again! :P -- Ticket URL: <https://trac.macports.org/ticket/52682#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#52682: gpredict @1.3.2: Runnin 100% CPU after `killall` ------------------------------+-------------------------------- Reporter: rubendibattista | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: worksforme | Keywords: Port: gpredict | ------------------------------+-------------------------------- Changes (by mf2k): * status: new => closed * resolution: => worksforme Old description:
Hello, I installed gpredict on my MBP (10.11.6). It was working fine. Then I created a new visualization module and filled it with satellites. It froze (don't know the actual reason, maybe wrong parameters of the ground station). So I killed gpredict {{{killall -KILL gpredict}}}. Now everytime I run {{{gpredict}}} it runs 100% CPU and the GUI is not showing up.
What I tried: 1) Uninstall, Clean, Install 2) Reboot 3) Update X11 (2.7.10) 4) Update Ports
Could be that there is some file where the visualization module is saved and it keeps trying to load it. Where does gpredict save visualization modules?
New description: Hello, I installed gpredict on my MBP (10.11.6). It was working fine. Then I created a new visualization module and filled it with satellites. It froze (don't know the actual reason, maybe wrong parameters of the ground station). So I killed gpredict {{{killall -KILL gpredict}}}. Now everytime I run {{{gpredict}}} it runs 100% CPU and the GUI is not showing up. What I tried: 1. Uninstall, Clean, Install 1. Reboot 1. Update X11 (2.7.10) 1. Update Ports Could be that there is some file where the visualization module is saved and it keeps trying to load it. Where does gpredict save visualization modules? -- -- Ticket URL: <https://trac.macports.org/ticket/52682#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts