search

projecthamster / hamster-shell-extension

Shell extension for hamster
http://projecthamster.org
GNU General Public License v3.0
217 stars 92 forks source link

Error on ubuntu 19.10 #326

Open marcbria opened 4 years ago

marcbria commented 4 years ago

Hi, Looks like is failing on ubuntu 19.10 that packages gnome-extensions 3.34.1.

How to reproduce the error: 1) Install a clean ubuntu 19.10 2) Install hamster (snap version) 3) Go to the "Central Extension Repository" 4) Click on the slider to enable the extension. 5) See the error.

Error

SyntaxError: redeclaration of let renderer

Stack trace:
  get prefsModule@resource:///org/gnome/shell/extensionPrefs/main.js:675:13
  _showPrefs@resource:///org/gnome/shell/extensionPrefs/main.js:57:13
  _extensionsLoaded@resource:///org/gnome/shell/extensionPrefs/main.js:320:13
  _scanExtensions/<@resource:///org/gnome/shell/extensionPrefs/main.js:298:13
  asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:132:13
  main@resource:///org/gnome/shell/extensionPrefs/main.js:707:5
  @<main>:1:43
mwilck commented 4 years ago

Please attach the full "journalctl --user" output. Which version of the extension have you used? You need to get the sources from #316 or #323, and install the extension locally.

marcbria commented 4 years ago

Hi mwilck,

I didn't know I need to install it from sources... so I though enabling it from Central Extension Repository was enoght, so I installed the version published by elbenfreund in, that is a 3.20: https://extensions.gnome.org/extension/425/project-hamster-extension

Here it is the "jounralctl --user" output from the last hour (the full one started on month ago and is hudge):

