Bug 32087

Summary:	org.gnome.Shell.Screencast tries to "open file /tmp" hundreds of times and fail (of course)
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	GNOME maintainers <gnome>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	davidwhodgins
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	Gnome...	CVE:
Status comment:

Description Morgan Leijström 2023-07-08 20:03:36 CEST

Description of problem:

right after logging in, journalctl show a series of hundreds of repeated two lines:

 org.gnome.Shell.Screencast[10103]: Failed to open file /tmp, continuing redirect to STDERR

 org.gnome.Shell.Screencast[10103]: Log data will be written to file: /tmp


We dont have a /tmp root folder nor file... so... ??
Seem to be a missing definition of where it should log to?


Version:
Current cauldron, including updates_testing

Comment 1 Dave Hodgins 2023-07-14 16:28:44 CEST

In an m9 vb guest, fully updated including updates testing, after logging
into gnome and opening a terminal ...
$ journalctl -b --no-h|grep -i screencast
Jul 14 09:59:50 dbus-daemon[3756]: [session uid=1000 pid=3756] Activating service name='org.gnome.Shell.Screencast' requested by ':1.17' (uid=1000 pid=3842 comm="/usr/bin/gnome-shell")

Just the one line.

The only screencast files are ...
/usr/share/dbus-1/interfaces/org.gnome.Shell.Screencast.xml
/usr/share/dbus-1/services/org.gnome.Shell.Screencast.service
/usr/share/gnome-shell/org.gnome.Shell.Screencast
/usr/share/gnome-shell/org.gnome.Shell.Screencast.src.gresource

Looking at the xml file, it's used to record screen contents.

I was able to use print screen to save a copy of the screen contents to
the clipboard, without triggering any messages in the journal.

Any idea how it was triggered?

CC: (none) => davidwhodgins

Comment 2 Dave Hodgins 2023-07-14 17:31:58 CEST

After some more digging, found out that screencast requires pipewire.
After switching to pipewire, alt+ctrl+shift+r successfully allowed capturing
a webm video of the desktop. After that, the journal has ...
$ journalctl -b --no-h|grep -i screencast
Jul 14 11:02:44 dbus-daemon[3436]: [session uid=1000 pid=3436] Activating service name='org.gnome.Shell.Screencast' requested by ':1.23' (uid=1000 pid=3615 comm="/usr/bin/gnome-shell")
Jul 14 11:02:45 org.gnome.Shell.Screencast[3660]: libEGL warning: DRI2: failed to authenticate
Jul 14 11:02:45 dbus-daemon[3436]: [session uid=1000 pid=3436] Successfully activated service 'org.gnome.Shell.Screencast'
Jul 14 11:04:53 dbus-daemon[3436]: [session uid=1000 pid=3436] Activating service name='org.gnome.Shell.Screencast' requested by ':1.23' (uid=1000 pid=3615 comm="/usr/bin/gnome-shell")
Jul 14 11:04:53 org.gnome.Shell.Screencast[9188]: libEGL warning: DRI2: failed to authenticate
Jul 14 11:04:53 dbus-daemon[3436]: [session uid=1000 pid=3436] Successfully activated service 'org.gnome.Shell.Screencast'
Jul 14 11:04:53 org.gnome.Shell.Screencast[9188]: *** pw_stream_set_error called from wrong context, check thread and locking: Operation not permitted
Jul 14 11:04:53 org.gnome.Shell.Screencast[9188]: *** pw_stream_set_error called from wrong context, check thread and locking: Operation not permitted
Jul 14 11:10:12 org.gnome.Shell.Screencast[9188]: *** pw_stream_set_error called from wrong context, check thread and locking: Operation not permitted
Jul 14 11:10:12 org.gnome.Shell.Screencast[9188]: *** pw_stream_set_error called from wrong context, check thread and locking: Operation not permitted


So it works for me.

Comment 3 Morgan Leijström 2023-07-17 13:04:44 CEST

Thank you for checking.

Today i get same as you...

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME