# Error with Chronic after installing a different plugin

**URL:** <https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537>\
**Category:** Rails\
**Created:** [June 4, 2008, 7:54pm UTC](https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537 "2008-06-04T19:54:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![gorgeoussoul](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/6f9a4e/32.png) [@gorgeoussoul](https://www.ruby-forum.com/u/gorgeoussoul)\
**Post date:** [June 4, 2008, 7:54pm UTC](https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537/1 "2008-06-04T19:54:20Z")

</div>

I’ve had Chronic installed for some time and it’s been working well.  
Yesterday I loaded ImageMagick and RMagick and ran “gem update --system”  
(part of RMagick’s installation instructions). I haven’t had time to do  
anything with RMagick or ImageMagick though, because as soon as I bring  
up a page from one of the controllers requiring Chronic, I see this:

Gem::Exception in xxController#list  
can’t activate rubyforge (\>= 1.0.0), already activated rubyforge-0.4.4]

or this:

no such file to load – chronic

I tried uninstalling the Chronic gem and then reinstalling it. But,  
there is no change.

I’m fairly new working with Rails and don’t really know where to start.  
Any idea how I can fix this?

Thanks

---

<div class="post-metadata">

**Author:** ![gorgeoussoul](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/6f9a4e/32.png) [@gorgeoussoul](https://www.ruby-forum.com/u/gorgeoussoul)\
**Post date:** [July 22, 2008, 3:25pm UTC](https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537/2 "2008-07-22T15:25:54Z")

</div>

OK, so I’m now having a similar problem. On one of my servers, I am  
still running rails 1.2.6 (due to upgrade very soon), but needed to  
update pdf-writer to fix the totalpagenum bug.

now I am getting the same  
can’t activate rubyforge (\>= 1.0.0), already activated  
rubyforge-0.4.4]  
when i try to use (require) pdf/writer

I have looked at the other similar posts about this, but cant really  
make sense of what the problem is.

Presumably requiring pdf-writer wants to use rubyforge(\>=1.00) [to  
unpack it?]. So can I just update ruby forge, or do I remove  
rubyforge 1.0.0 or am i just plain stuck till i update rails  
altogether??

Please if anyone can shed some light I’d be grateful  
Thanks  
Tonypm

---

<div class="post-metadata">

**Author:** ![gorgeoussoul](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/6f9a4e/32.png) [@gorgeoussoul](https://www.ruby-forum.com/u/gorgeoussoul)\
**Post date:** [July 22, 2008, 3:48pm UTC](https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537/3 "2008-07-22T15:48:09Z")

</div>

Thanks, Denise, you were a real and rapid help.

I did gem uninstall rubyforge  
which gave me

Select RubyGem to uninstall:

1. rubyforge-0.4.2
2. rubyforge-1.0.0
3. All versions

So I held my breath, entered 1. and restarted lighty and bingo all is  
serene

Many Thanks

On Jul 22, 2:32 pm, Denise R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![gorgeoussoul](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/6f9a4e/32.png) [@gorgeoussoul](https://www.ruby-forum.com/u/gorgeoussoul)\
**Post date:** [July 22, 2008, 4:06pm UTC](https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537/4 "2008-07-22T16:06:04Z")

</div>

Awesome. So glad to hear that. 🙂

---

<div class="post-metadata">

**Author:** ![gorgeoussoul](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/g/6f9a4e/32.png) [@gorgeoussoul](https://www.ruby-forum.com/u/gorgeoussoul)\
**Post date:** [July 22, 2008, 3:32pm UTC](https://www.ruby-forum.com/t/error-with-chronic-after-installing-a-different-plugin/139537/5 "2008-07-22T15:32:01Z")

</div>

I’m not sure I can help much. I ended up asking a consultant friend of  
mine for help. He just uninstalled the older rubyforge gem (gem  
uninstall rubyforge) and then left. Unfortunately, I had a couple more  
issues after that. I don’t remember all of them, but I do know that I  
had to change some stuff in the environment.rb file.

Wish I could be more descriptive…

GorgeousSoul