Moving windows no longer working lately

[elmerehbi]

I have been using this extension for a whiel however recently moving windows between the main display and an external monitor (in landscape mode) stopped working. It only moves focus to the other monitor.

May that be a bug?

[negesti]

hm, works here. Maybe "Move Focus" is enabled and uses the same key binding?

[elmerehbi]

@negesti You're right and I have thought of this however I didn't change any settings lately. Maybe this is a conflict following some update?

I have changed the key bindings for the focus to Super+Shift+Ctrl+Left/Right.

[negesti]

Thanks for you feedback. I will check the pull requests #136 and #137 maybe something was changed there

[horga83]

Antergos Linux with latest updates, 4 static workspaces and two monitors.

Does not seem to work for all windows. Gnome-terminal works but Firefox doesn't, Chromium doesn't, Evolution seems to. Gedit doesn't move to other monitor, in short it's very inconsistent. Gedit for example changed it's size but did not move to screen 2 as configured, so something happens but not the correct thing. Very interested in debugging this with your help.

[TheRoarkster]

I'm having this problem too. It used to auto-move windows between Workspaces based on per-application settings. After upgrade to Fedora 28 (GNOME 3.28), some applications respect the settings (e.g., gnome terminal) and some don't (e.g., Firefox and Chromium).

I can help debug too.

Also, is there a support/contribution/tip jar? I do not exaggerate when I say that this extension is the reason I use GNOME. I cannot understand how people function on any OS that just opens windows wherever the OS wants. That is insanity.

[negesti]

