While you’re standing in a Paladin ally’s Aura of Courage:
[the Paladin] and friendly creatures within 10 feet of [the Paladin] can’t be Frightened while [the Paladin is] conscious.
Does this prevent effects that cause Frightened from applying at all, or only suspend them while you stand near your Paladin?
Example: I am standing next to my level 10+ Paladin friend, and we are facing an Ancient Red Dragon. It uses its Frightful Presence.
A) Do nothing – I am immune to this effect as a result of the aura.
B) Roll the saving throw – and if I fail the effect is applied to me, but the Frightened condition involved in it is suppressed as long as I am near my Paladin.
This Q&A asks a similar question, but after such an effect has already been applied to a PC – I feel the answer may be different when it comes to the initial application of the effect.
Due to the identical wording, it’s likely that any answers to this question would apply to the Devotion Paladin’s Aura of Devotion and charm effects as well.
I have a desktop machine running ubuntu 19.04
until a couple of days ago, while the machine goes idle correctly, after the latest software upgrades, it doesn’t run correctly:
Now, the system first shut down the screen, then, while attempting to suspend the machine, it fails and the machine continue running.
But, if I move the mouse or press a key on the keyboard, nothing happens.
The only way to resume is to force the suspend status with the power button, then the machine can be resumed.
As I didn’t make any change on the machine, I suppose that the incorrect behavior derive from the latest software upgrade.
I seem to be having some problem with suspend mode. Every time I try to suspend my laptop, it just locks the screen. Or maybe it successfully suspends just to resume only an instant after. What could cause such a behaviour?
I’m running 64-bit Ubuntu 19.04 on a Lenovo ideapad 310-15ISK laptop.
I am currently running Ubuntu 18.04.3 LTS on a desktop machine (8 year old). After a recent software upgrade, when I long-pressed the power button and then pressed on the suspend button, the computer failed to enter the suspend mode. The fan was still running and a running light was still on. Before the upgrade, everything was running smoothly; the fan will stop and the running light will turn blinking.
Is there anything I should configure to restore the old behaviour?
I have two wifi adapters, one built-in in the laptop and one TP-LINK Archer T3U dongle, whose drivers I installed from this repo. Here is the config:
wlxd037453eb553 IEEE 802.11AC ESSID:"myWiFi" Nickname:"rtl8822bu" Mode:Managed Frequency:5.28 GHz Access Point: ___ Bit Rate:867 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=95/100 Signal level=47/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 enp4s0 no wireless extensions. lo no wireless extensions. wlp3s0 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=200 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off
Each time the laptop wakes up from suspend, there is no connection and both adapters can’t find any networks. Even restarting the network manager doesn’t help, only reboot!
What could be the cause?
P.S.: I disabled the 2.4 Ghz band on the router because the dongle always used this band instead of 5 Ghz, so I sort of “forced” it to pick 5 Ghz.
My computer (Acer Aspire, Ubuntu 18.04.3) won’t wake up after it goes dark from being idle for too long. My keyboard lights up as usual when I hit a key, but the screen stays dark. I have to hold down the power button to shut down before I can turn it back on again. Help?
Using Ubuntu 19.04, Dell XPS 9370
Normally, after resuming from a suspend, I can see the lock screen. A keyboard press or mouse click brings up the password prompt so that i can log in.
Occasionally, Ubuntu will get stuck at the lock screen, mouse clicks and keyboard presses dont bring up the password prompt. I can still interact with other elements of the lock screen, but i am not able to log in.
Googling around ‘no password prompt after resume’ returns a lot of results, but these dont appear to be my specific problem.
- Any ideas what might be going on here?
- In the absence of a complete fix, is there a workaround that will let me log in?
Sometimes, when i return from a “Suspended” state, I can see some artifacts in random areas of some application windows.
They are quite annoying and sometimes they make the application totally unusable, to the point I have to close it and opening again. In some cases like the “switch user” screen, make it simply unusuable.
What are those things? Why do they appear? How can I avoid them?
I’m having a few problems with my Pop!Os (Gnome) installation with regards to it waking up from suspend.
When the computer is locked and goes in suspend by itself it seems the laptop has no trouble starting up again. The problem only manifests itself when the lid is closed and opened back up later on. While sometimes it will resume properly, other times it will completly freeze, or a mix of the following issues:
- Wifi card not detected (restarting network manager does nothing, persists through reboots, has to be a full shutdown for it to work again)
- Mouse not working
- Bluetooth not detected
Most of the time, I will not even be able to type my password in; the lock screen is completely frozen and unusable.
I am using a Razer Blade first generation (RZ09-01962), running
Pop!_OS 19.04 x86_64 and kernel
5.0.0-29-generic . I had to fix multiples issues to get the laptop working correctly, and so I have few tweaks activated:
Kernel Boot Options:.systemd.show_status=false i915.enable_rc6=0 quiet intel_idle.max_cstate=4 splash loglevel=0 button.lid_init_state=open
/proc/acpi/wakeup so it stays in suspend.
The caps locks that crashes everything has been remaped the escape with gnome tweaks
I tried multiple things to fix the network not working when I was able to log back in:
- wifi not working after sleep/suspend
Nothing really worked. I also tried hibernation instead of suspend but the computer just shutdowns when waking up.
I have full disk encryption so shutting down instead of suspending is not really an option unfortunately. I am running the power manager that popos ships with.
I am looking for a fix to it just “dying” when the lid is closed.
I have an older desktop that I converted to a file server using SAMBA. I have tried to set it up so that it will automatically sleep/suspend after 2 hours with the intent to use wake on lan when I need to access the files. I am able to manually make the server suspend (either by directly logging in to the physical computer or using RDP) and have WOL working, but it doesn’t automatically go to sleep.
When I go to the power settings (I installed the default desktop environment), there is no option to set up auto-suspend (the only option on the power tab is to set the delay for the screen to go blank). When I use gsettings to query “org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout” the result is 7200 and “sleep-inactive-ac-type” is suspend.
I read elsewhere that the default kernel for 18.04 causes suspend issues on some computers, so I am now using 4.17.19, but that did not fix the problem.
I’d greatly appreciate any help figuring this one out.