search

keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Inability to access file in Nautilus #4116

Open richardkaler opened 2 years ago

richardkaler commented 2 years ago

System Info: Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal

When I check to see if Keybase is running, the system indicates the service is activated. Please note the following output:

Loaded: loaded (/usr/lib/systemd/user/keybase.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-03-16 05:14:32 EDT; 6h ago Main PID: 7304 (keybase) Memory: 153.6M CGroup: /user.slice/user-1000.slice/user@1000.service/keybase.service └─7304 /usr/bin/keybase --use-default-log-file --debug service

Mar 16 05:14:32 systemd[2113]: Starting Keybase core service... Mar 16 05:14:32 systemd[2113]: Started Keybase core service.

Yet, when I check in the Keybase root directory with < ls /keybase> I get the following:

KBFS_NOT_RUNNING

Aside from the aforementioned issues, I still haven't figured out how to access my Keybase file or folders in Nautilus.

When I click on a file, I am inundated with a barrage of error messages. Here's a sample:

Unknown Error: "/keybase/private//<homeuser./<FileLocation" (Several other errors are also listed).

I can only access files through $ /run/user/1000/keybase/kbfs/private/

The location above limits me to say the least. Saving files in the /run directory allows me to access the files through Keybase and locally but none of them are uploaded in the Keybase server; consequently, I can't access them on other devices, which defeats the purpose of cloud storage.

I suspect many other users are going through this issue. I may share my logs, but the Keybase team will have to persuade me that only the metadata is used and none of my data e.g., files and directories can be viewed by the team. I get the standard assurance is that "not even Keybase can view the files." Are there any audits to prove this.

I also don't exactly understand how the syncing works. I assume the syncing is one way, downloaded to the local device though no files from the device are automatically uploaded without them being deliberately placed in synced Keybase directories.

The documentation is somewhat limited on several issues here. Please assist.

More background:

When I run kbfs, I get the following errors:

▶ ERROR Error initializing disk cache: resource temporarily unavailable 2022/03/16 11:47:46 mount helper error: fusermount: mount failed: Operation not permitted

Of course, no errors are present on root though I am of the understanding though this is irrelevant as Keybase shouldn't be run as root, per the documentation: https://book.keybase.io/guides/linux

"Note that keybase cannot be run as root, and must be run as a user. Accordingly, it runs under the system user manager of a particular user, not the global system manager."

I've spent hours on this to no avail. Alas, I am throwing my hands up. Someone, please bail me out or share some anecdotal advice.

It would be super cool if the Keybase team knew exactly what's up ...

nabeelraza-7 commented 5 months ago

I'm also facing this issue.