Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJonathan Billings
2017-01-11 14:38:57 UTC
Description of problem:
After the system has been booted for a couple weeks, the entries in the Places menu stop responding to clicks. In the journal, I see:
Jan 11 08:59:29 caen-vnc-vm05 gnome-shell[25418]: GNOME Shell started at Wed Jan 11 2017 08:59:19 GMT-0500 (EST)
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: (gnome-shell:25418): Gjs-WARNING **: JS ERROR: Error: can't convert timestamp to an integer
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: PlaceInfo<.launch@/usr/share/gnome-shell/extensions/places-menu.github.com/placeDisplay.js:46
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: PlaceMenuItem<.activate@/usr/share/gnome-shell/extensions/places-menu.github.com/extension.js:55
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: PopupBaseMenuItem<._onButtonReleaseEvent@resource:///org/gnome/shell/ui/popupMenu.js:118
Jan 11 08:59:34 caen-vnc-vm05 gnome-session[25186]: wrapper@resource:///org/gnome/gjs/modules/lang.js:169
Issue is also reported here: https://github.com/gcampax/gnome-shell-extensions/issues/7
The solution of changing 'timestamp' to -1 in the javascript file fixes this for me.
Version-Release number of selected component (if applicable):
gnome-shell-extension-places-menu-3.14.4-21.el7.noarch
How reproducible:
It doesn't appear to happen right after a reboot, I didn't see this happen until the system had been up 26 days, even though people were logging in to all our systems for several weeks leading up to that time.
Steps to Reproduce:
1. Install gnome-shell-extension-places-menu-3.14.4-21.el7.noarch
2. Log in after several weeks and test.
Actual results:
Places menu entries are unresponsive. Logs indicate javascript error.
Expected results:
Places menu entries will open up Nautilus windows in appropriate directories
Additional info:
https://github.com/gcampax/gnome-shell-extensions/issues/7
Comment 1Jonathan Billings
2017-01-11 18:06:40 UTC
With some simple debugging (i.e. putting "log(timestamp)" in the javascript) I can see that timestamp is currently 2359526273 on the systems affected. Perhaps this is because 2359526273 is greater than 2^31 milliseconds (signed 32-bit int, 2147483648 milliseconds).
Comment 2Jonathan Billings
2017-01-11 18:24:01 UTC
And I confirmed this in lookingglass (Alt-F2 'lg'):
>>> global.create_app_launch_context(2359526273, -1)
r(0) = <exception Error: can't convert 2359526273 to an integer>
>>> global.create_app_launch_context(2147483648, -1)
r(1) = <exception Error: can't convert 2147483648 to an integer>
>>> global.create_app_launch_context(2147483647, -1)
r(2) = [object instance proxy GType:GdkX11AppLaunchContext jsobj@0x7f85941...
You can see that 2359526273 (earlier today) and 2147483648 (2^31) both create an exception, but 2147483647 (2^31 - 1) is fine.
So, looks like its a bug using a signed 32-bit int.
Comment 4Jonathan Billings
2017-02-14 17:19:37 UTC
It's been over 27 days since I filed this bug, can anyone confirm it?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:2098