Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Caja is respawning itself, as you predicted, in an endless loop. I think it's time to give up on this. I will probably keep the binary and try to run it in another desktop environment when I have a chance.
I would do the following:
back up the original caja
replace the original with my self-compiled copy
log out, then log back in
If it works, great, if not, log in to a console and restore the original
If it works, great, if not, log in to a console and restore the original
I was about to do this, but then I noticed something odd: the size of the executable compiled by me is 10 MB whereas the size of the original caja (in /usr/bin) is about 2 MB. How can the size be so different? Should I go ahead?
I was curious, so I tried it myself. I'm running Fedora Rawhide, so I downloaded the caja source rpm and the needed devel files and rebuilt caja using 144 (300%) as the largest icon size instead of the default 192 (400%). Both my original and my rebuilt /usr/bin/caja files are only about 2 MB, but the caja rpm itself was about 4.2 MB, and I had to install the caja-schemas rpm (13.1 MB), and the caja-core-extensions rpm (also 13.1 MB). The attached image show icons at 100%, 200%, and 300%
I was curious, so I tried it myself. I'm running Fedora Rawhide, so I downloaded the caja source rpm and the needed devel files and rebuilt caja using 144 (300%) as the largest icon size instead of the default 192 (400%). Both my original and my rebuilt /usr/bin/caja files are only about 2 MB, but the caja rpm itself was about 4.2 MB, and I had to install the caja-schemas rpm (13.1 MB), and the caja-core-extensions rpm (also 13.1 MB). The attached image show icons at 100%, 200%, and 300%
When you rebuilt it, did you just use its own config? I am not expert at all with this, so I am wondering whether perhaps I did something wrong or missed something.
What I did was:
1. I ran ./autogen.sh
2. I built with ./make
When you rebuilt it, did you just use its own config?
I used rpmbuild which used Fedora's spec file (which I did not modify) to build the rpm's after I changed the icon size. Fedora uses a configuration that includes
I assumed you used the actual caja source. What distro are you using? If your distro has a source package and the tools build the binary from it, that would definitely be the easiestway to go.
Sorry, I did not explain myself well, I did build from source. I downloaded it from the official Caja account on Github.
My OS is Manjaro. I still do not know how to build via the package manager. I will look into it.
What I did was simply: running autogen.sh and then ./make
I have manjaro installed, but never tried to build a package for it. I'm going to try my Fedora-compiled version of the caja binary on it. Will be back in a few minutes to let you know if it worked
But here's how I performed the trial (which you should be able to do, also)
open a terminal and become root (sudo su)
copy /usr/bin/caja to my home directory
copy my replacement caja to /usr/bin
logout
log back in
my desktop icons didn't show, so I knew something wasn't right. I opened a terminal window and tried to run caja
gave me error message
logout
from the Manjaro login screen, open a console (Alt-F2)
login
sudo su
copy the Manjaro caja back to /usr/bin
log out of console
Alt-F7 to get back to the graphical login screen
login
everything is back to the way it was
Thanks a lot for taking the time to write this mini-tutorial, I appreciate it.
I think the best thing for me is to stop playing with the idea of modifying Caja myself, as I would surely mess up. Instead, I have already filed a feature request in their bug tracking system.
Thanks to everyone for the help
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.