Problems With Extensions After Upgrading

[Notebook823]

So, I bought myself a PineNote like a month ago (my device is a batch 2, I think), and I'm having some issues with the Pinenote Helper extension and Maximized by default extension. 

I recently used a script https://git.sr.ht/~diederik/pinenote-bat...all-fixes/ to upgrade my system (heads up to people, using sudo apt upgrade seems to put the device in a boot loop. I had to re-flash the OS). I don't know if its the script or the upgrades themselves that did this, but the PineNote Helper extension and the Maximized by default extension appear to be completely broken after upgrading. They each give separate warnings inside of the Extension Manager. I tried re-installing the Pinenote Helper extension, but it only added back the display refresh button and nothing else. 

Pinenote Helper error:

An error has occurred in this extension. This could cause issues elsewhere in the system. It is recommended to turn the extension off until the error is resolved. 


Error details: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UknownMethod:
Unknown method SetNoOffScreen

Maximized by default extension:

The installed version of this extension (1.3.1+pn) is incompatible with the current version of GNOME (48.4). The extension has been disabled.

For the Maximized by default extension error, I'm guessing I have to wait until it supports GNOME 48.4 and then upgrade my system again since I probably want the latest system updates possible at the moment. But maybe there's some other solution? 

Anyways, for the Pinenote Helper extension error, I'm at a bit of a dead end. I did find this https://github.com/PNDeb/pinenote-gnome-.../issues/24, in which someone fixes the same issue I'm having by recompiling the PineNote DBUS Service. Apparently a change was made in the Pinenote Helper extension, creating a problem of some kind with the DBUS Service, which is fixed in the latest version of the DBUS Service. Only problem is, I barley know what a DBus is, much less how to recompile one. I've checked some other forum posts, but I can't find any other solutions or other posts talking about this issue. I tend to overlook things, so please let me know if some other post has already fixed this problem.

I'm new to Pine64 and relatively new to Linux as a whole, so excessive amounts of detail would be appreciated so I can research and learn more!

[HippopoStar]

Hi there!
I encountered the same issue, and solved it by updating both pinenote_dbus_service and pinenote-gnome-extension.
In order to follow the steps below, you might need at first to get the m-weigand's Pinenote package repository GPG public key (see this topic).

pinenote_dbus_service

Code:

# Install dependencie(s)
sudo apt-get update && sudo apt-get -y install \
  build-essential \
  curl \
  git \
  jq \
  libdbus-1-dev \
  linux-libc-dev \
  pkg-config
# Install Rust toolchain
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
. "$HOME/.cargo/env"
# Install crate(s)
cargo install cargo-deb
# Clone repository
git clone https://github.com/PNDeb/pinenote_dbus_service.git

# Enter repository directory
pushd pinenote_dbus_service
# Check abbreviated commit hash (83ed018 at the time of writing)
git log -n 1 --oneline
# Build project, create package and install
PINENOTE_DBUS_SERVICE_VERSION=$(
  cargo metadata --no-deps --format-version 1 \
  | jq -r '.["packages"][] | select(.["name"] == "pinenote_dbus_service")["version"]'
)
cargo build
cargo deb
sudo dpkg -i ./target/debian/pinenote-dbus-service_${PINENOTE_DBUS_SERVICE_VERSION}-1_arm64.deb

# Leave repository directory
popd

pinenote-gnome-extension

Code:

# Install dependencie(s)
sudo apt-get update && sudo apt-get -y install \
  git
# Clone repository
git clone https://github.com/PNDeb/pinenote-gnome-extension.git

# Enter repository directory
pushd pinenote-gnome-extension
# Check abbreviated commit hash (f755cbb at the time of writing)
git log -n 1 --oneline
# Run install script
./install.sh
gnome-extensions enable pnhelper@m-weigand.github.com

# Leave repository directory
popd

Now, restart gnome-shell (that can be done by rebooting the device).

Once done, everything should work fine!