Well. I got some luck in reproducing. Got it twice today (23:14:03 and
23:40:51), and these log messages were seen right around when the screen
locked:

$ journalctl --user  -S '-2 days' | grep CLUTTER -A2

mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: invalid (NULL) pointer instance
mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
--
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: invalid (NULL) pointer instance
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
--
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: invalid (NULL) pointer instance
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

In fact, I know what I was doing:

2024-05-03 23:40:45 sleep 5; start-vpn
2024-05-03 23:42:44 history | tail -n10


Somewhere around 23:40:48 I locked the screen, and at 23:40:50+ code started 
running that triggers a (maybe) GUI notification popup.

Full disclosure, that VPN notification popup is mine:
https://github.com/ossobv/openvpn-u2f-setup/blob/main/openvpn-u2f-ask-password


I'm not entirely sure what the sequence of events is here, but those dbus/glib 
interactions around the time when things break are too much of a coincidence. 
This also explains why I'm the only one having this issue.


mei 03 23:40:51 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: Got 
pyinotify event
mei 03 23:40:51 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. 
is_in_screensaver org.gnome.ScreenSaver True
mei 03 23:40:51 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. Ignoring 
ask-password request because in screensaver mode
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: invalid (NULL) pointer instance
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
mei 03 23:42:18 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: Re-reading 
/run/systemd/ask-password
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.28' 
(uid=1000 pid=362660 comm="/usr/bin/gnome-shell " label="unconfined")
mei 03 23:42:18 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. 
is_in_screensaver org.gnome.ScreenSaver True
mei 03 23:42:18 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. Ignoring 
ask-password request because in screensaver mode
mei 03 23:42:18 wortel.kiwi ubuntu-appindicat...@ubuntu.com[362660]: unable to 
update icon for software-update-available
mei 03 23:42:18 wortel.kiwi ubuntu-appindicat...@ubuntu.com[362660]: unable to 
update icon for livepatch
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Successfully activated service 'org.freedesktop.FileManager1'
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Can't update stage views actor 
<unnamed>[<MetaWindowGroup>:0x57eecffe8350] is on because it needs an 
allocation.
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Can't update stage views actor 
<unnamed>[<MetaWindowActorX11>:0x57eed23232f0] is on because it needs an 
allocation.
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Can't update stage views actor 
<unnamed>[<MetaSurfaceActorX11>:0x57eed2324db0] is on because it needs an 
allocation.
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Activating service name='org.gnome.ArchiveManager1' requested by ':1.97' 
(uid=1000 pid=364706 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" 
label="un>
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Successfully activated service 'org.gnome.ArchiveManager1'
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: DING: Detected async api for 
thumbnails
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: DING: GNOME nautilus 42.6
mei 03 23:42:21 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: Got 
pyinotify event
mei 03 23:42:21 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: file is 
now gone /run/systemd/ask-password/ask.waet3j
mei 03 23:42:21 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: Got 
pyinotify event
mei 03 23:42:21 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. 
is_in_screensaver org.gnome.ScreenSaver False
mei 03 23:42:21 wortel.kiwi openvpn-u2f-ask-password[364589]: WARNING. Skipped 
auth bit? Do nothing..

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064716

Title:
  gnome-terminal sometimes very dark after gnome unlock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to