Rattle no longer working after upgrade

537 views
Skip to first unread message

Brian Feeny

unread,
Nov 5, 2013, 8:16:59 PM11/5/13
to rattle-users
It had been a while since I used rattle.

I upgraded R to the latest R-3.0-branch, upgraded all my packages and upgraded R Studio, and when I launch rattle I just get a Session aborted screen.

I tried numerous things to recover from this, including re-installing latest versions of GTK2+

finally I removed all GTK:

rm -rf GTK+.framework/

removed R

rm -rf /Library/Frameworks/R.framework /Applications/R.app /Applications/R64.app
rm -f /usr/bin/R /usr/bin/Rscript /usr/bin/R32 /usr/bin/R64

re-installed R 2.15
re-installed GTK 2.18.5
re-installed RStudio .97 551

and I still get the same thing. When I fire it up (from either RStudio or R64 CLI):

library(rattle)
rattle()

I get a single gray X windows window with nothing in it, and the following in my R console:

> rattle()
Error: attempt to apply non-function
In addition: Warning message:
In method(obj, ...) : Unknown internal child: selection
>


Any ideas?

Brian Feeny

unread,
Nov 5, 2013, 8:32:54 PM11/5/13
to rattle...@googlegroups.com
I was able to get it to work by doing:

library(rattle)
crv$rattleUI <- "rattle_macosx.ui"
rattle()

But I am unsure why I had to do that. I see its documented here:

http://rattle.togaware.com/rattle-install-troubleshooting.html

But I am running R 2.15 and GTK 2.18.5 and rattle_2.6.26

I thought on these older versions of R I would not have to do that.

Brian
> --
> You received this message because you are subscribed to the Google Groups "rattle-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rattle-users...@googlegroups.com.
> To post to this group, send email to rattle...@googlegroups.com.
> Visit this group at http://groups.google.com/group/rattle-users.
> For more options, visit https://groups.google.com/groups/opt_out.

Scott....@added-value.com

unread,
Nov 6, 2013, 1:31:40 AM11/6/13
to rattle...@googlegroups.com, rattle...@googlegroups.com
This still comes up so often. As long as this workaround is still necessary, would it make sense for the welcome message that appears when you load rattle to gives these instructions?

It seems easy enough to just say... On some versions of Mac you may need to type:
crv$rattleUI <- "rattle_macosx.ui"
rattle()

Or is this issue going to disappear in the near future?

Sent from my iPhone

Brian Feeny

unread,
Nov 6, 2013, 10:20:42 AM11/6/13
to rattle...@googlegroups.com
On togaware http://rattle.togaware.com/rattle-install-troubleshooting.html  its filed under:

Mac OS/X: R 3.0.0 and RGtk2 and Rattle


Is it really just an issue for those with R 3.0.0? Or does this now effect those on 2.15?  I ask because I am running 2.15 and it appears I need to do this every time.  I just want to confirm its running as expected and I don't have some artifacts lying around from my previous 3.0.0 install (which I removed)

Brian

Scott....@added-value.com

unread,
Nov 6, 2013, 10:22:56 AM11/6/13
to rattle...@googlegroups.com, rattle...@googlegroups.com
I've never installed R 3 and I had to do this once I upgraded OS.

Sent from my iPhone

On Nov 6, 2013, at 7:21 AM, "Brian Feeny" <bfe...@mac.com<mailto:bfe...@mac.com>> wrote:

On togaware http://rattle.togaware.com/rattle-install-troubleshooting.html its filed under:

Mac OS/X: R 3.0.0 and RGtk2 and Rattle

Is it really just an issue for those with R 3.0.0? Or does this now effect those on 2.15? I ask because I am running 2.15 and it appears I need to do this every time. I just want to confirm its running as expected and I don't have some artifacts lying around from my previous 3.0.0 install (which I removed)

Brian

On Nov 6, 2013, at 1:31 AM, Scott....@added-value.com<mailto:Scott....@added-value.com> wrote:

This still comes up so often. As long as this workaround is still necessary, would it make sense for the welcome message that appears when you load rattle to gives these instructions?

It seems easy enough to just say... On some versions of Mac you may need to type:
crv$rattleUI <- "rattle_macosx.ui"
rattle()

Or is this issue going to disappear in the near future?

Sent from my iPhone

On Nov 5, 2013, at 5:33 PM, "Brian Feeny" <bfe...@mac.com<mailto:bfe...@mac.com>> wrote:

library(rattle)
crv$rattleUI <- "rattle_macosx.ui"
rattle()

--
You received this message because you are subscribed to the Google Groups "rattle-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rattle-users...@googlegroups.com<mailto:rattle-users...@googlegroups.com>.
To post to this group, send email to rattle...@googlegroups.com<mailto:rattle...@googlegroups.com>.
--
You received this message because you are subscribed to the Google Groups "rattle-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rattle-users...@googlegroups.com<mailto:rattle-users...@googlegroups.com>.
To post to this group, send email to rattle...@googlegroups.com<mailto:rattle...@googlegroups.com>.