mar 18 12:28:54 lightop telegram-desktop_telegram-desktop.desktop[3292]: QTextCursor::setPosition: Position '-1' out of range
mar 18 12:28:57 lightop telegram-desktop_telegram-desktop.desktop[3292]: [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f09f0001ac0] Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
mar 18 12:40:19 lightop dbus-daemon[3074]: [session uid=1000 pid=3074] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.396' (uid=1000 pid=30858 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/" label="unconfined")
mar 18 12:40:19 lightop dbus-daemon[3074]: [session uid=1000 pid=3074] Successfully activated service 'org.gnome.ChromeGnomeShell'
mar 18 12:40:29 lightop gnome-software[4253]: State change on user/*/*/shell-extension/hamster_projecthamster.wordpress.com/* from installed to available is not OK
mar 18 12:40:29 lightop gnome-software[4253]: hamster_projecthamster.wordpress.com has error: SyntaxError: redeclaration of let fact
mar 18 12:41:40 lightop gnome-shell[3292]: Archive:  /tmp/4O7ZH0.shell-extension.zip
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/schemas/gschemas.compiled
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/images/hamster-tracking-symbolic.svg
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/cs/
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/es/
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/cs/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/build.sh
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/pl/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/prefs.js
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/ru/LC_MESSAGES/
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/stuff.js
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/de/
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/es/LC_MESSAGES/
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/ru/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/nl/
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/fr/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/pl/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/schemas/org.gnome.shell.extensions.project-hamster.gschema.xml
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/stylesheet.css
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/de/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:    creating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/pt-BR/LC_MESSAGES/
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/pt-BR/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/nl/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/ru/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/extension.js
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/es/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/CHANGES
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/pt-BR/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/convenience.js
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/README.md
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/de/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/nl/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/cs/LC_MESSAGES/hamster-shell-extension.mo
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/fr/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/images/hamster-idle-symbolic.svg
mar 18 12:41:40 lightop gnome-shell[3292]:   inflating: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/locale/es/LC_MESSAGES/hamster-shell-extension.po
mar 18 12:41:40 lightop gnome-shell[3292]:  extracting: /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/metadata.json
mar 18 12:41:40 lightop gnome-shell[3292]: JS ERROR: Extension hamster@projecthamster.wordpress.com: SyntaxError: redeclaration of let fact @ /home/marc/.local/share/gnome-shell/extensions/hamster@projecthamster.wordpress.com/extension.js:366
mar 18 12:41:40 lightop gnome-software[4253]: State change on user/*/*/shell-extension/hamster_projecthamster.wordpress.com/* from available to installed is not OK
mar 18 12:41:40 lightop gnome-software[4253]: hamster_projecthamster.wordpress.com has error: SyntaxError: redeclaration of let fact
mar 18 12:45:50 lightop dbus-daemon[3074]: [session uid=1000 pid=3074] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.102' (uid=1000 pid=3546 comm="/usr/lib/tracker/tracker-miner-fs " label="unconfined")
mar 18 12:45:50 lightop systemd[3051]: Starting Tracker metadata database store and lookup manager...

I will try with sources.

Thanks for your time, m.

mwilck commented 4 years ago

so I though enabling it from Central Extension Repository was enoght, so I installed the version published by elbenfreund in, that is a 3.20:

No, it's not enough.

Grab my GNOME 3.36 branch, unpack it, and follow the instructions in README.rst under "Manual Installation For Testing and Development" (no need to run git clone or git checkout any more if you grabbed the zip file though).

matthijskooijman commented 4 years ago

For clarity: The plan is to make the extension on extensions.gnome.org again up-to-date and sufficient, but we're starting up development again after a long hiatus, so we're not there yet. In the meanwhile, testing using local installs is helpful!

mwilck commented 4 years ago

@matthijskooijman, I wonder if we could add a sticky note to our repo telling users that it makes no sense to test the stuff from e.g.o with late GNOME versions currently and that we're actively working on it, and providing instructions for installing / testing the test releases code from the PRs waiting to be merged.

matthijskooijman commented 4 years ago

I think you can mark issues as sticky (or pin them, dunno how it's called), that might be useful?

mwilck commented 4 years ago

I just created a sticky note (#327), please check it out.

marcbria commented 4 years ago

Thanks for the explanation. Hamster is one of my favorite programs ever and I love to help but I don't know python and gnome-shell and all this sounds like vudu for me... so please, be patien. :-)

Despite that, I can follow instructions (the README file is very clear). But during the process I got errors:

$ make dist
mkdir -p build
cp -R extension/* build
cp -R data/* build
glib-compile-schemas build/schemas
find build -name \*.po -execdir msgfmt hamster-shell-extension.po -o hamster-shell-extension.mo \;
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
find: ‘msgfmt’: No existe el archivo o el directorio
mkdir -p dist;
cd build; zip -rq ../dist/contact@projecthamster.org.zip ./* || true
cd build; tar -czf ../dist/contact@projecthamster.org.tar.gz *
total 112
-rw-r--r-- 1 marc marc 46403 mar 19 10:27 contact@projecthamster.org.tar.gz
-rw-r--r-- 1 marc marc 65436 mar 19 10:27 contact@projecthamster.org.zip

As said, I don't know python but some missing chains don't look like a real issue so I follow with the installation process but I don't see any new extension in my extensions.gnome.org/local or with Tweak Tool.

I reboot and the problem is still the same. After that I tried with 3.34 (that as far as I see it the version packaged with ubuntu 19.10 and the problem persists.

Then I tried pulling the code from github (dev branch) and I got a different error during make dist (pulling issues with a dependent repo).

mwilck commented 4 years ago

Please help us understand your issue better by using English error messages. Run `export LC_MESSAGES=C" before running any other commands.

Don't worry about python, the respective parts of the README are misleading, unfortunately. The python-related setup steps are only necessary for setting up hamster itself, not for the GNOME extension, and I believe you already have hamster running.

It seems you're missing the "msgfmt" tool. In my distro (SUSE), it's in the gettext-runtime package. Look for packages named `gettext-' and install them.

marcbria commented 4 years ago

Please help us understand your issue better by using English error messages. Run `export LC_MESSAGES=C" before running any other commands.

Sure, sorry for this:

make dist
cp -R extension/* build
cp -R data/* build
glib-compile-schemas build/schemas
find build -name \*.po -execdir msgfmt hamster-shell-extension.po -o hamster-shell-extension.mo \;
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
find: ‘msgfmt’: No such file or directory
mkdir -p dist;
cd build; zip -rq ../dist/contact@projecthamster.org.zip ./* || true
cd build; tar -czf ../dist/contact@projecthamster.org.tar.gz *
total 112
-rw-r--r-- 1 marc marc 46418 mar 19 11:05 contact@projecthamster.org.tar.gz
-rw-r--r-- 1 marc marc 65436 mar 19 11:05 contact@projecthamster.org.zip

Adding "gettext" package was enough to fix the error with langs: $ sudo apt install gettext

Maybe would be nice to mention this in the README.

About the issue, the extension is still not shown in gnome-extensions-local or in tweak tools.

imagen

Cheers, m.

mwilck commented 4 years ago

You need to create a directory contact@projecthamster.org under $HOME/.local/gnome-shell/extensions and unpack the generated zip (or tar.gz, you choose) there. Only then will the extension be visible.

Please provide journalctl --user output.

marcbria commented 4 years ago

I did it (3 times now :-)) but it never shows...

I follow your README instructions step by step:

    # Build
    make dist
    # Remove any old installation
    rm -rf ~/.local/share/gnome-shell/extensions/contact@projecthamster.org
    # Create directory
    mkdir -p ~/.local/share/gnome-shell/extensions/contact@projecthamster.org
    # Unpack build
    tar xfz dist/contact@projecthamster.org.tar.gz -C ~/.local/share/gnome-shell/extensions/contact@projecthamster.org

Here you have teh journalctl output of the last hour:

(.venv) marc@lightop:~/workspace/hamster-shell-extension-GNOME-3.34$ journalctl --user | grep "mar 19 11"
mar 19 11:03:49 lightop gnome-keyring-daemon[3255]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
mar 19 11:04:37 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 11:10:46 lightop pkexec[10889]: pam_unix(polkit-1:session): session opened for user root by (uid=1000)
mar 19 11:11:16 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.248' (uid=1000 pid=10947 comm="/usr/bin/python3 /usr/bin/chrome
-gnome-shell /usr/" label="unconfined")
mar 19 11:11:16 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.gnome.ChromeGnomeShell'
mar 19 11:11:45 lightop gnome-shell[3479]: Failed to store clipboard: Format image/tiff not supported
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b2844a0 StButton.app-well-app ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686584e680 StWidget ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b2844a0 StButton.app-well-app ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686584e680 StWidget ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x556867883b30 StWidget.app-well-app-running-dot] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b2844a0 StButton.app-well-app ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686584e680 StWidget ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686528e980 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b2844a0 StButton.app-well-app ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686584e680 StWidget ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686528e980 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686534b560 StBoxLayout] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b2844a0 StButton.app-well-app ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686584e680 StWidget ("6")] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686528e980 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686534b560 StBoxLayout] which is not in the stage.
mar 19 11:13:03 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b0121b0 StBin] which is not in the stage.
mar 19 11:26:11 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='io.snapcraft.Launcher' requested by ':1.253' (uid=1000 pid=11232 comm="snapctl user-open http://guifi.net/node/108295 " label="snap.telegram-desktop.telegram-desktop (enforce)")
mar 19 11:26:12 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'io.snapcraft.Launcher'
mar 19 11:26:12 lightop io.snapcraft.Launcher[3262]: userd.go:98: Starting snap userd
mar 19 11:31:25 lightop telegram-desktop_telegram-desktop.desktop[3479]:   OpenType support missing for "DAOpenSansRegular", script 12
mar 19 11:31:25 lightop telegram-desktop_telegram-desktop.desktop[3479]: [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fd950005400] Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
mar 19 11:34:01 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 11:40:38 lightop telegram-desktop_telegram-desktop.desktop[3479]: QTextCursor::setPosition: Position '-1' out of range
mar 19 11:44:23 lightop telegram-desktop_telegram-desktop.desktop[3479]: QTextCursor::setPosition: Position '-1' out of range
mar 19 11:47:00 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 11:50:32 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 11:50:32 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 11:50:32 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
marcbria commented 4 years ago

I forget to mention that I installed hamster app/service from snap (just in case it could be related).

mwilck commented 4 years ago

Have you restarted the GNOME shell? You have to log in / out, or restart (Alt-F2, then type "r" into the popup window). Restart doesn't work under wayland.

marcbria commented 4 years ago

Thanks for the tip. Alt-F2 + r worked like a charm.

Now the extension is shown in the list but when enabled, does not appear in the panel.

Here you have the journalctl output:

journalctl --user | grep "mar 19 12"
mar 19 12:00:25 lightop telegram-desktop_telegram-desktop.desktop[3479]: [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fd934005c00] Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
mar 19 12:00:28 lightop telegram-desktop_telegram-desktop.desktop[3479]: [mov,mp4,m4a,3gp,3g2,mj2 @ 0x7fd93401e2c0] Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
mar 19 12:00:40 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.102' (uid=1000 pid=3714 comm="/usr/lib/tracker/tracker-miner-fs " label="unconfined")
mar 19 12:00:40 lightop systemd[3239]: Starting Tracker metadata database store and lookup manager...
mar 19 12:00:40 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.Tracker1'
mar 19 12:00:40 lightop systemd[3239]: Started Tracker metadata database store and lookup manager.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568670698b0 StButton.app-well-app ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568676f5a50 StWidget ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568670698b0 StButton.app-well-app ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568676f5a50 StWidget ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x556864c2bc60 StWidget.app-well-app-running-dot] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568670698b0 StButton.app-well-app ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568676f5a50 StWidget ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568672a8e10 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568670698b0 StButton.app-well-app ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568676f5a50 StWidget ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568672a8e10 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b121a70 StBoxLayout] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568670698b0 StButton.app-well-app ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568676f5a50 StWidget ("1")] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x5568672a8e10 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55686b121a70 StBoxLayout] which is not in the stage.
mar 19 12:01:00 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x556866a4a750 StBin] which is not in the stage.
mar 19 12:01:10 lightop tracker-store[12744]: OK
mar 19 12:01:10 lightop systemd[3239]: tracker-store.service: Succeeded.
mar 19 12:01:58 lightop gnome-shell[3479]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4800007
mar 19 12:02:04 lightop gvfsd[3370]: got no contact to IPC$
mar 19 12:09:47 lightop org.kde.kdeconnect.daemon.desktop[3730]: QObject::connect: No such slot LanLinkProvider::connectError()
mar 19 12:09:47 lightop org.kde.kdeconnect.daemon.desktop[3730]: QObject::disconnect: No such slot LanLinkProvider::connectError()
mar 19 12:09:47 lightop org.kde.kdeconnect.daemon.desktop[3730]: kdeconnect.core: TCP connection done (i'm the existing device)
mar 19 12:09:47 lightop org.kde.kdeconnect.daemon.desktop[3730]: kdeconnect.core: Starting server ssl (I'm the client TCP socket)
mar 19 12:09:47 lightop org.kde.kdeconnect.daemon.desktop[3730]: kdeconnect.core: Socket successfully established an SSL connection
mar 19 12:09:47 lightop org.kde.kdeconnect.daemon.desktop[3730]: kdeconnect.core: It is a new device "xiaomi"
mar 19 12:13:07 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.102' (uid=1000 pid=3714 comm="/usr/lib/tracker/tracker-miner-fs " label="unconfined")
mar 19 12:13:07 lightop systemd[3239]: Starting Tracker metadata database store and lookup manager...
mar 19 12:13:07 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.Tracker1'
mar 19 12:13:07 lightop systemd[3239]: Started Tracker metadata database store and lookup manager.
mar 19 12:13:48 lightop tracker-store[13027]: OK
mar 19 12:13:48 lightop systemd[3239]: tracker-store.service: Succeeded.
mar 19 12:14:08 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 12:14:25 lightop gnome-shell[3479]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
mar 19 12:14:25 lightop gnome-shell[3479]: Object Meta.BackgroundActor (0x55686596b260), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
mar 19 12:14:25 lightop gnome-shell[3479]: == Stack trace for context 0x5568649d4350 ==
mar 19 12:14:25 lightop gnome-shell[3479]: #0   7ffe6a1b6450 b   resource:///org/gnome/gjs/modules/overrides/GObject.js:508 (7fa0b1dad8b0 @ 25)
mar 19 12:14:25 lightop gnome-shell[3479]: #1   55686add7cf0 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:210 (7fa095a7f940 @ 75)
mar 19 12:14:25 lightop gnome-shell[3479]: #2   55686add7c78 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:115 (7fa095a7f550 @ 12)
mar 19 12:14:25 lightop gnome-shell[3479]: #3   55686add7c00 i   resource:///org/gnome/shell/ui/main.js:224 (7fa0b1dcf940 @ 12)
mar 19 12:14:25 lightop gnome-shell[3479]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
mar 19 12:14:25 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:14:25 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:14:25 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:14:25 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:14:25 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:14:25 lightop systemd[3239]: Stopped target GNOME XSettings.
mar 19 12:14:25 lightop systemd[3239]: Stopping GNOME XSettings...
mar 19 12:14:25 lightop systemd[3239]: Stopped target GNOME session X11 services.
mar 19 12:14:25 lightop systemd[3239]: Stopped target GNOME X11 Session (session: ubuntu).
mar 19 12:14:25 lightop systemd[3239]: Stopped target GNOME X11 Session.
mar 19 12:14:25 lightop systemd[3239]: gsd-xsettings.service: Succeeded.
mar 19 12:14:25 lightop systemd[3239]: Stopped GNOME XSettings.
mar 19 12:14:25 lightop ibus-daemon[3574]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
mar 19 12:14:25 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.freedesktop.portal.IBus' requested by ':1.301' (uid=1000 pid=13059 comm="ibus-daemon --panel disable -r " label="unconfined")
mar 19 12:14:25 lightop firefox[7249]: Create input context failed: La conexión está cerrada.
mar 19 12:14:25 lightop thunderbird[4266]: Create input context failed: La conexión está cerrada.
mar 19 12:14:25 lightop thunderbird[4266]: Create input context failed: Connection is closed..
mar 19 12:14:25 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.portal.IBus'
mar 19 12:14:25 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): EDID vendor "SHP", prod id 5146
mar 19 12:14:25 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): Printing DDC gathered Modelines:
mar 19 12:14:25 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)
mar 19 12:14:25 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): Modeline "1920x1080"x0.0  110.92  1920 1968 2000 2080  1080 1083 1088 1111 -hsync -vsync (53.3 kHz e)
mar 19 12:14:25 lightop gsd-media-keys[3625]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
mar 19 12:14:26 lightop gnome-shell[3479]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mar 19 12:14:26 lightop gnome-shell[3479]: Will monitor session 3
mar 19 12:14:26 lightop gsd-media-keys[3625]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
mar 19 12:14:26 lightop gnome-shell[3479]: current session already has an ibus-daemon.
mar 19 12:14:27 lightop gnome-shell[3479]: Telepathy is not available, chat integration will be disabled.
mar 19 12:14:27 lightop gnome-shell[3479]: Usage of object.actor is deprecated for ClipboardIndicator
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'Extension' on the module 'dndExtension'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'DoNotDisturb' on the module 'doNotDisturb'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'GnomePresence' on the module 'system'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'DoNotDisturbToggle' on the module 'widgets'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'DoNotDisturbIcon' on the module 'widgets'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'SettingsManager' on the module 'settings'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'NotificationManager' on the module 'system'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'RemoteAPI' on the module 'settings'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: Some code accessed the property 'AudioManager' on the module 'system'. 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.
mar 19 12:14:27 lightop gnome-shell[3479]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/appIcons.js 1090]: unreachable code after return statement
mar 19 12:14:27 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.freedesktop.FileManager1' requested by ':1.308' (uid=1000 pid=3479 comm="/usr/bin/gnome-shell " label="unconfined")
mar 19 12:14:27 lightop systemd[3239]: Reached target GNOME session X11 services.
mar 19 12:14:27 lightop systemd[3239]: Starting GNOME XSettings...
mar 19 12:14:27 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.freedesktop.portal.IBus' requested by ':1.314' (uid=1000 pid=13127 comm="ibus-daemon --panel disable -r --xim " label="unconfined")
mar 19 12:14:27 lightop gsd-xsettings[13131]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
mar 19 12:14:27 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.portal.IBus'
mar 19 12:14:27 lightop systemd[3239]: Started GNOME XSettings.
mar 19 12:14:27 lightop systemd[3239]: Reached target GNOME XSettings.
mar 19 12:14:28 lightop gnome-shell[3479]: ibus_bus_hello: assertion 'ibus_bus_is_connected (bus)' failed
mar 19 12:14:28 lightop gnome-shell[3479]: Error while sending AddMatch() message: La conexión está cerrada
mar 19 12:14:28 lightop gnome-shell[3479]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
mar 19 12:14:28 lightop gnome-shell[3479]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
mar 19 12:14:29 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.FileManager1'
mar 19 12:14:29 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.141/org/ayatana/NotificationItem/Slack1
mar 19 12:14:29 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.117/StatusNotifierItem
mar 19 12:14:29 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.132/org/ayatana/NotificationItem/software_update_available
mar 19 12:14:30 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:hibernate
mar 19 12:14:30 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:playback-repeat
mar 19 12:14:30 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:screen-brightness-cycle
mar 19 12:14:30 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:rfkill
mar 19 12:14:30 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:playback-random
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop telegram-deskto[7060]: Failed to load module "canberra-gtk-module"
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.323/StatusNotifierItem
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:14:30 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update icon
mar 19 12:14:30 lightop gnome-shell[3479]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee01d2b0 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b60c0 StWidget ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee01d2b0 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b60c0 StWidget ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee01d8e0 StWidget.app-well-app-running-dot] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee01d2b0 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b60c0 StWidget ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b7030 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee01d2b0 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b60c0 StWidget ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b7030 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1edfd3b90 StBoxLayout] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee01d2b0 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b60c0 StWidget ("9")] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1ee0b7030 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1edfd3b90 StBoxLayout] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55f1edfd4180 StBin] which is not in the stage.
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
mar 19 12:14:32 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
mar 19 12:14:32 lightop gnome-shell[3479]: GNOME Shell started at Thu Mar 19 2020 12:14:27 GMT+0100 (CET)
mar 19 12:14:32 lightop gnome-shell[3479]: Registering session with GDM
mar 19 12:14:39 lightop org.freedesktop.FileManager1[3262]: Initializing Nextcloud-client-nautilus extension
mar 19 12:14:39 lightop org.freedesktop.FileManager1[3262]: Using python version sys.version_info(major=2, minor=7, micro=17, releaselevel='final', serial=0)
mar 19 12:14:39 lightop org.freedesktop.FileManager1[3262]: Could not connect to unix socket /run/user/1000/Nextcloud/socket. [Errno 2] No existe el archivo o el directorio
mar 19 12:14:39 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mar 19 12:14:48 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.gnome.ChromeGnomeShell' requested by ':1.328' (uid=1000 pid=13268 comm="/usr/bin/python3 /usr/bin/chrome-gnome-shell /usr/" label="unconfined")
mar 19 12:14:48 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.gnome.ChromeGnomeShell'
mar 19 12:14:58 lightop gnome-shell[3479]: Some code accessed the property 'FactsBox' on the module 'factsBox'. 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.
mar 19 12:14:58 lightop gnome-shell[3479]: hamster-shell-extension: 'hamster-windows-service' not running. Shutting down.
mar 19 12:14:58 lightop gnome-shell[3479]: Shutting down hamster-shell-extension.
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
mar 19 12:14:58 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
mar 19 12:15:03 lightop gnome-shell[3479]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6000007
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69c742e0.
mar 19 12:15:22 lightop gnome-shell[3479]: == Stack trace for context 0x555c6957d1a0 ==
mar 19 12:15:22 lightop gnome-shell[3479]: == Stack trace for context 0x555c6957d1a0 ==
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell[3479]: == Stack trace for context 0x555c6957d1a0 ==
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69c74ee0.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69c745e0.
mar 19 12:15:22 lightop gnome-shell[3479]: == Stack trace for context 0x555c6957d1a0 ==
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69c74be0.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69c748e0.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69fd5370.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
mar 19 12:15:22 lightop gnome-shell-ext[13294]: The offending signal was destroy on Gjs_ExtensionRow 0x555c69fd5670.
mar 19 12:15:35 lightop gnome-shell[3479]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
mar 19 12:15:35 lightop gnome-shell[3479]: Object Meta.BackgroundActor (0x55f1e8482330), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
mar 19 12:15:35 lightop gnome-shell[3479]: == Stack trace for context 0x55f1e7453320 ==
mar 19 12:15:35 lightop gnome-shell[3479]: #0   7ffe89130060 b   resource:///org/gnome/gjs/modules/overrides/GObject.js:508 (7f410c9ad8b0 @ 25)
mar 19 12:15:35 lightop gnome-shell[3479]: #1   55f1ea427be0 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:210 (7f40e8f838b0 @ 75)
mar 19 12:15:35 lightop gnome-shell[3479]: #2   55f1ea427b68 i   /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopGrid.js:115 (7f40e8f834c0 @ 12)
mar 19 12:15:35 lightop gnome-shell[3479]: #3   55f1ea427af0 i   resource:///org/gnome/shell/ui/main.js:224 (7f410c9cf940 @ 12)
mar 19 12:15:35 lightop gnome-shell[3479]: JS ERROR: Error: Argument 'instance' (type interface) may not be null
mar 19 12:15:35 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:15:35 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:15:35 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:15:35 lightop gnome-shell[3479]: JS ERROR: TypeError: actor.get_meta_window(...) is null
mar 19 12:15:35 lightop systemd[3239]: Stopped target GNOME XSettings.
mar 19 12:15:35 lightop systemd[3239]: Stopped target GNOME session X11 services.
mar 19 12:15:35 lightop systemd[3239]: Stopping GNOME XSettings...
mar 19 12:15:35 lightop systemd[3239]: gsd-xsettings.service: Succeeded.
mar 19 12:15:35 lightop systemd[3239]: Stopped GNOME XSettings.
mar 19 12:15:35 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.freedesktop.portal.IBus' requested by ':1.335' (uid=1000 pid=13322 comm="ibus-daemon --panel disable -r " label="unconfined")
mar 19 12:15:35 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.portal.IBus'
mar 19 12:15:35 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): EDID vendor "SHP", prod id 5146
mar 19 12:15:35 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): Printing DDC gathered Modelines:
mar 19 12:15:35 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1111 -hsync -vsync (66.6 kHz eP)
mar 19 12:15:35 lightop /usr/lib/gdm3/gdm-x-session[3259]: (II) modeset(0): Modeline "1920x1080"x0.0  110.92  1920 1968 2000 2080  1080 1083 1088 1111 -hsync -vsync (53.3 kHz e)
mar 19 12:15:35 lightop gsd-media-keys[3625]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
mar 19 12:15:36 lightop gsd-media-keys[3625]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
mar 19 12:15:37 lightop gnome-shell[3479]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
mar 19 12:15:37 lightop gnome-shell[3479]: Will monitor session 3
mar 19 12:15:37 lightop gnome-shell[3479]: current session already has an ibus-daemon.
mar 19 12:15:37 lightop gnome-shell[3479]: Telepathy is not available, chat integration will be disabled.
mar 19 12:15:37 lightop gsd-media-keys[3625]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface “org.gnome.Shell” on object at path /org/gnome/Shell
mar 19 12:15:37 lightop gnome-shell[3479]: Usage of object.actor is deprecated for ClipboardIndicator
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'Extension' on the module 'dndExtension'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'DoNotDisturb' on the module 'doNotDisturb'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'GnomePresence' on the module 'system'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'DoNotDisturbToggle' on the module 'widgets'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'DoNotDisturbIcon' on the module 'widgets'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'SettingsManager' on the module 'settings'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'NotificationManager' on the module 'system'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'RemoteAPI' on the module 'settings'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'AudioManager' on the module 'system'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: Some code accessed the property 'FactsBox' on the module 'factsBox'. 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.
mar 19 12:15:37 lightop gnome-shell[3479]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-dock@ubuntu.com/appIcons.js 1090]: unreachable code after return statement
mar 19 12:15:37 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.freedesktop.FileManager1' requested by ':1.343' (uid=1000 pid=3479 comm="/usr/bin/gnome-shell " label="unconfined")
mar 19 12:15:38 lightop systemd[3239]: Reached target GNOME session X11 services.
mar 19 12:15:38 lightop systemd[3239]: Starting GNOME XSettings...
mar 19 12:15:38 lightop ibus-daemon[13322]: GChildWatchSource: Exit status of a child process was requested but ECHILD was received by waitpid(). See the documentation of g_child_watch_source_new() for possible causes.
mar 19 12:15:38 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Activating service name='org.freedesktop.portal.IBus' requested by ':1.349' (uid=1000 pid=13387 comm="ibus-daemon --panel disable -r --xim " label="unconfined")
mar 19 12:15:38 lightop gsd-xsettings[13390]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist
mar 19 12:15:38 lightop systemd[3239]: Started GNOME XSettings.
mar 19 12:15:38 lightop systemd[3239]: Reached target GNOME XSettings.
mar 19 12:15:38 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.portal.IBus'
mar 19 12:15:39 lightop gnome-shell[3479]: ibus_bus_hello: assertion 'ibus_bus_is_connected (bus)' failed
mar 19 12:15:39 lightop gnome-shell[3479]: Error while sending AddMatch() message: La conexión está cerrada
mar 19 12:15:39 lightop gnome-shell[3479]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
mar 19 12:15:39 lightop gnome-shell[3479]: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
mar 19 12:15:40 lightop dbus-daemon[3262]: [session uid=1000 pid=3262] Successfully activated service 'org.freedesktop.FileManager1'
mar 19 12:15:40 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.141/org/ayatana/NotificationItem/Slack1
mar 19 12:15:40 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.117/StatusNotifierItem
mar 19 12:15:40 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.132/org/ayatana/NotificationItem/software_update_available
mar 19 12:15:40 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:screen-brightness-cycle
mar 19 12:15:40 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:playback-random
mar 19 12:15:40 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:hibernate
mar 19 12:15:40 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:playback-repeat
mar 19 12:15:40 lightop gsd-media-keys[3625]: Failed to grab accelerator for keybinding settings:rfkill
mar 19 12:15:40 lightop telegram-deskto[7060]: Failed to load module "canberra-gtk-module"
mar 19 12:15:40 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.359/StatusNotifierItem
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: [AppIndicatorSupport-FATAL] unable to update overlay icon
mar 19 12:15:41 lightop gnome-shell[3479]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
mar 19 12:15:41 lightop gnome-shell[3479]: hamster-shell-extension: 'hamster-windows-service' not running. Shutting down.
mar 19 12:15:41 lightop gnome-shell[3479]: Shutting down hamster-shell-extension.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f275c20 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d08b0 StWidget ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f275c20 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d08b0 StWidget ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f2760b0 StWidget.app-well-app-running-dot] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f275c20 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d08b0 StWidget ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d1d70 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f275c20 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d08b0 StWidget ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d1d70 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d2770 StBoxLayout] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f275c20 StButton.app-well-app ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d08b0 StWidget ("9")] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d1d70 Gjs_BaseIcon.overview-icon] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d2770 StBoxLayout] which is not in the stage.
mar 19 12:15:42 lightop gnome-shell[3479]: st_widget_get_theme_node called on the widget [0x55aa6f1d35c0 StBin] which is not in the stage.
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
mar 19 12:15:43 lightop gnome-shell[3479]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
mar 19 12:15:43 lightop gnome-shell[3479]: GNOME Shell started at Thu Mar 19 2020 12:15:37 GMT+0100 (CET)
mar 19 12:15:43 lightop gnome-shell[3479]: Registering session with GDM
mar 19 12:15:45 lightop thunderbird.desktop[3479]: JavaScript error: resource:///modules/activity/autosync.jsm, line 251: uncaught exception: 2147746065
mwilck commented 4 years ago

hamster-shell-extension: 'hamster-windows-service' not running. Shutting down.

Big step forward. The extension starts. Now you seem to have a problem with the autostart of the hamster-windows-service. Normally the extension should be able to start the hamster DBus service automatically. Now it looks as if your snap package was having an issue.

Try firing up the program "d-feet", select the Session Bus at the top, and type "hams" in the search window. You should see org.gnome.Hamster.WindowServer listed. Clicking on that should activate the interface, if it isn't active yet (that's the most important step, actually). Then you can select /org/gnome/Hamster/WindowServer -> org.gnome.Hamster.WindowServer -> Methods -> overview(), click on it, adn in the popup that appears, click on "execute" - you should get a hamster overview window. If this works, the extension should work, too.

Otherwise: Can you start "hamster" from the command line? If you do, leave the window open, and restart the GNOME shell again, does the extension work?

You may also want to look

marcbria commented 4 years ago

What if I install the regular version instead of snap one? (or you want me to go with the snap to test this scenario)

mwilck commented 4 years ago

Try it. In theory it shouldn't matter, but the error message I quoted above points toward a problem with hamster itself.

mwilck commented 4 years ago

@extraymond should be able to comment on the snap package. That's not my area of expertise.

extraymond commented 4 years ago

@marcbria About the snap version, if the hamster-service is started, external applications should be able to interact with it on the dbus path.

Screenshot from 2020-03-19 22-18-08

Screenshot is d-feet(non-snap app) inspecting interfaces of hamster.

mwilck commented 4 years ago

@extraymond , does that mean auto-activation of the service doesn't work with snap?

extraymond commented 4 years ago

That's right. At the moment all snap's will behave this way, because snap's is still too strict about allowing external services to launch user session dbus-services. snap related discussion

So in order to launch the snap, currently the launcher will manually wake up the dbus service before the GUI client. For desktop use cases it might be alright, but it will make extensions a bit hard to use.

mwilck commented 4 years ago

That's a problem for the extension, because the extension is started right after login, and by that time, the hamster-windows-service won't be started yet (Edit: I'm not certain about that), even if you create an autostart file to do that (if that's possible with snap, I don't know).

The extension gives up after failing to start the DBus service. Even if the service becomes available later, the extension won't be activated again, at least not in the GNOME panel (perhaps that's a bug, but I have no idea how to fix it).

So, basically, users of the snap package and the GNOME extension will need to launch hamster manually after logging in, and then type Alt-F2 -> r to restart GNOME shell, which is not exactly user-friendly, and doesn't work at all for Wayland.

mwilck commented 4 years ago

This is worth a separate issue.

@marcbria, please report if manually starting hamster and Alt-F2 - r "fixes" the issue for you. We'll need to discuss the general problem with the snap package separately.

extraymond commented 4 years ago

Thanks for the info, that sounds really bad. So either the extension have to start hamster service manually, or it would need to have some delay after it can detect the snap has started.

mwilck commented 4 years ago

@extraymond, in the discussion you linked someone said that autostart does work. So that might be worth a try. I honestly don't know if autostart will be "soon enough" - at worst it might cause timing issues, and work sometimes, sometimes not. Anyway, it would open the possiblity to implement a poor man's workaround by simply waiting a few seconds in the extension.

extraymond commented 4 years ago

Autostart works either via snap itself or putting it in the xdg autostart directory. But you are correct that it might not be soon enough for the extension to pick it up.

Another option I can think of,is that since the extension is unconfined, which can launch the snap, maybe it would make more sense to let the extension launch hamster on first run, therefore the extension will always be launched with the service ready.

mwilck commented 4 years ago

maybe it would make more sense to let the extension launch hamster on first run, therefore the extension will always be launched with the service ready.

Honestly, I don't like that idea. DBus service activation is nice and clean. Replacing this with an executable forked and exec'd from a shell extension sounds ugly to me.

Anyway I've forked #328 now.

marcbria commented 4 years ago

sorry, but I get lost in the DBus discussion. Rolling back to the last post I understand, yes? ;-) https://github.com/projecthamster/hamster-shell-extension/issues/326#issuecomment-601184354

About the request of reporting in a different issue... What do you want me to report? I mean... this thread is about problems installing in ubuntu 19.10 and we are still there, isn't it? https://github.com/projecthamster/hamster-shell-extension/issues/326#issuecomment-601231371

extraymond commented 4 years ago

@marcbria

In summary:

  1. Currently, snaps can't use dbus-activation to activate program if the dbus path is called
  2. gnome-shel-extension need the dbus-service to operate
  3. So here are the options we're describing:
    • a. either the snap based hamster service to autostart before the gnome-shell extension
    • b. or you let the gnome-shell extension to invoke the service if it's not up.
    • c. or hibernate the gnome-shell extension until if can find the service is up.

We're discussing this because it seems that you are running into the problem where the extension can't find the dbus-service. And we're suspecting it's due to snap. You can try the non-snap version or try the advice https://github.com/projecthamster/hamster-shell-extension/issues/326#issuecomment-601231371 after you can see the hamster service up and running.

I believe what @mwilck mean by reporting, is to narrow down the scope of the problem, and let snap specific stuff go to #328 so people can find better issues they bump into. Did you made that work if you start the service before hand? I'm quite interested.

mwilck commented 4 years ago

Guys, don't expect a solution on the exension side soon. We're currently working on getting the support for recent GNOME versions merged. After that, we'll be willing to take patches, but I don't think we'll actively work on this in the near future. At least I have different priorities, both with the extension and otherwise.

I don't want to reject or disappoint anyone, I just want to avoid raising expectations too high.

marcbria commented 4 years ago

Ok... so we just need to avoid snap. It's not a big deal if, at the end (when the app is tested enough), you can deliver DEB and RPM (that are the most common) and the rest can complie from the sources.

Today I need to focus in work. I will try to test your suggestion during the weekend or on Monday.

Thanks a lot for your time, m.