Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Tim]

Allegedly, on or about 29 August 2016, Ranjan Maitra sent:
> 1. In /etc/default/grub
> 
> add --> resume=UUID="" <-- to the line GRUB_CMDLINE_LINUX= 

I seem to recall that was only necessary if your swap was a file rather
than a partition, or you had multiple swap partitions.

Perhaps you can clarify what you use, and someone else can clarify if
this is the case.

-- 
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

Boilerplate:  All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.

Using Windows software is like coating all your handtools with sewage.


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Rick Stevens]

On 08/30/2016 03:44 PM, Ranjan Maitra wrote:
> Rick,
> 
> Thanks! 
> 
> On Tue, 30 Aug 2016 13:54:38 -0700 Rick Stevens  wrote:
> 
>>
>> 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).
> 
> Your explanation may be right, but I wonder why this problem has only 
> happened to me with F24 systems. This problem did not happen with F23 
> installations. So, unless this bug recently came in, then I don't know why it 
> worked just fine with the old setup.

I had issues with F23 doing this on occasion. I believe it was a point
where NM had been updated but nm-applet hadn't caught up yet. I don't
recall exactly. Had similar issues with bluetooth (those were definitely
dbus-related).

> Btw, assuming that this is a bug, where should I file it? Before that, I 
> should perhaps make sure and look at the logs that you talked about here? 
> Which logs should I check?

I'd assume the bug should be filed against both NM and nm-applet since
it's some sort of mis-interaction between them and it's not clear whose
mechanism should be followed. As far as logs, I'd check both dmesg and
the system log for things containing "network".
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
- IGNORE that man behind the keyboard!   -
-- The Wizard of OS  -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Greg Woods]

On Tue, Aug 30, 2016 at 6:05 PM, Doug H. 
wrote:

> While waiting for a bug fix, you might try setting up a post hybernate
> action.
>

I have done something similar myself. I use ipsec-tools based VPN, and this
has never properly recovered from a hibernate without a restart. I also
have one to kill all my ssh sessions; I am a server administrator by trade,
so I usually have several ssh sessions to different hosts open, and if I
don't kill the ssh before hibernate, I wind up with a bunch of hung windows
on resume that I then have to close manually.

--Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Doug H.]

On Mon, 2016-08-29 at 18:37 -0500, Ranjan Maitra wrote:
> Hi,
> 
> 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.
> 
> I have set up, after installation, hibernate with F24 using the
> techniques that are now required since the days of F22 (or so). Here
> is what I did:
> 
> 1. In /etc/default/grub
> 
> add --> resume=UUID="" <-- to the line GRUB_CMDLINE_LINUX= 
> 
> where the uuid is obtained using blkid.
> 
> then I do the following:
> 
> 2. sudo bash -x grub2-mkconfig
> 3. sudo bash -x grub2-mkconfig -o /boot/grub2/grub.cfg
> 
> and after rebooting, hibernate works.
> 
> 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.
> 
> 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.
> 
> So, what should I be doing to avoid having to kill and restart my nm-
> applet? Is this a bug somewhere (some hook not being turned on, as
> used to happen with suspend in the bad old days of early Fedora) and
> if so, where should I file it (under what component in BZ)? 


While waiting for a bug fix, you might try setting up a post hybernate
action. I use suspend, but I found the below "fix" to work most of the
time to the need to hit the need for hitting a key to wake my monitor
after resuming from suspend. You would clearly need to change it for
your usage:

Command line to exit screen saver:
xscreensaver-command -deactivate
Added
to new file: cat  /etc/systemd/system/post-suspend.service
[Unit]
Descrip
tion=Run post-suspend
After=suspend.target
#After=hibernate.target
#After=
hybrid-sleep.target

[Service]
#ExecStart=/bin/xscreensaver-command -deactivate
ExecStart=/bin/su - user -c "/bin/xscreensaver-command -deactivate"

[Install]
WantedBy=suspend.target
#WantedBy=hibernate.target
#WantedBy=hybrid-sleep.target





> Many thanks and best wishes,
> Ranjan
> 
> PS: As an aside, one of the parameters in: /etc/default/grub, I have
> GRUB_DISABLE_RECOVERY="true" -- I also tried with 
> GRUB_DISABLE_RECOVERY="false" but there was no visible effect. I am
> not completely sure what this parameter does because it seems to give
> me the same result irrespective of whether or not it is set to
> "true".

