Skip to content
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.

Not working on 3.34 (3.33.9*) (Ubuntu 19.10 developmental branch) #7

Open
fcole90 opened this issue Aug 30, 2019 · 5 comments
Open
Assignees

Comments

@fcole90
Copy link

fcole90 commented Aug 30, 2019

Since the update to 3.33.9* the screenshot location is no longer respected. Whatever the path, the screenshot gets always saved under $USER/Pictures.

I can see this in the logs:

JS WARNING: [/home/fabio/.local/share/gnome-shell/extensions/[email protected]/keybinder.js 125]: reference to undefined property "MESSAGE_TRAY"

Let me know how I can help.

@kiyui
Copy link
Owner

kiyui commented Sep 2, 2019

Looks like a breaking change in 3.33 that may affect many extensions 😄 I'll look into setting up a 19.10 VM when I have free time.

@kiyui kiyui self-assigned this Sep 2, 2019
@szpak
Copy link

szpak commented Jan 2, 2020

I've just upgraded to gnome-shell-3.34.2-1.fc31.x86_64 in Fedora 31 and also bumped into that problem.

@eode
Copy link

eode commented Jan 13, 2020

Ditto..

@kiyui
Copy link
Owner

kiyui commented Jan 14, 2020

The issue is with the vendored keybinder.js, if anyone has time to look into it. I do not have any internet outside work so it's not easy to work on this issue. Here's a workaround which basically does what the extension does:

Disable the default screenshot keyboard shortcut:
Disabling the default keyboard shortcut in GNOME settings

Add a new shortcut with the Print key:
Creating a new shortcut to gnome-screenshot assigned to the Print key

Change the gnome-screenshots save directory with dconf Editor or using the cli:

gsettings set org.gnome.gnome-screenshot auto-save-directory /path/to/screenshots

Using dconf Editor to change the screenshot location

@kiyui
Copy link
Owner

kiyui commented Oct 10, 2020

There was an API change between 3.34 and 3.36 that renders #11 broken on those versions before. I'm open to PRs if anyone still wants to add in support for older versions that I do not personally use.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants