After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698963 - Backtraces from network indicator
Backtraces from network indicator
Status: RESOLVED DUPLICATE of bug 698962
Product: gnome-shell
Classification: Core
Component: network-indicator
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2013-04-26 15:28 UTC by Lionel Landwerlin
Modified: 2013-09-20 20:22 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
network: fix backtraces with VPN connections (1.89 KB, patch)
2013-04-26 15:29 UTC, Lionel Landwerlin 		none Details | Review

Description Lionel Landwerlin 2013-04-26 15:28:53 UTC 
I get a few of thoses with a VPN connection :

      JS ERROR: !!!   Exception was: TypeError: obj.active is undefined
      JS ERROR: !!!     message = '"obj.active is undefined"'
      JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/status/network.js"'
      JS ERROR: !!!     lineNumber = '1564'
      JS ERROR: !!!     stack = '"([object GObject_Object])@/usr/share/gnome-shell/js/ui/status/network.js:1564
  wrapper([object GObject_Object])@/usr/share/gjs-1.0/lang.js:213
  ()@/usr/share/gnome-shell/js/ui/status/network.js:2032
  wrapper()@/usr/share/gjs-1.0/lang.js:213
  ([object GObject_Object],[object GObject_ParamSpec])@/usr/share/gnome-shell/js/ui/status/network.js:2287
  wrapper([object GObject_Object],[object GObject_ParamSpec])@/usr/share/gjs-1.0/lang.js:213
  "'
Comment 1 Lionel Landwerlin 2013-04-26 15:29:47 UTC 
Created attachment 242586 [details] [review]
network: fix backtraces with VPN connections
Comment 2 Giovanni Campagna 2013-04-26 15:57:58 UTC 
No, that code should never see obj.active == null (ok, if you apply 698962 actually)
In what conditions is this happening?
Comment 3 Dan Williams 2013-09-20 20:22:27 UTC 
This is caused by the checkConnection issue you've identified in bug 698962, so I'm duping this one to that.

*** This bug has been marked as a duplicate of bug 698962 ***