Just tried with gedit and firefox and both work for me :(

• Please check if the key binding is used somewhere else
• Does the "configuration" work for application "All" ?
• Any error/exceptions if you run gnome-shell --restart & in terminal?

[TheRoarkster]

Really? That's odd. Are you on GNOME 3.28 in Fedora 28?

I just tried it with a fresh install of Ubuntu 18.04, and it seems to retain the Workspace settings (i.e., it works). But one glitch is that the Window Target Workspace number always reverts to 0 -- even if it is set to Workspace 1 or Workspace 2.

I will try the suggestions when I switch over to Fedora later.

[horga83]

Firefos does not work for me. I am on Arch (Antergos) with gnome-shell 3.28.1. What do you mean "key binding", there are no key bindings for this extension. Also what does the configuration "all" mean? Gnome- shell 3.28 doesn't have a --restart option from the command line, did you mean "replace"? George

On Tue, 2018-05-08 at 22:42 -0700, negesti wrote:

Just tried with gedit and firefox and both work for me :(

Please check if the key binding is used somewhere else Does the "configuration" work for application "All" ? Any error/exceptions if you run gnome-shell --restart & in terminal?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5 5493e4bb","name":"GitHub"},"entity":{"external_key":"github/negesti/g nome-shell-extensions-negesti","title":"negesti/gnome-shell- extensions-negesti","subtitle":"GitHub repository","main_image_url":" https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5 d88-11e6-95fc- 7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent .com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed- b52498112777.png","action":{"name":"Open in GitHub","url":"https://gi thub.com/negesti/gnome-shell-extensions- negesti"}},"updates":{"snippets":[{"icon":"PERSON","message":"@negest i in #138: Just tried with gedit and firefox and both work for me :(\r\n\r\n* Please check if the key binding is used somewhere else\r\n* Does the "configuration" work for application "All" ?\r\n* Any error/exceptions if you run gnome-shell --restart \u0026 in terminal?"}],"action":{"name":"View Issue","url":"https://github .com/negesti/gnome-shell-extensions-negesti/issues/138#issuecomment- 387626350"}}} {"@type":"MessageCard","@context":"http://schema.org/extensions","hid eOriginalBody":"false","originator":"37567f93-e2a7-4e2a-ad37- a9160fc62647","title":"Re: [negesti/gnome-shell-extensions-negesti] Moving windows no longer working lately (#138)","sections":[{"text":"","activityTitle":"negesti","activit yImage":"https://cloud.githubusercontent.com/assets/143418/15842166/7 c72db34-2c0b-11e6-9aed- b52498112777.png","activitySubtitle":"@negesti","facts":[]}],"potenti alAction":[{"name":"Add a comment","@type":"ActionCard","inputs":[{"isMultiLine":true,"@type":" TextInput","id":"IssueComment","isRequired":false}],"actions":[{"name ":"Comment","@type":"HttpPOST","target":"https://api.github.com","bod y":"{"commandName":"IssueComment","repositoryFullName":"negest i/gnome-shell-extensions- negesti","issueId":138,"IssueComment":"{{IssueComment.value}}" }"}]},{"name":"Close issue","@type":"HttpPOST","target":"https://api. github.com","body":"{"commandName":"IssueClose","repositoryFullN ame":"negesti/gnome-shell-extensions- negesti","issueId":138}"},{"targets":[{"os":"default","uri":"https ://github.com/negesti/gnome-shell-extensions- negesti/issues/138#issuecomment- 387626350"}],"@type":"OpenUri","name":"View on GitHub"},{"name":"Unsubscribe","@type":"HttpPOST","target":"https://a pi.github.com","body":"{"commandName":"MuteNotification","thread Id":306712596}"}],"themeColor":"26292E"}

[horga83]

I forgot to mention that this only fails with Firefox when I have two monitors running, so multiple monitor support is not working well. If I disable the second monitor it works fine. George

On Tue, 2018-05-08 at 10:40 -0700, TheRoarkster wrote:

I'm having this problem too. It used to auto-move windows between Workspaces based on per-application settings. After upgrade to Fedora 28 (GNOME 3.28), some applications respect the settings (e.g., gnome terminal) and some don't (e.g., Firefox and Chromium).

I can help debug too.

Also, is there a support/contribution/tip jar? I do not exaggerate when I say that this extension is the reason I use GNOME. I cannot understand how people function on any OS that just opens windows wherever the OS wants. That is insanity.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5 5493e4bb","name":"GitHub"},"entity":{"external_key":"github/negesti/g nome-shell-extensions-negesti","title":"negesti/gnome-shell- extensions-negesti","subtitle":"GitHub repository","main_image_url":" https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5 d88-11e6-95fc- 7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent .com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed- b52498112777.png","action":{"name":"Open in GitHub","url":"https://gi thub.com/negesti/gnome-shell-extensions- negesti"}},"updates":{"snippets":[{"icon":"PERSON","message":"@TheRoa rkster in #138: I'm having this problem too. It used to auto-move windows between Workspaces based on per-application settings. After upgrade to Fedora 28 (GNOME 3.28), some applications respect the settings (e.g., gnome terminal) and some don't (e.g., Firefox and Chromium). \r\n\r\nI can help debug too. \r\n\r\nAlso, is there a support/contribution/tip jar? I do not exaggerate when I say that this extension is the reason I use GNOME. I cannot understand how people function on any OS that just opens windows wherever the OS wants. That is insanity. "}],"action":{"name":"View Issue","url":" https://github.com/negesti/gnome-shell-extensions-negesti/issues/138# issuecomment-387483587"}}} {"@type":"MessageCard","@context":"http://schema.org/extensions","hid eOriginalBody":"false","originator":"37567f93-e2a7-4e2a-ad37- a9160fc62647","title":"Re: [negesti/gnome-shell-extensions-negesti] Moving windows no longer working lately (#138)","sections":[{"text":"","activityTitle":"TheRoarkster","ac tivityImage":"https://cloud.githubusercontent.com/assets/143418/15842 166/7c72db34-2c0b-11e6-9aed- b52498112777.png","activitySubtitle":"@TheRoarkster","facts":[]}],"po tentialAction":[{"name":"Add a comment","@type":"ActionCard","inputs":[{"isMultiLine":true,"@type":" TextInput","id":"IssueComment","isRequired":false}],"actions":[{"name ":"Comment","@type":"HttpPOST","target":"https://api.github.com","bod y":"{"commandName":"IssueComment","repositoryFullName":"negest i/gnome-shell-extensions- negesti","issueId":138,"IssueComment":"{{IssueComment.value}}" }"}]},{"name":"Close issue","@type":"HttpPOST","target":"https://api. github.com","body":"{"commandName":"IssueClose","repositoryFullN ame":"negesti/gnome-shell-extensions- negesti","issueId":138}"},{"targets":[{"os":"default","uri":"https ://github.com/negesti/gnome-shell-extensions- negesti/issues/138#issuecomment- 387483587"}],"@type":"OpenUri","name":"View on GitHub"},{"name":"Unsubscribe","@type":"HttpPOST","target":"https://a pi.github.com","body":"{"commandName":"MuteNotification","thread Id":306712596}"}],"themeColor":"26292E"}

[elmerehbi]

I can also confirm that is working for me (Gnome Shell 3.18.5 on Ubuntu Gnome 16.04 ). Maybe it is a conflict with something else? Have you installed another software recently?

[TheRoarkster]

I accessed another Fedora 28 install, one that was an upgrade from Fedora 27, on a different machine. And it works. So it is just on a fresh/clean Fedora 28 install (for me) that it didn't work.

[negesti]

@horga83

• you're right it's --replace
• I mean keyboard binding/shortcuts
• You can configure position and size for an individual application or just configure different position and sizes for "All"

There was a bug when trying to move or resize a already maximized window. Does it work with firefox, if the current window is not maximized?

I can create a Fedora 28 VM and test the extension there. But that will take some time.

Please check if your Fedora 28 installation is running wayland. The extension does not work properly with wayland

[negesti]

@TheRoarkster "Move to workspace" is based on the "official" gnome extension "Auto-Move-Window". But the feature was added about 2 years ago e.g. maybe a fresh "copy" of the auto-move-window would resolve the issue

[negesti]

Just tried with a fresh installation of fedora 28 inside a vm.

1. Using wayland I was not able to start gnome-shell at all
2. Using "Gnome Xorg" works
3. Installed and successfully tested github release

Unfortunately i'm not able to add a second monitor to my vm :(

[negesti]

Any feedback? Can i close the ticket?

[horga83]

Well moving Firefox still does not work with multiple monitors.

On Thu, 2018-06-21 at 08:57 -0700, negesti wrote:

Any feedback? Can i close the ticket?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

{"@context":"http://schema.org","@type":"EmailMessage","potentialActi on":{"@type":"ViewAction","target":"https://github.com/negesti/gnome- shell-extensions-negesti/issues/138#issuecomment- 399154118","url":"https://github.com/negesti/gnome-shell-extensions- negesti/issues/138#issuecomment-399154118","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}} {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5 5493e4bb","name":"GitHub"},"entity":{"external_key":"github/negesti/g nome-shell-extensions-negesti","title":"negesti/gnome-shell- extensions-negesti","subtitle":"GitHub repository","main_image_url":" https://assets-cdn.github.com/images/email/message_cards/header.png", "avatar_image_url":"https://assets- cdn.github.com/images/email/message_cards/avatar.png","action":{"name ":"Open in GitHub","url":"https://github.com/negesti/gnome-shell-exte nsions- negesti"}},"updates":{"snippets":[{"icon":"PERSON","message":"@negest i in #138: Any feedback? Can i close the ticket?"}],"action":{"name":"View Issue","url":"https://github.com/ne gesti/gnome-shell-extensions-negesti/issues/138#issuecomment- 399154118"}}} { "@type": "MessageCard", "@context": "http://schema.org/extensions", "hideOriginalBody": "false", "originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB", "title": "Re: [negesti/gnome-shell-extensions-negesti] Moving windows no longer working lately (#138)", "sections": [ { "text": "", "activityTitle": "negesti", "activityImage": "https://assets-cdn.github.com/images/email/message_ cards/avatar.png", "activitySubtitle": "@negesti", "facts": [

] } ], "potentialAction": [ { "name": "Add a comment", "@type": "ActionCard", "inputs": [ { "isMultiLine": true, "@type": "TextInput", "id": "IssueComment", "isRequired": false } ], "actions": [ { "name": "Comment", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "negesti/gnome-shell- extensions-negesti",\n"issueId": 138,\n"IssueComment": "{{IssueComment.value}}"\n}" } ] }, { "name": "Close issue", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "negesti/gnome-shell-extensions-negesti",\n"issueId": 138\n}" }, { "targets": [ { "os": "default", "uri": "https://github.com/negesti/gnome-shell-extensions-negesti/iss ues/138#issuecomment-399154118" } ], "@type": "OpenUri", "name": "View on GitHub" }, { "name": "Unsubscribe", "@type": "HttpPOST", "target": "https://api.github.com", "body": "{\n"commandName": "MuteNotification",\n"threadId": 306712596\n}" } ], "themeColor": "26292E" }

[negesti]

@horga83 that's strange. just tried again and can move firefox between screens without problems :(

• using put windows shift + super + left/right to move to other screens
• using gnome-shells shift + ctrl + left/right to move to other screens
• add a configuratoin to put windows to move it between screens (both maximized and 'smaller')
• add a config to put windows and auto-move it on creation

You are using fedora 28 with shell 3.28? Any error when running gnome-shell --replace & from bash? Are you using the latest version of the extension? (both github and extension.gnome.org are up to date)

[TheRoarkster]

Sorry for the gap in posting. This is still an issue. I appreciate the troubleshooting.

@negesti, are you saying that the "Auto-Move-Windows" extension is a required dependency? I just installed it (wasn't before) and will report back.

Also, this is the output from gnome-shell --replace & (note: it is long):

current session already has an ibus-daemon.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.334: Some code accessed the property 'DBusMenu' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.335: Some code accessed the property 'WORKAROUND_RELOAD_TYPE_REGISTER' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.337: Some code accessed the property 'StatusNotifierWatcher' on the module 'statusNotifierWatcher'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.337: Some code accessed the property 'StatusNotifierWatcher' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.338: Some code accessed the property 'traverseBusNames' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Impatience-Message: 08:21:48.350: [impatience] enabled
Impatience-Message: 08:21:48.350: [impatience] enabled
Impatience-Message: 08:21:48.351: [impatience] setting new speed: 0.75
Impatience-Message: 08:21:48.352: [impatience] setting new speed: 0.75

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.354: Some code accessed the property 'ScrollablePopupMenu' on the module 'scrollablePopupMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.355: Some code accessed the property 'PopupExtensionItem' on the module 'popupExtensionItem'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.412: Some code accessed the property 'MAX_THUMBNAIL_SCALE' on the module 'workspaceThumbnail'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.425: Some code accessed the property 'SoundDeviceChooserBase' on the module 'base'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.428: Some code accessed the property 'SETTINGS_SCHEMA' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Gjs-Message: 08:21:48.428: JS WARNING: [/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/convenience.js 200]: reference to undefined property Symbol.toPrimitive

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.432: Some code accessed the property 'SHOW_INPUT_SLIDER' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.492: JS ERROR: Could not load extension org.gnome.desktop-icons-reworked-master: Error: uuid "org.gnome-shell.desktop-icons" from metadata.json does not match directory name "org.gnome.desktop-icons-reworked-master"
createExtensionObject@resource:///org/gnome/shell/misc/extensionUtils.js:134:15
_loadExtension@resource:///org/gnome/shell/misc/extensionUtils.js:179:25
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
scanExtensions/<@resource:///org/gnome/shell/misc/extensionUtils.js:190:13
collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
scanExtensions@resource:///org/gnome/shell/misc/extensionUtils.js:189:9
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:320:5
enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:328:9
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:359:9
init@resource:///org/gnome/shell/ui/extensionSystem.js:367:5
_initializeUI@resource:///org/gnome/shell/ui/main.js:229:5
start@resource:///org/gnome/shell/ui/main.js:133:5
@<main>:1:31


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.504: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.520: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.566: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.586: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.601: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.619: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1


(gnome-shell:21024): Gjs-WARNING **: 08:21:48.645: JS ERROR: ReferenceError: Utils is not defined
MoveWorkspace.prototype._findAndMove@/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/moveWorkspace.js:165:1

Gjs-Message: 08:21:48.650: JS WARNING: [/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/extension.js 761]: reference to undefined property "screen"
[mbwd@imac-fed28 ~] $ 
(gnome-shell:21024): Gjs-WARNING **: 08:21:48.927: Some code accessed the property 'introspectBusObject' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.938: Some code accessed the property 'getUniqueBusNameSync' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.939: Some code accessed the property 'Logger' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
KStatusNotifierItem/AppIndicator Support-Message: 08:21:48.940: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.103/StatusNotifierItem

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.940: Some code accessed the property 'AppIndicator' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.940: Some code accessed the property 'StatusNotifierItem' on the module 'interfaces'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.941: Some code accessed the property 'connectSmart' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.942: Some code accessed the property 'IndicatorStatusIcon' on the module 'indicatorStatusIcon'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.944: Some code accessed the property 'IconActor' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:48.945: Some code accessed the property 'IconCache' on the module 'iconCache'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
KStatusNotifierItem/AppIndicator Support-Message: 08:21:48.948: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.82/StatusNotifierItem
KStatusNotifierItem/AppIndicator Support-Message: 08:21:48.955: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.81/org/ayatana/NotificationItem/syncthing_gtk

(gnome-shell:21024): Bluetooth-WARNING **: 08:21:48.992: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.006: Some code accessed the property 'dbusNodeImplementsInterfaces' on the module 'util'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.034: Some code accessed the property 'SNIStatus' on the module 'appIndicator'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.036: Some code accessed the property 'Client' on the module 'dbusMenu'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
GNOME Shell-Message: 08:21:49.164: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.668: Some code accessed the property 'HIDE_ON_SINGLE_DEVICE' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.668: Some code accessed the property 'SHOW_PROFILES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.668: Some code accessed the property 'ICON_THEME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.668: Some code accessed the property 'HIDE_MENU_ICONS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.668: Some code accessed the property 'PORT_SETTINGS' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.668: Some code accessed the property 'SHOW_OUTPUT_DEVICES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Sound Input & Output Device Chooser-Message: 08:21:49.669: Max Id:8

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.671: Some code accessed the property 'ICON_THEME_COLORED' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.671: Some code accessed the property 'ICON_THEME_MONOCHROME' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Sound Input & Output Device Chooser-Message: 08:21:49.691: Getting profile form stream id hdmi-output-0
Sound Input & Output Device Chooser-Message: 08:21:49.692: HDMI / DisplayPort
(Turks HDMI Audio [Radeon HD 6500/6600 / 6700M Series])
Sound Input & Output Device Chooser-Message: 08:21:49.693: output:hdmi-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.694: output:hdmi-surround
Sound Input & Output Device Chooser-Message: 08:21:49.694: output:hdmi-surround71
Sound Input & Output Device Chooser-Message: 08:21:49.695: Added: 1:HDMI / DisplayPort:hdmi-output-0
Gjs-Message: 08:21:49.695: JS WARNING: [/home/mbwd/.local/share/gnome-shell/extensions/[email protected]/base.js 167]: reference to undefined property 1
Sound Input & Output Device Chooser-Message: 08:21:49.720: Getting profile from cards iec958-stereo-output for card id 0
Sound Input & Output Device Chooser-Message: 08:21:49.721: Getting profile from cards iec958-stereo-output for card id 1
Sound Input & Output Device Chooser-Message: 08:21:49.722: Digital Output (S/PDIF)
(Built-in Audio)
Sound Input & Output Device Chooser-Message: 08:21:49.723: output:iec958-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.724: Added: 2:Digital Output (S/PDIF):iec958-stereo-output
Sound Input & Output Device Chooser-Message: 08:21:49.728: Getting profile form stream id analog-output-headphones
Sound Input & Output Device Chooser-Message: 08:21:49.729: Headphones
(Built-in Audio)
Sound Input & Output Device Chooser-Message: 08:21:49.730: output:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.731: Added: 3:Headphones:analog-output-headphones
Sound Input & Output Device Chooser-Message: 08:21:49.733: Removed: 3
Sound Input & Output Device Chooser-Message: 08:21:49.735: Getting profile form stream id analog-output-speaker
Sound Input & Output Device Chooser-Message: 08:21:49.736: Speakers
(Built-in Audio)
Sound Input & Output Device Chooser-Message: 08:21:49.737: output:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.737: output:analog-surround-21
Sound Input & Output Device Chooser-Message: 08:21:49.738: output:analog-surround-40
Sound Input & Output Device Chooser-Message: 08:21:49.739: Added: 4:Speakers:analog-output-speaker
Sound Input & Output Device Chooser-Message: 08:21:49.743: Activated: 4

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.744: Some code accessed the property 'SHOW_INPUT_DEVICES' on the module 'prefs'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway.
Sound Input & Output Device Chooser-Message: 08:21:49.745: Max Id:9
Sound Input & Output Device Chooser-Message: 08:21:49.762: Getting profile from cards iec958-stereo-input for card id 0
Sound Input & Output Device Chooser-Message: 08:21:49.763: Getting profile from cards iec958-stereo-input for card id 1
Sound Input & Output Device Chooser-Message: 08:21:49.763: Digital Input (S/PDIF)
(Built-in Audio)
Sound Input & Output Device Chooser-Message: 08:21:49.764: input:iec958-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.765: input:iec958-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.766: input:iec958-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.767: input:iec958-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.767: input:iec958-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.768: Added: 5:Digital Input (S/PDIF):iec958-stereo-input
Sound Input & Output Device Chooser-Message: 08:21:49.771: Getting profile form stream id analog-input-linein
Sound Input & Output Device Chooser-Message: 08:21:49.772: Line In
(Built-in Audio)
Sound Input & Output Device Chooser-Message: 08:21:49.772: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.773: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.773: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.774: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.774: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.775: Added: 6:Line In:analog-input-linein
Sound Input & Output Device Chooser-Message: 08:21:49.776: Removed: 6
Sound Input & Output Device Chooser-Message: 08:21:49.779: Getting profile form stream id analog-input-mic
Sound Input & Output Device Chooser-Message: 08:21:49.779: Microphone
(Built-in Audio)
Sound Input & Output Device Chooser-Message: 08:21:49.780: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.780: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.781: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.781: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.782: input:analog-stereo
Sound Input & Output Device Chooser-Message: 08:21:49.782: Added: 7:Microphone:analog-input-mic
Sound Input & Output Device Chooser-Message: 08:21:49.784: Activated: 7
Gjs-Message: 08:21:49.801: JS WARNING: [resource:///org/gnome/shell/ui/keyboard.js 546]: reference to undefined property "_rect"

(gnome-shell:21024): Gjs-WARNING **: 08:21:49.801: JS ERROR: Exception in callback for signal: position-changed: TypeError: this._rect is undefined
getCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:546:22
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_onFocusPositionChanged@resource:///org/gnome/shell/ui/keyboard.js:611:20
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
_emit@resource:///org/gnome/gjs/modules/signals.js:128:27
_setCurrentWindow/this._currentWindowPositionId<@resource:///org/gnome/shell/ui/keyboard.js:528:21

Window manager warning: Overwriting existing binding of keysym ff53 with keysym ff53 (keycode 72).
Window manager warning: Overwriting existing binding of keysym ff53 with keysym ff53 (keycode 72).

[TheRoarkster]

No joy after installing "Auto-Move-Windows." I wanted to show you an oddity (I think) that presents itself in the settings (Put Windows>Applications>app) on each "Put Windows" app that I try to auto-move to the second workspace. Instead of showing the proper workspace (i.e., 2), it shows a 0. Not sure if that helps.

[negesti]

The move to workspace feature is based on the official "Auto-Move-Windows" extension. I will try to debug is further i find have some time off

[TheRoarkster]

Sounds good. FWIW, the official "Auto-Move-Windows" itself does work. I just tried it with an app that doesn't work in "Put Windows."

[horga83]

On Thu, 2018-10-25 at 15:57 +0000, TheRoarkster wrote:

Sounds good. FWIW, the official "Auto-Move-Windows" itself does work. I just tried it with an app that doesn't work in "Put Windows." — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Actually it doesn't work if you have multiple monitors. For example Auto-Move-Windows will work fine on a single monitor, however, it will only work with certain apps on dual monitors. Evolution seems to work fine, Firefox does not, it always opens on the current workspace.

This has been a problem for a long time.

Cheers George

[TheRoarkster]

@horga83, I only use one monitor, so I can't replicate the Auto-Move-Windows problem for two. But I can confirm that Put Windows is not able to consistently open applications in the designated workplace on one monitor. For some reason, the number set for the workspace always reverts to 0.