apps-menu: Exception: can't convert event.get_time() to an integer #7
Comments
I can confirm the same issue and error. |
this seems to be present on the version of the plugin that comes as part of centos7, and not fixed in any update (just did a yum update and it reverted my manual -1 fix) |
I am now seeing this issue on a Debian Jessie box, with 28 days of uptime. Maybe, it's a problem once milliseconds since kernel reboot is outside a 32-bit signed integer range? This is a 64-bit platform, though... |
This occurs on RHEL7.2 as well. |
I opened an issue in debian for this ages ago, but have had no response there either. |
Furthermore, the same thing can happen with the Places menu. Again, a workaround (not fix) is to edit /usr/share/gnome-shell/extensions/places-menu@gnome-shell-extensions.gcampax.github.com/placeDisplay.js and change line 46 from: |
I came across this while investigating a similar bug in my own extension. FWIW, the correct solution seems to be:
Which is now used many places in Gnome Shell and explicitly allowed in the Shell global object documentation: https://developer.gnome.org/shell/stable/shell-shell-global.html#shell-global-create-app-launch-context |
After a while of using the applications menu extension, sometimes items no longer execute when clicked on. Notably, gnome-shell outputs the following when you try:
The only way to stop it which I could find was to log out entirely - even restarting gnome-shell was insufficient.
Changing line 77 from:
this._app.open_new_window(event.get_time());
to e.g.:
this._app.open_new_window(-1);
makes this problem go away though. But obviously this is not a true fix. Hopefully a real fix should be easy so please have a look, thanks :-)
The text was updated successfully, but these errors were encountered: