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.

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

FIX#107: Indicator stops working after screen lock #177

Merged
merged 1 commit into from
Feb 25, 2020

Conversation

drivera73
Copy link

Added code to handle the case when the name org.kde.StatusNotifierWatcher can't be owned (for whatever reason), and thus the indicators disappear when the lock screen is engaged (manually or otherwise).

This is by no means a final approach, and it may revive some of the side-effects that gave birth to the watchDog object, but I think it's a start.

@echosa
Copy link

echosa commented Aug 29, 2019

Just tried this myself, and it seems to work.

@echosa
Copy link

echosa commented Sep 5, 2019

Correction: it works for anything that's already open. However, there's still an issue:

  • apply this PR's fix
  • reload GNOME
  • have some programs running in the appindicators
  • lock screen
  • wake and unlock
  • notice that the appindicators still show (the fix in this PR does this)
  • open a new program that uses has an appindicator

You'd expect the new app to show up. It does not. You have to restart GNOME again for it to show up.

@echosa
Copy link

echosa commented Sep 5, 2019

Ah, actually, this might just be in issue with some apps, in my case, Slack, specifically. Even if I have Slack running, it doesn't show up again after unlocking the computer, like others do. I have to restart GNOME to get it to show up.

@drivera73
Copy link
Author

The issue has to do with an already-running instance of indicator-application which was mucking up the works. Removed that, and everything works just fine, real-time.

@echosa
Copy link

echosa commented Sep 6, 2019

Removed that

I don't fully understand the issue or what you did. Can you explain so I and others can get it working, too? :-)

@drivera73
Copy link
Author

In Ubuntu's Gnome there's an "application indicators" program running by default (you can run a "ps -ef | grep indicat" ... or maybe it was "appind" ... I forget). When that program isn't available (i.e its .deb has been removed), then this extension works flawlessly because it's able to own the handle to org.kde.StatusNotifierWatcher

Thus, what you need to do is figure out the following:

  1. is that application indicator program running in your system?
  2. which .deb installed it ("dpkg -S " should do the trick for you ... you'll need to discover the executable path yourself)

Once you have that, you can remove the .deb, and re-start the Gnome shell, and voilá - this extension will work flawlessly.

Cheers!

@echosa
Copy link

echosa commented Sep 6, 2019

Thanks! Here's hoping it works for me, too!

$ ps -ef | grep indic
echosa    2195  1702  0 09:52 tty2     00:00:00 /usr/lib/x86_64-linux-gnu/indicator-application/indicator-application-service
echosa   13799 13698  0 10:29 pts/1    00:00:00 grep --color=auto indic
$ dpkg -S indicator-application-service
indicator-application: /usr/lib/x86_64-linux-gnu/indicator-application/indicator-application-service
$ sudo apt remove indicator-application 
[sudo] password for echosa: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be REMOVED:
  indicator-application
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 122 kB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 311262 files and directories currently installed.)
Removing indicator-application (12.10.1+19.04.20190308.1-0ubuntu1) ...

Then I restarted GNOME.

@3v1n0 3v1n0 merged commit d7fa506 into ubuntu:master Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants