New Fedora tester here on Orange Pi 5 Max
Reporting that 1password Desktop App
(installation instructions here: Get the 1Password for Linux app | 1Password Support scroll down to ARM) and the browser extension (tested in the included pre-installed Firefox included with Fedora, and Chromium installed via package manager non-Flatpak) cannot communicate with eachother. They report connection error inside the extension.
Note that the 1Password app is a 3rd party app and does not come from fedora.
It seems they may not have fully updated the app to work properly in fedora 43 on arm64. This means support for your problem probably needs to come from their site. They probably also need to coordinate with the developers of Firefox and Chromium.
Hi Jeff and thanks for the reply! I totally get that it’s not a Fedora made software but the problem does seem to affect Fedora and not the other arm-based distros I also boot into (still in the testing phase between a bunch)
I thought maybe someone would identify a quick fix, maybe something like a filesystem location difference in Fedora or something similar
Or, even better, maybe encounter another 1password user who also solved this problem as it’s a pretty popular password manager
I will try to report it to 1password as well, thanks anyway!
If the app puts something the wrong place as you thought, then it may be a fedora change, but only the user of that app would be able to identify the change since they are the only one with the detals.
You might be able to use journalctl --no-hostname --no-pager -f in a terminal when you try starting the app and see what it tells you.
Thank you again, I’ll give that a try
In case some power user is out there and wants to make short work of this problem (at their leisure of course) I can condense the steps down and no accounts or anything are required. You just need a web browser to check
Desktop app instructions from Get the 1Password for Linux app | 1Password Support
curl -sSO https://downloads.1password.com/linux/tar/stable/aarch64/1password-latest.tar.gz
tar -xf 1password-latest.tar.gz
sudo mkdir -p /opt/1Password && sudo mv 1password-*/* /opt/1Password
sudo /opt/1Password/after-install.sh
1password
If you only have x86 and no aarch64, maybe the same symptoms would happen. substitute the URL for this: curl -sSO https://downloads.1password.com/linux/tar/stable/x86_64/1password-latest.tar.gz
Then click on your browser here to install the matching extension Download the Best Password Manager for Your Browser | 1Password
At this point both will be asking you for a username and password, but we don’t need it. Just right click the browser extension and press Settings, and if it was working, you’d see this:
But on Fedora it is yellow and says Connection Problem
Just in case anybody has a free moment to spare of course, I will expect nothing but hope for anything! haha
Those steps theoretically should provide some info in journalctl, but I don’t know if it would be in ‘journalctl’ for the system or ‘journalctl --user’ for the user specific part.
Just a hunch but I wonder if there are any SELinux denials.
Is there anything in the output of sudo ausearch -m avc -ts today ?
Nothing worthwhile in journalctl that makes sense to me at least
$ journalctl --user
Oct 30 15:54:42 orangepi5max systemd[3292]: Queued start job for default target default.target.
Oct 30 15:54:42 orangepi5max systemd[3292]: Created slice app.slice - User Application Slice.
Oct 30 15:54:42 orangepi5max systemd[3292]: Started drkonqi-sentry-postman.path - Submitting pending crash events (file monitor).
Oct 30 15:54:42 orangepi5max systemd[3292]: drkonqi-coredump-cleanup.timer - Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/snow/.cache/kcrash-metadata/*.ini).
Oct 30 15:54:42 orangepi5max systemd[3292]: drkonqi-sentry-postman.timer - Submitting pending crash events was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/snow/.cache/drkonqi/sentry-envelopes/*).
Oct 30 15:54:42 orangepi5max systemd[3292]: Started grub-boot-success.timer - Mark boot as successful after the user session has run 2 minutes.
Oct 30 15:54:42 orangepi5max systemd[3292]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of User's Temporary Directories.
Oct 30 15:54:42 orangepi5max systemd[3292]: Reached target paths.target - Paths.
Oct 30 15:54:42 orangepi5max systemd[3292]: Reached target timers.target - Timers.
Oct 30 15:54:42 orangepi5max systemd[3292]: Starting dbus.socket - D-Bus User Message Bus Socket...
Oct 30 15:54:42 orangepi5max systemd[3292]: Listening on drkonqi-coredump-launcher.socket - Socket to launch DrKonqi for a systemd-coredump crash.
Oct 30 15:54:42 orangepi5max systemd[3292]: Listening on pipewire-pulse.socket - PipeWire PulseAudio.
Oct 30 15:54:42 orangepi5max systemd[3292]: Listening on pipewire.socket - PipeWire Multimedia System Sockets.
Oct 30 15:54:42 orangepi5max systemd[3292]: Listening on systemd-ask-password.socket - Query the User Interactively for a Password.
Oct 30 15:54:42 orangepi5max systemd[3292]: Starting systemd-tmpfiles-setup.service - Create User Files and Directories...
Oct 30 15:54:42 orangepi5max systemd[3292]: Listening on dbus.socket - D-Bus User Message Bus Socket.
Oct 30 15:54:42 orangepi5max systemd[3292]: Reached target sockets.target - Sockets.
Oct 30 15:54:42 orangepi5max systemd[3292]: Finished systemd-tmpfiles-setup.service - Create User Files and Directories.
Oct 30 15:54:42 orangepi5max systemd[3292]: Reached target basic.target - Basic System.
Oct 30 15:54:42 orangepi5max systemd[3292]: drkonqi-coredump-cleanup.service - Cleanup lingering KCrash metadata was skipped because of an unmet condition check (ConditionPathExistsGlob=/home/snow/.cache/kcrash-metadata/*.ini).
Oct 30 15:54:42 orangepi5max systemd[3292]: Starting unity-gtk-module.service - Unity GTK Module Environment variables...
Oct 30 15:54:42 orangepi5max systemd[3292]: Created slice session.slice - User Core Session Slice.
Oct 30 15:54:42 orangepi5max systemd[3292]: Starting dbus-broker.service - D-Bus User Message Bus...
Oct 30 15:54:42 orangepi5max dbus-broker-launch[3311]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Oct 30 15:54:42 orangepi5max dbus-broker-launch[3311]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
$ journalctl --no-hostname --no-pager -f
Oct 31 14:12:27 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 31 14:12:27 audit: BPF prog-id=87 op=UNLOAD
Oct 31 14:12:27 audit: BPF prog-id=86 op=UNLOAD
Oct 31 14:12:27 audit: BPF prog-id=85 op=UNLOAD
Oct 31 14:12:27 systemd[1588]: Started app-org.kde.konsole-3649.scope.
Oct 31 14:12:28 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 2056192 bytes), total 32768 (slots), used 21592 (slots)
Oct 31 14:12:30 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1916928 bytes), total 32768 (slots), used 20540 (slots)
Oct 31 14:12:33 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 282624 bytes), total 32768 (slots), used 24548 (slots)
Oct 31 14:12:36 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 626688 bytes), total 32768 (slots), used 24548 (slots)
Oct 31 14:12:38 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 1048576 bytes), total 32768 (slots), used 18004 (slots)
Oct 31 14:12:56 systemd[1588]: Started app-org.chromium.Chromium-3883.scope.
Oct 31 14:12:58 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 16384 bytes), total 32768 (slots), used 32726 (slots)
Oct 31 14:12:58 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 262144 bytes), total 32768 (slots), used 32246 (slots)
Oct 31 14:12:59 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 27832 (slots)
Oct 31 14:12:59 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 483328 bytes), total 32768 (slots), used 24548 (slots)
Oct 31 14:13:00 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 25722 (slots)
Oct 31 14:13:05 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 442368 bytes), total 32768 (slots), used 18658 (slots)
Oct 31 14:13:05 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 704512 bytes), total 32768 (slots), used 18300 (slots)
Oct 31 14:13:13 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 131072 bytes), total 32768 (slots), used 32688 (slots)
Oct 31 14:13:21 systemd[1588]: Starting grub-boot-success.service - Mark boot as successful...
Oct 31 14:13:21 systemd[1588]: Finished grub-boot-success.service - Mark boot as successful.
Oct 31 14:13:29 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 32768 bytes), total 32768 (slots), used 32718 (slots)
Oct 31 14:13:29 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 131072 bytes), total 32768 (slots), used 32588 (slots)
Oct 31 14:13:30 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 25642 (slots)
Oct 31 14:13:34 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 65536 bytes), total 32768 (slots), used 32654 (slots)
Oct 31 14:13:35 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 29800 (slots)
Oct 31 14:13:35 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 25644 (slots)
Oct 31 14:13:39 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 262144 bytes), total 32768 (slots), used 32584 (slots)
Oct 31 14:13:39 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 65536 bytes), total 32768 (slots), used 32640 (slots)
Oct 31 14:13:51 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 30002 (slots)
Oct 31 14:13:53 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 20852 (slots)
Oct 31 14:14:37 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 32768 bytes), total 32768 (slots), used 32706 (slots)
Oct 31 14:14:39 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 65536 bytes), total 32768 (slots), used 32648 (slots)
Oct 31 14:14:49 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 131072 bytes), total 32768 (slots), used 32554 (slots)
Oct 31 14:14:50 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 131072 bytes), total 32768 (slots), used 32618 (slots)
Oct 31 14:14:52 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 131072 bytes), total 32768 (slots), used 32642 (slots)
Oct 31 14:14:53 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 32340 (slots)
Oct 31 14:14:57 kernel: rockchip-drm display-subsystem: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 30232 (slots)
Log is making tons of these buffer is full warnings though
$ sudo ausearch -m avc -ts today
[sudo] password for user:
<no matches>
Nothing in that second command either I’m afraid 
1password is running for the desktop and fully unlocked – still cannot communicate with the extension
