Red Hat Bugzilla – Bug 1371398
[DELL 7.3 BUG] gnome-session reports depreciation of octal literals and escape sequence.
Last modified: 2018-05-17 10:39:45 EDT
Created attachment 1195642 [details]
/var/log/messages file showing the warning
Description of problem:
After successful installation and boot into RHEL-7.3 alpha and beta in BIOS mode, /var/log/messages shows the following warning messages:
" gnome-session: Gjs-Message: JS WARNING: [resource:///org/gnome/shell/ui/extensionSystem.js 301]: octal literals and octal escape sequences are deprecated
gnome-session: Gjs-Message: JS WARNING: [resource:///org/gnome/shell/gdm/loginDialog.js 1017]: anonymous function does not always return a value ".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.install RHEL7.3 beta on x86_64 in BIOS mode
2. boot into OS and check for /Var/log/messages
we can see the warning
no such warning should be there
Hi Ray ,
I am getting this issue in rhel 7.3 snapshort 5 also , this bug is duplicate of bz 1346931 which was closed as cantfix ,may i know the reson for the js warning and why it was decided not to get fixed.is there a plan to get it fixed in future release
This is a legitimate bug and it should get looked at in a future update.
The deprecated octal syntax warning came up last week on another bug actually. I got a local fix, but didn't consider it freeze-worthy ...
Please provide me the root cause with the fix which you have
Created attachment 1313424 [details]
Use non-deprecated octal notation in downstream patch
(Not sure what you mean by "root cause", but I attached the warning fix now)
I took the liberty to fix the warning when rebasing the downstream patch for RHEL 7.5 - it should be gone in the latest gnome-shell build.
Warnings not present in 3.26.
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.