** Changed in: mutter
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882462
Title:
Displays wake up pre-maturely (likely driven by
Also try setting the monitor's input source (there's a button for that
surely) to something other than 'Auto'. I fear Auto might be doing some
active scanning and wake itself up when it comes back to the connector
that you're using but wish to keep off.
--
You received this bug notification
I've set this bug to track:
https://gitlab.gnome.org/GNOME/mutter/-/issues/877
but there's also:
https://gitlab.gnome.org/GNOME/mutter/-/issues/976
and maybe also see:
https://gitlab.gnome.org/GNOME/mutter/-/issues/915
Although I think we should be careful to keep this bug about a
OK, so an update. I removed fwupd from my system and I can confirm that
once I can get the displays to sleep, they stay that way as they should.
Now for the weird part... they won't go to sleep on their own. Doesn't
matter whether I'm in Wayland or Xorg - they won't go to sleep on their
own. DPMS
Looking at the most recent log in comment #6 again, that was back when
you had fwupd and boltd running. I wonder if you could provide a system
log from a night where those were disabled?
journalctl -b0 > journal.txt
I'm still particularly skeptical of fwupd because it appears that caused
a
Looking at the most recent log in comment #6 again, that was back when
you had fwupd and boltd running. I wonder if you could provide a system
log from a night where those were disabled?
journalctl -b0 > journal.txt
I'm still particularly skeptical of fwupd because it appears that cause
a
Quick update. I do not have tlp installed and it also does it on Wayland.
I'm out of ideas.
On Wed, Jun 24, 2020 at 9:25 PM Daniel van Vugt <1882...@bugs.launchpad.net>
wrote:
> Another idea: You seem to be using the default Xorg session so that
> increases the possible set of components that
Another idea: You seem to be using the default Xorg session so that
increases the possible set of components that could tamper with the
power state. Please try logging into 'Ubuntu on Wayland' to see if the
problem happens there.
And another idea: Check that you don't have 'tlp' installed. It
I disabled the color profile of both of my displays and my printer and the
displays are still awake in the morning. I did check the PID of gnome-shell
and it is the same so there don't appear to be any silent crashes.
--
You received this bug notification because you are a member of Desktop
Also, you say there's no evidence of crashes but we should check to see
if there are any crashes occurring without a trace. To do that please
run:
pidof gnome-shell
in the evening and again in the morning. They should both report the
same process ID.
--
You received this bug notification
There's a slight chance this is a side-effect of gnome-settings-daemon
trying to enforce the default colour profile. It's a bit of a mess but I
believe that does so by programming the display hardware directly,
independently of the power mode mutter/gnome-shell last set. So if
If you report it upstream:
https://gitlab.gnome.org/GNOME/mutter/issues
then they will be able to provide more suggestions to better understand
what power management is doing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
OK, I'm out of ideas. Using do not disturb and thereby eliminating
notifications didn't help either.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882462
Title:
Displays wake
I don't use nightlight and disabling bolt didn't help. As I think it's
notification related, I'm going to turn on do not disturb this evening and
see what happens.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Also check that you don't have a Night Light schedule which might be
triggering it:
Settings > Screen Display > Night Light [in the top bar]
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I've disabled fwupd and cups and I still see it in the morning when I come
into the office. I'm inclined to shutdown boltd and see if that stops it
from happening since I don't have anything plugged into the thunderbolt
port at this time.
--
You received this bug notification because you are a
@Dean, thanks for the log. Did you see the issue directly on boot? Did
you note the time where you saw it (would be useful to match the log
activity)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
The only possibly-related information I can see there is:
Jun 12 06:17:30 hero boltd[7027]: power: setting force_power to ON
Jun 12 06:17:30 hero boltd[7027]: power: state changed: supported/on
Jun 12 06:17:30 hero boltd[7027]: power: guard '3' for 'fwupd' active
which may be relevant
The only possibly-related information I can see there is:
Jun 12 06:17:30 hero boltd[7027]: power: setting force_power to ON
Jun 12 06:17:30 hero boltd[7027]: power: state changed: supported/on
Jun 12 06:17:30 hero boltd[7027]: power: guard '3' for 'fwupd' active
which may be relevant
I rebooted last night for a new kernel. This morning the monitors were
on with nothing but a cursor on the screen again. Attached is the
journal output.
** Attachment added: "lastboot.log.gz"
Could you add your 'journalctl -b 0' log when you notice the issue and
add a note about the time where you saw the issue/interacted with the
computer?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
I have no crashes in /var/crash of gnome-shell and I've removed all non-
system extensions. I'll post an update once I observe either the
behavior or lack there of.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
The most common issue we're seeing in this area right now is that gnome-
shell crashes on lock, and so locking fails. That's bug 184 with a
fix coming soon. Please also check /var/crash in case there is any
evidence there (it might be a different crash).
Secondly, we find extensions cause a
** Attachment added: "Screens-awake.jpg"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+attachment/5381404/+files/Screens-awake.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
24 matches
Mail list logo
