On 08/30/2016 01:25 PM, Ranjan Maitra wrote:
Hi,
Thanks for the response.
On Mon, 29 Aug 2016 19:19:33 -0700 Samuel Sieb <samuel(a)sieb.net> wrote:
> On 08/29/2016 04:37 PM, Ranjan Maitra wrote:
>> I understand that Fedora has gone the way of my hated linux distribution (Ubuntu)
in actively disconnecting hibernate in a very disappointing distribution, but I still
think that someone may know what to do so I thought that I would post this here and get
suggestions and advice.
>>
> See
https://bugzilla.redhat.com/show_bug.cgi?id=1206936 for why and how
> it's being worked on.
From what I understand, this bug is about the laptop not resuming from hibernate but
booting. Mine boots just fine from following the instructions by Fedora. This is not a
problem.
>> However, of late, since F24, I have been having this problem that the laptop
comes back from hibernate but the nm-applet does not. Basically, what happens is that the
nm-applet has the disconnected symbol. The network does work (at the location it was
working from when the laptop was hibernated). It will not work in a new location simply
because nm-applet does not have the ability to provide me with a list of new possibly
connections. I have not tried this part with ethernet but I suspect that the general idea
would be similar.
>>
> Where do you see an "nm-applet"? I have no such process on my F24
> laptop, so how do you restart it? I just did a hibernate test. I'm
> using ethernet and when it resumed, the connection status at the top
> showed disconnected even though it was working. However, in the menu it
> said connected and unplugging and replugging the cord reset the status
> icon. I had wifi hardware disabled at the time and re-enabling it
> automatically connected. It takes so long to resume that I really don't
> want to try again with wifi enabled, but it does seem to be fine.
I use openbox and I have nm-applet (which controls NetworkManager using a graphical
interface from a system tray). The program is run using nm-applet but once on, it still
keeps running. What happens is after waking up from hibernate, I lose the ability to
change and get new connections. Specifically, I have a similar experience as you, in that
the connection status at the top shows disconnected even though it is working. But, it is
important to note that because the status is disconnected, I do not have any other wifi
networks shown to be available.
> There was one problem on resuming. gnome-settings-daemon was spamming
> the pcscd process really badly for some reason. Restarting pcscd didn't
> make any difference, I had to kill gnome-settings-daemon.
>
>> The only way I can get back to using nm-applet to provide me with Wifi
connections (beyond the one to which it has been connected) is by killing and restarting
nm-applet. The process has to be repeated for every hibernate.
>>
> Please explain how you did this.
I used:
killall nm-applet
nm-applet &
I believe this is caused by the startup sequence and a "bug" in
nm-applet. On boot, NetworkManager (NM) is started by systemd. When you
log in, your desktop session starts nm-applet (it is optional after
all). nm-applet queries NM when nm-applet starts, gets the status and
tracks it as long as your session is running.
On wake up from hibernate, nm-applet picks up where it left off, but it
doesn't "check in" with NM so it doesn't know what the status is.
I'm
not sure how they coordinate (dbus, etc.), but that seems to be the
issue. Perhaps NM gets a different dbus identity on wakeup and
nm-applet doesn't find out about it. I simply don't know. I do recall
that on a previous version I saw errors in the system log that
nm-applet couldn't "find" NM for some odd reason. I don't have the
records any longer so I can't tell you exactly what it said, but that
was the gist of it.
IMHO, nm-applet should periodically query NM and, if it doesn't get a
response, restart itself. If it still doesn't get a response, then it
should pop up an error message about it (e.g. that NM isn't running or
some such thing).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- UNIX is actually quite user friendly. The problem is that it's -
- just very picky of who its friends are! -
----------------------------------------------------------------------