Graham Williams

unread,
Nov 15, 2013, 2:12:09 PM11/15/13
to rattle-users
Is it still required with the beta release? I "fixed" this back in April in the beta release but if the problem still exists we'll need to resolve it before I get a new CRAN release done.

To install the beta version:

> install.packages("rattle", repos="http://rattle.togaware.com", type="source")

Graham Williams


To unsubscribe from this group and stop receiving emails from it, send an email to rattle-users...@googlegroups.com.
To post to this group, send email to rattle...@googlegroups.com.

Scott....@added-value.com

unread,
Nov 15, 2013, 2:20:53 PM11/15/13
to rattle...@googlegroups.com

I updated to the latest version, and then was prompted to update X11.  Then after quiting and restarting R and rattle, it was no longer required…

 

Thanks!

 

Scott Porter | VP Methods

Find out how top brands stay culturally relevant. Added Value announces Cultural Traction™ 2013

Scott....@added-value.com

unread,
Nov 20, 2013, 8:54:17 PM11/20/13
to rattle...@googlegroups.com

I probably spoke too soon on this.  No longer required to type: crv$rattleUI <- "rattle_macosx.ui"

 

But now my rattle is broken…  anything I do, I get the error: 

 

Error in resetRattle() : attempt to apply non-function

 

I may have to uninstall and try again…

 

From: Porter, Scott (AVLA1 cs)
Sent: Friday, November 15, 2013 11:21 AM
To: rattle-users
Subject: RE: Rattle no longer working after upgrade

 

I updated to the latest version, and then was prompted to update X11.  Then after quiting and restarting R and rattle, it was no longer required…

 

Thanks!

 

Scott Porter | VP Methods

Find out how top brands stay culturally relevant. Added Value announces Cultural Traction™ 2013

 

From: rattle...@googlegroups.com [mailto:rattle...@googlegroups.com] On Behalf Of Graham Williams
Sent: Friday, November 15, 2013 11:12 AM
To: rattle-users
Subject: Re: Rattle no longer working after upgrade

 

Is it still required with the beta release? I "fixed" this back in April in the beta release but if the problem still exists we'll need to resolve it before I get a new CRAN release done.

Scott....@added-value.com

unread,
Nov 20, 2013, 11:03:15 PM11/20/13
to rattle...@googlegroups.com

Just to be sure, I reinstalled R and upgraded to R 2.15.3 from R 2.15.2. 

 

I reinstalled Rattle.  Rattle version 2.6.26 works fine as long as you type:

 

crv$rattleUI <- “rattle_macosx.ui”

 

Then, I re-installed the beta version:

 

install.packages("rattle", repos="http://rattle.togaware.com", type="source")

 

Version 2.6.27 brings up the UI without the crv$ bit, but anything I do, I get the error: 

 

Error in resetRattle() : attempt to apply non-function

 

 

From: Porter, Scott (AVLA1 cs)
Sent: Wednesday, November 20, 2013 5:54 PM
To: 'rattle...@googlegroups.com'
Subject: RE: Rattle no longer working after upgrade

 

I probably spoke too soon on this.  No longer required to type: crv$rattleUI <- "rattle_macosx.ui"

 

But now my rattle is broken…  anything I do, I get the error: 

 

Error in resetRattle() : attempt to apply non-function

 

I may have to uninstall and try again…

 

From: Porter, Scott (AVLA1 cs)
Sent: Friday, November 15, 2013 11:21 AM
To: rattle-users
Subject: RE: Rattle no longer working after upgrade

 

I updated to the latest version, and then was prompted to update X11.  Then after quiting and restarting R and rattle, it was no longer required…

 

Thanks!

 

Scott Porter | VP Methods

Find out how top brands stay culturally relevant. Added Value announces Cultural Traction™ 2013

 

From: rattle...@googlegroups.com [mailto:rattle...@googlegroups.com] On Behalf Of Graham Williams
Sent: Friday, November 15, 2013 11:12 AM
To: rattle-users
Subject: Re: Rattle no longer working after upgrade

 

Is it still required with the beta release? I "fixed" this back in April in the beta release but if the problem still exists we'll need to resolve it before I get a new CRAN release done.

Graham Williams

unread,
Mar 7, 2014, 11:32:47 PM3/7/14
to rattle...@googlegroups.com

Version 3.0.3 of Rattle has fixed this issue. Thanks to Akbar Waljee and Christopher T. Lowenkamp for assistance in solving the bug.

To install this version before the CRAN update please use:


> install.packages("rattle", repos="http://rattle.togaware.com", type="source")

Graham Williams

Reply all
Reply to author
Forward
0 new messages