Update for GNOME 42 #7
Comments
|
I ran into this issue aswell I have managed to mitigate this by changing the following(line 122 to 125) in extension.js: From: this._system_actions._updateOrientationLock = function() {
this._actions.get(SystemActions.LOCK_ORIENTATION_ACTION_ID).available = true;
this.notify('can-lock-orientation');
};To: this._system_actions._updateOrientationLock = function() {
try {
this._actions.get(SystemActions.LOCK_ORIENTATION_ACTION_ID).available = true;
this.notify('can-lock-orientation');
} catch (error) {
log(error)
}
};This is by no means a clean solution but I am out of my depth when it comes to figuring out why I have however been able to test this temporary solution and it seems to work fine using GNOME 42.0 |
|
@shyzus i just gave your suggestion a go and i can confirm it worked for me too. thanks! |
|
@shyzus your solution works and I also love coffee. |
|
@shyzus works for me as well! |
|
@shyzus This worked for me too! Thank you! |
|
@shyzus I confirm this removes the error and activates the extension for me however although the screen auto rotates, it starts in 180 degrees in the wrong orientation (upside down). Currently my solution is to physically invert the laptop and lock the orientation. Its a 2 in 1 Asus BR1100FKA |
It might be possible that your particular device has its sensor installed the other way around (or at least, compared to how the iio module interprets it). You could add your own transformation matrix to correct this, if this is the case. To confirm if this might be the case, try running If that's the case, and you want to try to fix this, you can create a transformation matrix that should correct this. this file has useful information in its header comments that you can use. And while it specifically covers the subject under Xorg (so not applicable if you're using Wayland), this link has useful transformation matrix examples that you can use. |
|
Hi @jibsaramnim I think you are correct; running monitor-sensor returns: When it should be normal Im not familiar enough with xorg to confidently edit the Transformation Matrix but strongly think its related to the lack of support for 2 in 1 displays (laptop & tablet) |
I’m guessing you might have corrected the display orientation post-login in your display settings then, right? There’s a Grub configuration option you can add to correct the display orientation there, which should correct it everywhere (aside from the actual grub screen though), and hopefully includes corrected orientation for your touch/pen as-well. You’d need to know the name of the port through which your display panel is connected internally. I think something like running With that information, you can modify your grub config by adding the following kernel parameters: Replace That hopefully helps resolve the issue for you, but if it persists, and you for whatever reason must keep using Xorg (Wayland tends to handle these kinds of things better), you might still have to go the route of setting up a corrected matrix yourself, but hopefully this won’t be necessary. |
|
FYI, this issue has lasted for over six months and now also affects Gnome 43 (used in Ubuntu 22.10). Any plans for a release @kosmospredanie or do you need new maintainer? |
Please view issue #10 . |
|
Latest release (on the fork at https://github.com/shyzus/gnome-shell-extension-screen-autorotate ) resolves this I believe: https://extensions.gnome.org/extension/5389/screen-rotate/ |
|
Testing this on Fedora 37 + GNOME 43, and can confirm it's fixed on the fork. |
Extension doesn't work in gnome 42.beta. Manually adding 42 to the metadata.json still fails, complaining that
this._actions.get(...)is undefined:(I thought this extension might not be needed in 42 based on gnome gitlab chatter, but still not seeing rotation work on my device)
The text was updated successfully, but these errors were encountered: