ArchR is running safely in R CLI, but "Cairo is not functional" error shows in rstudio, even Cairo is already installed.

[genomicworks]

I think I safely installed ArchR, and confimed that ArchR is running safely in R command line.
But when I run the ArchR package in rstudio,

"WARNING : Cairo check shows Cairo is not functional.
ggplot2 rasterization will not be available without Cario.
This may cause issues editing plots with many thousands of points from single cells." error comes.

But, Cairo package was already installed, (with library(Cairo) showed no error)
and the warning is not shown in R command line.

I think this is the difference between rstudio and R CLI. but I can't solve it.

In the ArchR code,
if (!.checkCairo()){
packageStartupMessage("WARNING : Cairo check shows Cairo is not functional.\n ggplot2 rasterization will not be available without Cario.\n This may cause issues editing plots with many thousands of points from single cells.")
}

Why ArchR could not check the already installed Cairo package in rstudio?
Thank you very much, everybody, firstly.

[rcorces]

Sounds like your different R setups are seeing different environments. Cairo is both a system library and an R package and both are required for Cairo to be functional.

[genomicworks]

Thank you very much for your quick response, Sir.

I checked .libPaths() in both environment, and results the same library paths are used.
Only R4.0.2 is install in my Centos7 computer.

If you can help me more,
could you tell me some more detail about what point I can check?

Thank you firstly, sir.

[rcorces]

I do not have additional input on this. The .checkCairo() function is very simple. You will have to diagnose for yourself why it is failing.

ArchR/R/GgplotUtils.R

Lines 956 to 966 in f6c0388

	.checkCairo <- function(){
	tryCatch({
	tmp <- dev.cur()
	Cairo::Cairo(type='raster')
	dev.off()
	dev.set(tmp)
	TRUE
	}, error = function(e){
	FALSE
	})
	}

Also not that Cairo is not necessarily essential for ArchR.

[genomicworks]

Thank you very much, rcorces,

I'll try by myself. (not optimistic~^^)

[sheryymm]

I have the same problem as you. Have you solved it? Thank you very much for your reply

[um-pdavila]

This may be a bug in ArchR package requirements. Updating cario R package fixed issue for us.