GNOME: totem controls not accessible

Hello

When viewing a video in totem, totem controls in the botton are not

accessible with the mouse. It is possible to control the playback with

keyboard.

totem version 3.38.1

clutter version 1.26.2 in totem's dependencies per "guix show totem"

Roman

Roman Riabenko schreef op wo 25-05-2022 om 09:03 [+0300]:

What kind of accessibility are you looking for? Supporting only the

mouse is usually considered to be inaccessible and additionally

supporting keyboard control is usually considered good for

accessibility, so I assume you're referring to a different kind of

accessibility (*) here.

(*) https://developer.gnome.org/documentation/guidelines/accessibility.html

and other sources have some information on what is usually meant by accessibility.

Greetings,

Maxime.

Roman Riabenko schreef op wo 25-05-2022 om 09:03 [+0300]:

I tried reproducing this:

$ guix shell --pure totem -- totem '/home/[...]/[...].mp4'

but for me it was even worse, it was unable to play the video at all:

** Message: 15:13:20.263: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)1, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)

** Message: 15:13:20.263: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)2.2, profile=(string)main (H.264 (Main Profile) decoder)

Looks like a bug, especially since the package description says:

synopsis: Simple media player for GNOME based on GStreamer

description: Totem is a simple yet featureful media player for GNOME

which can read a large number of file formats.

Adding gst-plugins-bad resolves this.

Maybe the description should state that additional formats are

available from gst-plugins-bad may need to be installed? Though then

bad plugins would be recommended ...

Greetings,

Maxime.

'Accessible' just means 'available' (toeganklijk, same problem though).

It does not generally imply 'accesibility' as used in various fields of engineering, although of course we're biased to read it so.

Anyway, Maxime: do the buttons work for you once the codec's fixed? My computer seems to have frozen whilst building them.

Ah, engineering.

Kind regards,

T G-R

Sent on the go. Excuse or enjoy my brevity.

Tobias Geerinckx-Rice schreef op za 28-05-2022 om 15:35 [+0000]:

Pressing the ‘pause’ buttons turns it into ‘play’ button and the other

way around.

The next chapter/movie button doesn't work, but the file that is

playing doesn't have any chapters, so not surprising. OTOH, there is

another .mp4 in the same directory.

The previous/next chapter are ‘accessible’ in the sense that they are

visible, the cursor could be moved on top of them and moving the cursor

above them displays a tiny popup, but they are unclickable.

I don't know what exactly was meant by accessibility (the existence of

the buttons or the pressability?) in the bug report.

There is some weirdness though:

* no sound (though that might be a problem in the played mp4 itself,

there were some recording problems)

* The pause/play button don't seem to have any effect apart from

toggling what the button looks like -- the played mp4 remains

frozen.

Greetings,

Maxime.

also, some other potential problems:

(totem:147294): Gtk-WARNING **: 16:32:42.791: Could not load a pixbuf

from /org/gtk/libgtk/theme/Adwaita/assets/bullet-symbolic.svg.

This may indicate that pixbuf loaders or the mime database could not be

found.

** (totem:147294): WARNING **: 16:32:42.897: An error occurred trying

to open logo org.gnome.Totem: Icon 'org.gnome.Totem' not present in

theme gnome

^^^ icon problems

(totem:147294): Totem-WARNING **: 16:32:42.898: Failed to acquire

screensaver proxy: Failed to execute child process ?dbus-launch? (No

such file or directory)

^^^ file names needing a substitute*

Greetings,

Maxime.

Thank you for looking into this and sorry for confusion!

I just noticed that my issue happens only under Wayland. I configured

my system with Wayland and completely forgot about it. Now, I relogined

into Xorg session from GDM greeter and there was no such problem with

totem. Still, Wayland should be supported...

The issue is: when I click or drag on the contorls in the panel in the

bottom of totem, nothing happens, as if they are a picture. When I

double click on them, totem goes full screen or is restored from full

screen respectively.

Because I realized that it is related to Wayland, I looked up totem

issues and found two similar reports:

Though, I am not yet sure what the cause really is.

? ??, 2022-05-28 ? 17:20 +0200, Maxime Devos ????:

After some trial-and-error, I had installed gst-libav in my user

profile to play mp4 files. gst-plugins-bad is just one of the options.

After Debian, I am quite accustomed that totem is not playing "bad"

formats out-of-the-box, so there was no surprise here for me. The

synopsis could tell that the player is extensible and supports

additional formats through GStreamer plugins.

? ??, 2022-05-28 ? 18:34 +0200, Maxime Devos ????:

I do not see this when I start totem from terminal. Maybe that is

because I am using GNOME. I mean that I have the system configured with

(service gnome-desktop-service-type) and totem is installed as a system

application.

For your reference, I attach what I get from the terminal when I start

totem from terminal, play a video from the library, click and double

click on controls, then close. I see nothing relevant there. The

error.log shows something related to plugins. The stdout.log shows how

totem fails to generate thumbnails for videos. I opened a different

issue for the latter: https://issues.guix.gnu.org/55624

Roman

Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:

Probably the reason is that I am doing things in a ‘pure’ environment

here:

$ guix shell --pure totem -- totem a-file.mp4

In a ‘pure’ environment, various environment variables are unset, which

avoids interference with other installed applications, which can be

usefel for debugging. If you try "guix shell --pure totem -- totem",

you'll probably at least see the logo warning.

I don't expect it to be related to the issue you originally reported

though.

Greetings,

Maxime.

Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:

‘Activatable’ might mean buttons and such, maybe GI_TYPELIB_PATH needs

to be added to the wrap-program in the package definition of 'totem'

like for some other GTK applications.

Greetings,

Maxime.

Hello

? ??, 2022-05-28 ? 21:31 +0200, Maxime Devos ????:

(I looked at rhythmbox for an example.) When I add GI_TYPELIB_PATH to

wrap-program, libpeas-WARNING stops appearing. Though I notice no other

change. I also tried adding GUIX_PYTHONPATH as in rhythmbox, but I

notice no effect. I attach an example output from terminal.

Roman