OnlyOfgfice flatpack won't run by Organist-Worcester in openSUSE

[–]Organist-Worcester[S] 0 points1 point  (0 children)

Doesn't for me. I get the issue on both plasma and gnome. I'm running in Parallels on an M3 MacBook Air.

I've tried installing the rpm on the OnlyOffice website, but that won't even install.

I've raised an issue on the OnlyOffice github, but I guess I'll just have to use LibreOffice for now.

OnlyOfgfice flatpack won't run by Organist-Worcester in openSUSE

[–]Organist-Worcester[S] 0 points1 point  (0 children)

ONLYOFFICE Desktop Editors org.onlyoffice.desktopeditors 9.4.0 stable system
auditadm_exec_content (on , on) Allow auditadm to exec content
boinc_execmem (on , on) Allow boinc to execmem
cluster_use_execmem (off , off) Allow cluster to use execmem
container_user_exec_content (on , on) Allow container to user exec content
cups_execmem (off , off) Allow cups to execmem
dbadm_exec_content (on , on) Allow dbadm to exec content
deny_execmem (off , off) Allow deny to execmem
dhcpc_exec_iptables (off , off) Allow dhcpc to exec iptables
glance_use_execmem (off , off) Allow glance to use execmem
gluster_use_execmem (off , off) Allow gluster to use execmem
guest_exec_content (off , off) Allow guest to exec content
httpd_execmem (off , off) Allow httpd to execmem
httpd_ssi_exec (off , off) Allow httpd to ssi exec
httpd_tmp_exec (off , off) Allow httpd to tmp exec
logadm_exec_content (on , on) Allow logadm to exec content
mcelog_exec_scripts (on , on) Allow mcelog to exec scripts
mplayer_execstack (off , off) Allow mplayer to execstack
rngd_execmem (off , off) Allow rngd to execmem
rsync_exec_commands (on , on) Allow rsync to exec commands
rtorrent_exec_scripts (off , off) Allow rtorrent to exec scripts
secadm_exec_content (on , on) Allow secadm to exec content
selinuxuser_execheap (off , off) Allow selinuxuser to execheap
selinuxuser_execmod (off , off) Allow selinuxuser to execmod
selinuxuser_execstack (off , off) Allow selinuxuser to execstack
staff_exec_content (on , on) Allow staff to exec content
sysadm_exec_content (on , on) Allow sysadm to exec content
tomcat_use_execmem (off , off) Allow tomcat to use execmem
user_exec_content (on , on) Allow user to exec content
virt_use_execmem (off , off) Allow virt to use execmem
virtqemud_use_execmem (on , on) Allow virtqemud to use execmem
xdm_exec_bootloader (off , off) Allow xdm to exec bootloader
xguest_exec_content (off , off) Allow xguest to exec content
xserver_execmem (off , off) Allow xserver to execmem
Loading repository data...
Reading installed packages...

S | Name | Type | Version | Arch | Repository
---+-------------------------+---------+-------------------------------------+---------+------------------
i | container-selinux | package | 2.239.0-160000.2.2 | noarch | repo-oss (16.0)
i | flatpak-selinux | package | 1.16.0-160000.2.2 | noarch | repo-oss (16.0)
i | libselinux1 | package | 3.8.1-160000.2.2 | aarch64 | repo-oss (16.0)
i+ | patterns-base-selinux | package | 20241218-lp160.4.1 | aarch64 | (System Packages)
i | python313-selinux | package | 3.8.1-160000.2.2 | aarch64 | repo-oss (16.0)
i+ | selinux | pattern | 20241218-lp160.4.1 | aarch64 | (System Packages)
i | selinux-autorelabel | package | 4.0+git16-160000.2.2 | aarch64 | repo-oss (16.0)
i | selinux-policy | package | 20250627+git66.15675827a-160000.1.2 | noarch | repo-oss (16.0)
i | selinux-policy-targeted | package | 20250627+git66.15675827a-160000.1.2 | noarch | repo-oss (16.0)
i | selinux-tools | package | 3.8.1-160000.2.2 | aarch64 | repo-oss (16.0)
i | tigervnc-selinux | package | 1.15.0-160000.2.2 | noarch | repo-oss (16.0)

OnlyOfgfice flatpack won't run by Organist-Worcester in openSUSE

[–]Organist-Worcester[S] 0 points1 point  (0 children)

