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.
DescriptionSiteshwar Vashisht
2015-06-09 12:09:51 UTC
Description of problem:
Unable to launch applications from Applications menu if system is up for long time.
Version-Release number of selected component (if applicable):
gnome-shell-extension-apps-menu-3.8.4-10.el7_0.noarch
How reproducible:
Always
Steps to Reproduce:
1. Keep system up for approximately a month.
2. Try to launch applications through Applications menu
Actual results:
Applications are not launched and below error is logged in journalctl logs :
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: wrapper([object GObject_Union])@/usr/share/gjs-1.0/lang.js:213
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: ([object GObject_Object],[object GObject_Union])@/usr/share/gnome-shell/js/ui/popupMenu.js:87
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: wrapper([object GObject_Object],[object GObject_Union])@/usr/share/gjs-1.0/lang.js:213
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: "'
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: JS ERROR: !!! Exception was: Error: can't convert event.get_time() to an integer
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: JS ERROR: !!! message = '"can't convert event.get_time() to an integer"'
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: JS ERROR: !!! fileName = '"/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js"'
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: JS ERROR: !!! lineNumber = '77'
Jun 05 17:09:14 oracle-node1.i2pos gnome-session[29144]: JS ERROR: !!! stack = '"([object GObject_Union])@/usr/share/gnome-shell/extensions/apps-menu.github.com/extension.js:77
Expected results:
Applications should be launched
Additional info:
open_new_window() method is incorrectly called with timestamp parameter and it should be fixed by passing '-1' instead of timestamp parameter.
Comment 1Siteshwar Vashisht
2015-06-09 12:19:52 UTC
Thanks, this fixed the issue for me as well. Does "pushed upstream" mean this will be in a updated package soon, or should I be patching all my systems by hand?
(In reply to Matt from comment #7)
> Does "pushed upstream" mean this will be in a updated package soon
It means upstream releases 3.16.2 and later contain the fix. It is also on track to be included in RHEL 7.2, and it'd certainly be possible to roll out a fix for 7.1 provided we get the necessary permissions.
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://rhn.redhat.com/errata/RHBA-2015-2216.html