Caja's zoom settings

RockDoctor · 01-13-2019, 05:12 PM

Quote:

Originally Posted by Grabby

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

Grabby · 01-28-2019, 12:24 AM

Quote:

Originally Posted by RockDoctor

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

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?

RockDoctor · 01-28-2019, 09:10 AM

I would definitely go ahead and try it, but keep that backup handy.

RockDoctor · 01-28-2019, 09:48 AM

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%

Grabby · 01-28-2019, 10:27 PM

Quote:

Originally Posted by RockDoctor

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

RockDoctor · 01-29-2019, 06:30 PM

Quote:

Originally Posted by Grabby

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

Code:

 --disable-static \
--disable-schemas-compile \
--disable-update-mimedb

which may explain why your self-compiled caja binary is so much larger

Grabby · 01-29-2019, 06:47 PM

I forgot to mention: instead of using a package from a distro (like Fedora), I had downloaded the program directly from Github.

RockDoctor · 01-29-2019, 07:01 PM

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.

Grabby · 01-29-2019, 07:15 PM

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

RockDoctor · 01-29-2019, 07:28 PM

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

RockDoctor · 01-29-2019, 07:33 PM

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.

Tried it - doesn't work. Fedora version requires libselinux.so.1, and I don't believe Manjaro uses selinux.

RockDoctor · 01-29-2019, 07:40 PM

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

Grabby · 01-31-2019, 10:40 AM

Quote:

Originally Posted by RockDoctor

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