What | Removed | Added |
---|---|---|
OS | Other | openSUSE Tumbleweed |
Hardware | Other | HP |
I too have been encountering this issue journalctl: Jun 30 09:28:02 Sus dbus-daemon[5265]: [session uid=1000 pid=5265] Successfully activated service 'org.gnome.Shell.Screencast' Jun 30 09:28:02 Sus org.gnome.Shell.Screencast[7321]: *** pw_stream_set_error called from wrong context, check thread and locking: Operation not permitted Jun 30 09:28:16 Sus dbus-daemon[5265]: [session uid=1000 pid=5265] Activating service name='org.gnome.Shell.Screencast' requested by ':1.17' (uid=1000 pid=6025 comm="/usr/bin/gnome-shell") Jun 30 09:28:16 Sus dbus-daemon[5265]: [session uid=1000 pid=5265] Successfully activated service 'org.gnome.Shell.Screencast' Jun 30 09:28:16 Sus org.gnome.Shell.Screencast[7382]: *** pw_stream_set_error called from wrong context, check thread and locking: Operation not permitted Jun 30 09:28:16 Sus gnome-shell[6025]: Screencast failed during phase STARTUP: GLib.Error shell-screencast-error: GDBus.Error:org.gnome.Shell.Screencast.Error.AllPipelinesFailed: All pipelines failed to start