RPi 5 with Bitcoin Core via SNAP, trouble with bitcoin.conf

I’ve got a Raspberry Pi 5 running the latest RPi OS (Bookworm), and I installed Bitcoin Core (26.0.0) on it. Everything seemed to go pretty smoothly, the blockchain downloaded without any issues, and Bitcoin Core is up and running. Then, I thought I’d give Sparrow Wallet a shot on my MacBook Pro and connect it to the Bitcoin Core running locally on the RPi. So, I went to the Pi, opened Bitcoin Core, clicked on Options, and then on "Open Configuration File". But I got nothing. I opened a terminal and navigated to ~/snap/bitcoin-core/common/.bitcoin, where I found the bitcoin.conf file was empty. I added some settings to the config file to enable connections from local devices... From what I gather, this should set Bitcoin Core to bind to localhost and the IP address 192.168.1.33, allowing connections using the ID and password from localhost or any device in the 192.168.1.X range. After restarting Bitcoin Core, I tried to configure Sparrow Wallet to connect to my local Core server. But I hit a "Connection Refused" error when testing the connection. I checked the Core log on the RPi and all I see is a bunch of nothing... So, here are my questions... 1) When Bitcoin Core is installed through SNAP, is there some additional configuration that I need to set up to help Bitcoin Core recognize it’s not a standard install? 2) Do you see any issues in the config file I set up? 3) If using SNAP for Bitcoin Core causes all sorts of headaches, can I switch to a regular install of Bitcoin Core on my RPi and transfer the data?

Well, never mind...mostly... The issue, as is usual, was me and my misconfiguration.... I went back in to the config file and changed it to... Restarted, and the config was loaded and I can now connect using port 8335... I still don't know why trying to open the config file from within the Options panel by clicking "Open Configuration File" fails, so if someone can shed light on that it would be great. But apparently I really needed the "server=1" and to set rpcport to some other port that was not already being used for other things...