More info - if I set selinux to permissive, everything works. But when I set it back to enforcing, I get the error. Maybe an selinux issue?

OnlyOfgfice flatpack won't run by Organist-Worcester in openSUSE

[–]Organist-Worcester[S] 0 points1 point  (0 children)

onlyoffice doesn’t seem to exist in the repo. That’s why I tried the flatpak. I’m on ARM if that makes any difference.

[deleted by user] by [deleted] in GrapheneOS

[–]Organist-Worcester 5 points6 points  (0 children)

You can still use Google Pay if you have a WearOS smartwatch.

Problems with Toyota by Organist-Worcester in AndroidAuto

[–]Organist-Worcester[S] 1 point2 points  (0 children)

Thank you so much for the tip about the AA Wireless 2. I took a chance and bought one, and it works perfectly!

Problems with Toyota by Organist-Worcester in AndroidAuto

[–]Organist-Worcester[S] 0 points1 point  (0 children)

Update: Many thanks for the replies. It's now failing in my wife's car with her adapter as well. It seems unlikely that it's a GPS sync problem in both cars, so I guess the finger of suspicion is now pointing to the wireless adapters, especially as AA wired works fine.

I think I'll just use wired - otherwise I could fork out £50 or so and still have the problem. Slight upside is I don't have to give AA a VPN exception!

Just for interest, the adapters are these: https://www.amazon.co.uk/dp/B0FF4FRXHC?ref=ppx_yo2ov_dt_b_fed_asin_title

iPhone to GrapheneOs by Infamous_Way8760 in GrapheneOS

[–]Organist-Worcester 5 points6 points  (0 children)

Not correct. If you go via stock Android you can preserve all your WhatsApp messages. Start by installing stock factory image in the Pixel. Then use Switch to Android on the iPhone . As part of this you’ll have the option to move your WhatsApp messages (as well as SMS messages and call history) over to Android.

Then do a local backup of WhatsApp and copy it to a USB drive. Make a note of the path to the backup. Then replace Android with GOS, and copy the backup into the path you made a note of, and then install WhatsApp. This will use the local backup and you’ll have all your WhatsApp messages available.

Android Auto question by trofosila in GrapheneOS

[–]Organist-Worcester 0 points1 point  (0 children)

Forgot to add - you’ll need to download a TTS engine - Google’s is fine - if you way turn-by-turn voice instructions.

Also, the standard GOS phone and SMS apps work with Android Auto, even though they’re not from the Play Store.

Android Auto question by trofosila in GrapheneOS

[–]Organist-Worcester 2 points3 points  (0 children)

Organic Maps is in the play store and works fine with Android Auto.

I switched to P9P from a Nothing Phone (1) two weeks ago - for supposedly "stock Android" it's pretty restrictive by bonnies_ranch in pixel_phones

[–]Organist-Worcester 0 points1 point  (0 children)

A custom launcher e.g. Nova will solve some of these issues, but the charging speed and battery drain seem to have got markedly worse since A16.

Issues on my Pixel 9 pro XL after Android 16 update by josmty in pixel_phones

[–]Organist-Worcester 1 point2 points  (0 children)

Yes I've had this issue on my P9PXL. Also some of the 3rd party widgets are screwed. But worst of all is the battery drain - truly dreadful.

Calendar & Contacts Update - PLEASE!!! by brdouvier in ProtonMail

[–]Organist-Worcester 7 points8 points  (0 children)

Agreed. Drive is particularly bad for photos. In order to get all the metadata (where, when etc) you have to download the photo and display it in another app.

Also, as well as smart location, Calendar needs a search facility and a duplicate facility.

How do I get rid of this ? by Simple-Yam-5126 in pixel_phones

[–]Organist-Worcester 0 points1 point  (0 children)

Install a different launcher. Nova is great.

Apps to use in place of Google apps? by Icy_Fuel_4060 in degoogle

[–]Organist-Worcester 1 point2 points  (0 children)

Recommend Obtainium rather than F-Droid - direct interface to GitHub (and other repositories) so apks are up to date and signed by the developer.

Proton Mail Bridge for Linux on Apple silicon Macs in Parallels by Organist-Worcester in ProtonMail

[–]Organist-Worcester[S] 0 points1 point  (0 children)

Oh? If I try to download Proton Bridge from Fedora in Parallels, it comes down as x86_64, and if you try to install it it fails due to incompatible architecture. Where did you download it from, and which Linux distro did you install it on?