Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

no network activity #2

Closed
anika200 opened this issue Jun 6, 2016 · 2 comments
Closed

no network activity #2

anika200 opened this issue Jun 6, 2016 · 2 comments

Comments

@anika200
Copy link

anika200 commented Jun 6, 2016

Not sure what I need or how to fix my network monitor suddenly quit working. I think it happened as a result of the new update I did on 6/6/16 but I had system updates that day too..??
How can it be fixed?
@elvetemedve
Copy link
Owner

@anika200 Can you take a look at the error logs, which could give some hint where to look for the issue?

In the Gnome desktop session press Alt + F2 and type the lg command. Now select the Extensions tab on the top right corner. Scroll down to the Network Monitor entry and click on the Show Errors.
What do you see there?

@anika200
Copy link
Author

anika200 commented Jun 7, 2016

No errors there, my bad though it seems to be working fine today. I have no idea what was wrong, consider the problem solved. Thank you for the great extension and taking the time to respond.

@anika200 anika200 closed this as completed Jun 7, 2016
@elvetemedve elvetemedve mentioned this issue May 10, 2021
Merged
elvetemedve added a commit that referenced this issue Mar 21, 2023
@elvetemedve
Fix bug in removing observers
1b79fbf 
When the extension is disabled, all observers must be removed which are
updating the GUI. It's not happening for widgets, which can cause errors
when terying to update a UI element after freeing.

Example:
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: clutter_text_get_editable: assertion 'CLUTTER_IS_TEXT (self)' failed
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: == Stack trace for context 0x559ef55c4180 ==
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: #0   559ef985b408 i   /home/geza/.local/share/gnome-shell/extensions/System_Monitor@bghome.gmail.com/widget.js:103 (58421c75a60 @ 18)
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: #1   559ef985b368 i   /home/geza/.local/share/gnome-shell/extensions/System_Monitor@bghome.gmail.com/widget.js:299 (58421c7a4c0 @ 51)
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: #2   559ef985b2b8 i   /home/geza/.local/share/gnome-shell/extensions/System_Monitor@bghome.gmail.com/widget.js:374 (58421c7a7e0 @ 22)
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: #3   7fff3eebcb40 b   /home/geza/.local/share/gnome-shell/extensions/System_Monitor@bghome.gmail.com/meter.js:44 (58421c68ba0 @ 127)
Mar 21 18:29:44 Geza-ThinkPad-T580 gnome-shell[72961]: #4   559ef985b228 i   /home/geza/.local/share/gnome-shell/extensions/System_Monitor@bghome.gmail.com/meter.js:80 (58421c68d80 @ 25)

The bug is caused by the wrong order of calling _destroyIcon() and
_destroyMeterWidget(), plus the if condition in the second function
which hides the problem.
The solution is to free items in reversed order compared to creation.
Meaning _destroyMeterWidget() should be called first and _destroyIcon() second.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elvetemedve @anika200