If my personal note about that is correct, then here is what that is
about:

# Setting GRUB_DISABLE_RECOVERY to "false" will enable the single user
# mode / recovery entries.  The trouble is that the dnf auto install
# of new kernels does not use it so I would have to run
# `grub2-mkconfig -o /boot/grub2/grub.cfg` after each kernel update.
# I don't think it is worth bothering with.
GRUB_DISABLE_RECOVERY="true"

-- 
Doug H.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Ranjan Maitra]

Rick,

Thanks! 

On Tue, 30 Aug 2016 13:54:38 -0700 Rick Stevens  wrote:

> 
> 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).

Your explanation may be right, but I wonder why this problem has only happened 
to me with F24 systems. This problem did not happen with F23 installations. So, 
unless this bug recently came in, then I don't know why it worked just fine 
with the old setup.

Btw, assuming that this is a bug, where should I file it? Before that, I should 
perhaps make sure and look at the logs that you talked about here? Which logs 
should I check?

Many thanks again!
Ranjan


FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your 
desktop!
Check it out at http://www.inbox.com/marineaquarium

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Rick Stevens]

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  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, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 226437340   Yahoo: origrps2 -
--
-   UNIX is actually quite user friendly.  The problem is that it's  -
-  just very picky of who its friends are!   -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: 

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Ranjan Maitra]

Hi,

Thanks for the response.

On Mon, 29 Aug 2016 19:19:33 -0700 Samuel Sieb  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 &

and then the behaviour is back to normal in the sense that the applet shows 
"connected" and I have the available wifi networks listed. The big issue is 
that this has to be done every time since Fedora 24.

> 
> > PS: As an aside, one of the parameters in: /etc/default/grub, I have 
> > GRUB_DISABLE_RECOVERY="true" -- I also tried with
> > GRUB_DISABLE_RECOVERY="false" but there was no visible effect. I am not 
> > completely sure what this parameter does because it seems to give me the 
> > same result irrespective of whether or not it is set to "true".
> >
> https://bugzilla.redhat.com/show_bug.cgi?id=1055759

So, I guess the solution is to get rid of dracut-config-rescue. But it is still 
not clear to me what this GRUB_DISABLE_RECOVERY does.

Many thanks,
Ranjan


Can't remember your password? Do you need a strong and secure password?
Use Password manager! It stores your passwords & protects your account.
Check it out at http://mysecurelogon.com/password-manager

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Samuel Sieb]

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.



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.


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.


PS: As an aside, one of the parameters in: /etc/default/grub, I have 
GRUB_DISABLE_RECOVERY="true" -- I also tried with
GRUB_DISABLE_RECOVERY="false" but there was no visible effect. I am not completely sure 
what this parameter does because it seems to give me the same result irrespective of whether or not 
it is set to "true".


https://bugzilla.redhat.com/show_bug.cgi?id=1055759
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

F24: waking up from hibernate no longer wakes nm-applet (however existing connection works fine)

[Ranjan Maitra]

Hi,

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.

I have set up, after installation, hibernate with F24 using the techniques that 
are now required since the days of F22 (or so). Here is what I did:

1. In /etc/default/grub

add --> resume=UUID="" <-- to the line GRUB_CMDLINE_LINUX= 

where the uuid is obtained using blkid.

then I do the following:

2. sudo bash -x grub2-mkconfig
3. sudo bash -x grub2-mkconfig -o /boot/grub2/grub.cfg

and after rebooting, hibernate works.

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.

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.

So, what should I be doing to avoid having to kill and restart my nm-applet? Is 
this a bug somewhere (some hook not being turned on, as used to happen with 
suspend in the bad old days of early Fedora) and if so, where should I file it 
(under what component in BZ)? 

Many thanks and best wishes,
Ranjan

PS: As an aside, one of the parameters in: /etc/default/grub, I have 
GRUB_DISABLE_RECOVERY="true" -- I also tried with 
GRUB_DISABLE_RECOVERY="false" but there was no visible effect. I am not 
completely sure what this parameter does because it seems to give me the same 
result irrespective of whether or not it is set to "true".

Best wishes,
Ranjan


FREE 3D EARTH SCREENSAVER - Watch the Earth right on your desktop!
Check it out at http://www.inbox.com/earth

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org