Not supported error in GNOME 46

RZHSSNZDH commented 5 months ago

Description

When I try to install the extension I get a not supported error. It occures after I upgraded my GNOME to

Details

Mark with [ ] all that applies:

It happens with any application?

[ ] Yes, it applies to any application.
[ ] No. Only with the following applications:
- VSCode
[ ] It works with the following applications that I have tried:
- Fill in a list with any application that applies

It happens only on one computer?

[* ] I don't know.
[ ] No. I have tried it on more than one computer.

It happens only with some specific gnome configuration?

[x] I don't think that the configuration matters.
[ ] Yes. Only if the following config is set up:
- Fill in a list with any configuration tha applies.

It happens only with some specific extension installed?

[x] I don't think that the installed extensions affect the bug/behavior.
[ ] Yes. Only if the following gnome extension is installed:
- Fill in a list with any extension tha applies.
- Fill in also any detail about the extensions that applies.

Diagnostics

Under what conditions does it happen?

Fill in all information that applies:

Environment

GNOME Shell version: 46
Distro: Arch

Screenshots

Application Details

What is pasted, if applicable

...

Application Version

$ app --version  # ...
1.74.3

Output and Logs

Gnome

Command: journalctl --since=now --follow /usr/bin/gnome-shell

$ journalctl --since=now --follow /usr/bin/gnome-shell
...

Pano Configuration

Command: dconf dump /org/gnome/shell/extensions/pano/

$ dconf dump /org/gnome/shell/extensions/pano/
...
open-links-in-browser=false
play-audio-on-copy=false
send-notification-on-copy=false

Enabled Extensions

Command: dconf read /org/gnome/shell/enabled-extensions | tr ' ' '\n'

$ dconf read /org/gnome/shell/enabled-extensions | tr ' ' '\n'
...
['lockkeys@vaina.lt',
'shamsi-calendar@gnome.scr.ir',
'gsconnect@andyholmes.github.io',
'Resource_Monitor@Ory0n',
'Bluetooth-Battery-Meter@maniacx.github.com',
'ProxySwitcher@flannaghan.com',
'persian-calendar@iamrezamousavi.gmail.com',
'toggle-proxy@wuma',
'runcat@kolesnikov.se',
'pano@elhan.io']

Totto16 commented 5 months ago

This is known and worked on, see #271 I am temped to release a pre-release for gnome support, since the master branch already supports GNOME 46, but not the release on EGO

Tommimon commented 5 months ago

This is known and worked on, see #271 I am temped to release a pre-release for gnome support, since the master branch already supports GNOME 46, but not the release on EGO

Publishing the alpha on EGO removing GNOME 45 compatibility from metadata.json could be an idea, also for the future:

People with GNOME 45 will stay on the stable version by default, unless they decide tu upgrade manually.
People with the latest GNOME will get an alpha quality extension, which is still better then no extension at all.
When new stable Pano is available, it can be published with GNOME 45 compatibility so everyone gets the latest extension eventually.

What do you think of this solution?

RZHSSNZDH commented 3 months ago

This is known and worked on, see #271 I am temped to release a pre-release for gnome support, since the master branch already supports GNOME 46, but not the release on EGO

What's up? Still it is unsopported.

bartv42 commented 2 months ago

What's the status of Gnome 46 support? This version is becoming pretty mainstream now.

ricardosierra commented 3 weeks ago

I need support to gnome 46! How I do it ?

oae / gnome-shell-pano