search

Cacti / cacti

Cacti ™
http://www.cacti.net
GNU General Public License v2.0
1.65k stars 406 forks source link

Various issues in Chrome and only Chrome. #3044

Closed crkinard closed 4 years ago

crkinard commented 5 years ago

Cacti v1.2.2 Raspberry Pi Chrome 77.0.3865.120

Graphs do not show up when viewing a host in tree view. Only way to get ANY graph to show up in chrome is to: Management -> Devices -> Select device -> Graph list -> Right click broken image icon for graph and and say open in another tab.

Most right click menus on top of said broken image graphs do not work. Well, the right click menu shows but no sub items expand and clicking on anything does nothing.

Clicking on the user name in the top right does nothing. No drop down menu so impossible to set account settings or even log out.

Factory defaulting chrome (clearing all cache's and settings as well as unloading all extensions) does not fix the issue.

All works fine in IE.

netniV commented 5 years ago

What console errors are you seeing? I suspect slowness is an issue and therefore Chrome is terminating the scripts though the scripts themselves work fine.

crkinard commented 5 years ago

I am not sure. There seems to be no delay in loading the page or anything hanging when said page loads.

netniV commented 5 years ago

You'll need to use the network tab of the developer tools to investigate and check the console errors.

crkinard commented 5 years ago

I think this is the error for the graphs. Getting one for each graph that should be displayed.

Refused to load the image 'data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAyMAAAFMCAIAAABXjPQ0AAAABmJLR0QA/wD/AP+gvaeTAAAgAElEQVR4nOydeXxMV/vAz10mM9mJ7CETEUuCoEGb2LeiilfR1ku1iGqV0uWt0ir6Q7VV5a2gJSqopVpvLa2t9iKKVEOoLSZ7Insms9/l98eVMWbLPbPfON+Pz8jMnPneZ869Mzl57jnPxS5dugQQCAQCgUAgEI6mtraWBAB06NDB3ZEgEAgEAoFANDV27NiBuzsGBAKBQCAQiCYLGmkhEAgEAoFAOAs00kIgEAgEAoFwFqS7A0AgEAgEAoEQJDU1NUaPNGvWzOgRNNJCIBAIBAKBsIXi4mLuh/z8/Ojo6Pz8/GHDhhm1QSMtBAKBQCAQCFtISEgAAFAUlZ+fHx8fX1BQYNoGjbQQCAQCgUAgbESpVN65c8fb2zs3N9fb29u0ARppIRAIBAKBQNjClStXAABSqTQ+Pr6ws...s0NIQz68agpVAoFi1ahBCSSqU4JAAAMAk1Li5Oe6cdAAAMs7a2trCwqKmpaWhoeP78uaenp52d3cOHD6uqqhobG21sbKhUan9/v52dXW9v7+DgIIfDIf2USqVWV1fLZDIrKysWi0Wn02tra+vr62fOnKmb38nJqa6urrGxkU6n0+l0giBwGBqNRqVS1dXVqVQqoVBIo9HodHp1dbWfn5/ueMja2hrv6P79+zY2Ns7OzpaWlrr7tbe3f/DgQVVVVUtLi6enJ47B1dW1r6/Pzs6OyWQqlUqJRNLS0sJgMAQCAbwRDwAwiUQiody8eVMoFE50JAAAMCoKhUKpVHp7e090IAAA8P/Onj0LN8MBAK+89vb2u3fvcrnciQ4EAACGg/e0AACvPFdXV1dX14mOAgAASMA9LQAAAACA8QIjLQAAAACA8QIjLQAAAACA8QIjLQAAAACA8UIpLi5uamqa6DAAAAAAAP6B/g/+uPGE8MRqogAAAABJRU5ErkJggg==' because it violates the following Content Security Policy directive: "default-src 'self' 'unsafe-inline'". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback.

Another error:

Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "default-src 'self' 'unsafe-inline'".

at getZoomOutFactorText (jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:746)
at zoomContextMenu_init (jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:884)
at zoomFunction_init (jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:389)
at HTMLImageElement.<anonymous> (jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:161)
at HTMLImageElement.dispatch (jquery.js?e72ea0937e1b2729159f27b6749b8685:3)
at HTMLImageElement.elemData.handle (jquery.js?e72ea0937e1b2729159f27b6749b8685:2)

getZoomOutFactorText @ jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:746 zoomContextMenu_init @ jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:884 zoomFunction_init @ jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:389 (anonymous) @ jquery.zoom.js?ebe407101d8d61e617730e487c2739f2:161 dispatch @ jquery.js?e72ea0937e1b2729159f27b6749b8685:3 elemData.handle @ jquery.js?e72ea0937e1b2729159f27b6749b8685:2

netniV commented 5 years ago

As this occurs in the jquery.zoom.js, I'm going to label this one a 3rd party bug for now. We don't maintain that as far as I am aware altough @cigamit or @TheWitness may correct me on that. Not sure how we would actually fix that without supplying an upstream patch.

cigamit commented 5 years ago

jquery.zoom.js was created by @browniebraun. So, it's supported. Have to see what is broken on Chrome. I did some bug fixing lately for Chrome too. However, it could be that Chrome, though very fast has thousands of bugs.

cigamit commented 5 years ago

Before I invest any time on this, please upgrade to branch 1.2.x. Then let us know what you find.

reubenfarrelly commented 4 years ago

Curiously I am seeing something very similar but I'm not sure if it's the same bug or not. As of 1.2.x today (28-Nov) I cannot get any graphs to display in Tree View in the Graphs Tab, with Chrome, or in fact Edge. But with Firefox everything renders just fine. If I change from Tree View everything works.

I have however just changed from Modern to Classic Theme and it all immediately started working which leads me to think this could be a theme specific bug. Can the OP confirm if this is the case as well if it is possible to log in and change it?

Looks a lot like Tree View + Modern theme is broken...

netniV commented 4 years ago

If you are on a broken theme, do you see any console javascript errors?

reubenfarrelly commented 4 years ago

I'm getting the following output from Edge:

HTML1300: Navigation occurred. graph_view.php (1,1)

HTML1524: Invalid HTML5 DOCTYPE. Consider using the interoperable form “<!DOCTYPE html>”. graph_view.php (1,1)

CONSOLE1810304: console.memory is not implemented and will return 0 for all attributes. Please use the memory profiler to monitor memory utilisation.

2HTML1300: Navigation occurred. graph_view.php (1,1)

CONSOLE1810304: console.memory is not implemented and will return 0 for all attributes. Please use the memory profiler to monitor memory utilisation.

SEC7115: :visited and :link styles can only differ by colour. Some styles were not applied to :visited. graph_view.php (1,1)

From Firefox:

Error: Can't find profile directory. XULStore.jsm:66:15 Unknown category for SetEventRecordingEnabled: fxmonitor Content Security Policy: Directive ‘child-src’ has been deprecated. Please use directive ‘worker-src’ to control workers, or directive ‘frame-src’ to control frames respectively. LoginManager: searchLogins: formActionOrigin or httpRealm is recommended LoginManager.jsm:473:13 Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml LoginManager: searchLogins: formActionOrigin or httpRealm is recommended LoginManager.jsm:473:13 Use of nsIFile in content process is deprecated. 8 NetUtil.jsm:253:8 NS_ERROR_FAILURE: Failed to open input source 'file:///' DevToolsUtils.js:678 ‘src’ attribute of Githubissues.

  • Githubissues is a development platform for aggregating issues.