# Error when starting JuliaPro v1.4.1

**URL:** <https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223>\
**Category:** New to Julia\
**Tags:** question, juliapro\
**Created:** [May 26, 2020, 9:57pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223 "2020-05-26T21:57:19Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![akahs](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/akahs/32/15377_2.png) [@akahs](https://discourse.julialang.org/u/akahs)\
**Post date:** [May 26, 2020, 9:57pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/1 "2020-05-26T21:57:19Z")

</div>

Just installed JuliaPro v1.4.1 and seeing the following error when starting Julia…

```julia
Starting Julia...
[Info: Precompiling Atom [c52e3926-4ff0-5f6e-af25-54175e0327b1]
ERROR: LoadError: LoadError: ArgumentError: Package Atom does not have Traceur in its dependencies:
- If you have Atom checked out for development and have
  added Traceur as a dependency but haven't updated your primary
  environment's manifest file, try `Pkg.resolve()`.
- Otherwise you may need to report an issue with Atom
Stacktrace:
 [1] require(::Module, ::Symbol) at .\loading.jl:905
 [2] include(::Module, ::String) at .\Base.jl:377
 [3] include(::String) at C:\Users\...\.juliapro\JuliaPro_v1.4.1-1\packages\Atom\wlPiw\src\Atom.jl:4
 [4] top-level scope at C:\Users\...\.juliapro\JuliaPro_v1.4.1-1\packages\Atom\wlPiw\src\Atom.jl:67
 [5] include(::Module, ::String) at .\Base.jl:377
 [6] top-level scope at none:2
 [7] eval at .\boot.jl:331 [inlined]
 [8] eval(::Expr) at .\client.jl:449
 [9] top-level scope at .\none:3
in expression starting at C:\Users\...\.juliapro\JuliaPro_v1.4.1-1\packages\Atom\wlPiw\src\profiler\traceur.jl:1
in expression starting at C:\Users\...\.juliapro\JuliaPro_v1.4.1-1\packages\Atom\wlPiw\src\Atom.jl:67
ERROR: LoadError: Failed to precompile Atom [c52e3926-4ff0-5f6e-af25-54175e0327b1] to C:\Users\...\.juliapro\JuliaPro_v1.4.1-1\compiled\v1.4\Atom\w9XOh_5ybJQ.ji.
Stacktrace:
 [1] error(::String) at .\error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at .\loading.jl:1272
 [3] _require(::Base.PkgId) at .\loading.jl:1029
 [4] require(::Base.PkgId) at .\loading.jl:927
 [5] require(::Module, ::Symbol) at .\loading.jl:922
 [6] top-level scope at C:\Users\...\AppData\Local\JuliaPro-1.4.1-1\.atom\packages\julia-client\script\boot_repl.jl:56
 [7] include(::Module, ::String) at .\Base.jl:377
 [8] exec_options(::Base.JLOptions) at .\client.jl:288
 [9] _start() at .\client.jl:484
in expression starting at C:\Users\...\AppData\Local\JuliaPro-1.4.1-1\.atom\packages\julia-client\script\boot_repl.jl:1

```

---

<div class="post-metadata">

**Author:** ![Javier\_Quintero](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/javier_quintero/32/10082_2.png) [@Javier\_Quintero](https://discourse.julialang.org/u/Javier_Quintero)\
**Post date:** [May 27, 2020, 7:18am UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/2 "2020-05-27T07:18:32Z")

</div>

Jus had similar problem with Juno in Atom.  
I solved that by updating package Atom.

I opened a Julia REPL,  
went to package prompt by typing ],  
type `update` and hit Enter,  
wait until all packages get updated,  
hit backspace to return to normal Julia prompt  
go back to Atom editor,  
Ctr+j Ctr+k to stop Julia  
Ctr+j Ctr+s to start Julia  
and that’s it

hope it works for you as well

---

<div class="post-metadata">

**Author:** ![dadada\_dadada](https://avatars.discourse-cdn.com/v4/letter/d/ce7236/32.png) [@dadada\_dadada](https://discourse.julialang.org/u/dadada_dadada)\
**Post date:** [May 27, 2020, 12:35pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/3 "2020-05-27T12:35:21Z")

</div>

I have the same issue. Tried ] update but it did not work.

```julia
 [Info: Precompiling Atom [c52e3926-4ff0-5f6e-af25-54175e0327b1]
┌ Warning: Package Atom does not have Traceur in its dependencies:
│ - If you have Atom checked out for development and have
│ added Traceur as a dependency but haven't updated your primary
│ environment's manifest file, try `Pkg.resolve()`.
│ - Otherwise you may need to report an issue with Atom
└ Loading Traceur into Atom from project dependency, future warnings for Atom are suppressed.

```

---

<div class="post-metadata">

**Author:** ![res0nanc3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/res0nanc3/32/15210_2.png) [@res0nanc3](https://discourse.julialang.org/u/res0nanc3)\
**Post date:** [May 27, 2020, 12:41pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/4 "2020-05-27T12:41:57Z")

</div>

Exactly the same issue just started to happen for me. Also tried the suggested fix with ] update but no luck.

Can confirm that a clean reinstall did not fix the problem. I got warnings when precompiling the “Plots” package that traceur was missing.

---

<div class="post-metadata">

**Author:** ![waqas](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/waqas/32/15176_2.png) [@waqas](https://discourse.julialang.org/u/waqas)\
**Post date:** [May 27, 2020, 3:00pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/5 "2020-05-27T15:00:45Z")

</div>

If you updated the package in Atom then this is probably the reason. As I have just updated julia-client (I am not sure about the package name) and started getting the same error after that.

It was working fine before the update.

---

<div class="post-metadata">

**Author:** ![akahs](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/akahs/32/15377_2.png) [@akahs](https://discourse.julialang.org/u/akahs)\
**Post date:** [May 27, 2020, 5:22pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/6 "2020-05-27T17:22:38Z")

</div>

Switched from JuliaPro to Atom with vanilla Julia and not seeing this problem.

---

<div class="post-metadata">

**Author:** ![izzatum](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/izzatum/32/15982_2.png) [@izzatum](https://discourse.julialang.org/u/izzatum)\
**Post date:** [May 27, 2020, 7:25pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/7 "2020-05-27T19:25:53Z")

</div>

I removed Atom in the REPL via rm Atom, and then I reinstalled it with Pkg.add(“Atom”) and Pkg.build(“Atom”).

Restart Julia by doing Ctr+j + Ctr+k (to stop Julia) and Ctr+j + Ctr+s (to start Julia), the issue has been resolved.

I hope it works for you as well.

---

<div class="post-metadata">

**Author:** ![res0nanc3](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/res0nanc3/32/15210_2.png) [@res0nanc3](https://discourse.julialang.org/u/res0nanc3)\
**Post date:** [May 27, 2020, 8:31pm UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/8 "2020-05-27T20:31:43Z")

</div>

This did the job. Thanks a lot.

---

<div class="post-metadata">

**Author:** ![EmadAlamoudi](https://avatars.discourse-cdn.com/v4/letter/e/35a633/32.png) [@EmadAlamoudi](https://discourse.julialang.org/u/EmadAlamoudi)\
**Post date:** [May 28, 2020, 8:44am UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/9 "2020-05-28T08:44:07Z")

</div>

That solve the issue for me. Thanks a lot

---

<div class="post-metadata">

**Author:** ![andreasnoack](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/andreasnoack/32/27_2.png) [@andreasnoack](https://discourse.julialang.org/u/andreasnoack)\
**Post date:** [May 28, 2020, 8:45am UTC](https://discourse.julialang.org/t/error-when-starting-juliapro-v1-4-1/40223/10 "2020-05-28T08:45:55Z")

</div>

We have now identified the issue. With the latest of Atom.jl, Registrator introduced wrong bounds in the Compat.toml file [in the registry](https://github.com/JuliaRegistries/General/pull/14961). The problem is isolated to the version of Registrator running on JuliaHub so relatively few packages should be affected. We have now fixed the issue in the JuliaPro registry so you should be able to resolve the issue locally by updating your packages.

We are currently working of fixing the General registry for all affected packages.