GNU bug report logs - #55625
GNOME: totem controls not accessible

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55625 in the body.
You can then email your comments to 55625 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Roman Riabenko <roman <at> riabenko.com>
To: bug-guix <at> gnu.org
Subject: GNOME: totem controls not accessible
Date: Wed, 25 May 2022 09:03:37 +0300

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

Message #8 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Roman Riabenko <roman <at> riabenko.com>, 55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 17:11:38 +0200

[Message part 1 (text/plain, inline)]

Roman Riabenko schreef op wo 25-05-2022 om 09:03 [+0300]:
> 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.

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.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Roman Riabenko <roman <at> riabenko.com>, 55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 17:20:50 +0200

[Message part 1 (text/plain, inline)]

Roman Riabenko schreef op wo 25-05-2022 om 09:03 [+0300]:
> 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

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.

[signature.asc (application/pgp-signature, inline)]

Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: bug-guix <at> gnu.org, Maxime Devos <maximedevos <at> telenet.be>,
 Roman Riabenko <roman <at> riabenko.com>, 55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 15:35:43 +0000

'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.

Message #20 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>, bug-guix <at> gnu.org, Roman Riabenko
 <roman <at> riabenko.com>, 55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 18:29:18 +0200

[Message part 1 (text/plain, inline)]

Tobias Geerinckx-Rice schreef op za 28-05-2022 om 15:35 [+0000]:
> '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.

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.

[signature.asc (application/pgp-signature, inline)]

Message #26 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>, Roman Riabenko
 <roman <at> riabenko.com>,  55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 18:34:46 +0200

[Message part 1 (text/plain, inline)]

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.

[signature.asc (application/pgp-signature, inline)]

Message #29 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Roman Riabenko <roman <at> riabenko.com>
To: Maxime Devos <maximedevos <at> telenet.be>, Tobias Geerinckx-Rice
 <me <at> tobias.gr>,  55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 22:15:36 +0300

[Message part 1 (text/plain, inline)]

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:
https://gitlab.gnome.org/GNOME/totem/-/issues/356
https://gitlab.gnome.org/GNOME/totem/-/issues/316
Though, I am not yet sure what the cause really is.

У сб, 2022-05-28 у 17:20 +0200, Maxime Devos пише:
> 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 ...

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 пише:
>(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*

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

[error.log (text/x-log, attachment)]

[stdout.log (text/x-log, attachment)]

Message #32 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Roman Riabenko <roman <at> riabenko.com>, Tobias Geerinckx-Rice
 <me <at> tobias.gr>,  55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 21:28:04 +0200

[Message part 1 (text/plain, inline)]

Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:
> > (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*
> 
> 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.

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.

[signature.asc (application/pgp-signature, inline)]

Message #35 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Roman Riabenko <roman <at> riabenko.com>, Tobias Geerinckx-Rice
 <me <at> tobias.gr>,  55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Sat, 28 May 2022 21:31:34 +0200

[Message part 1 (text/plain, inline)]

Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:
> (totem:4116): libpeas-WARNING **: 22:05:01.766: Type not found in
> introspection: 'PeasActivatable'
> 
> (totem:4116): libpeas-WARNING **: 22:05:01.766: Method
> 'PeasActivatable.deactivate' was not found

‘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.

[signature.asc (application/pgp-signature, inline)]

Message #38 received at 55625 <at> debbugs.gnu.org (full text, mbox):

From: Roman Riabenko <roman <at> riabenko.com>
To: Maxime Devos <maximedevos <at> telenet.be>, Tobias Geerinckx-Rice
 <me <at> tobias.gr>,  55625 <at> debbugs.gnu.org
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Mon, 30 May 2022 21:45:53 +0300

[Message part 1 (text/plain, inline)]

Hello

У сб, 2022-05-28 у 21:31 +0200, Maxime Devos пише:
> Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:
> > (totem:4116): libpeas-WARNING **: 22:05:01.766: Type not found in
> > introspection: 'PeasActivatable'
> > 
> > (totem:4116): libpeas-WARNING **: 22:05:01.766: Method
> > 'PeasActivatable.deactivate' was not found
> 
> ‘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.

(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

[output.txt (text/plain, attachment)]

Message #43 received at 55625-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Roman Riabenko <roman <at> riabenko.com>
Cc: 55625-done <at> debbugs.gnu.org, Tobias Geerinckx-Rice <me <at> tobias.gr>,
 Maxime Devos <maximedevos <at> telenet.be>
Subject: Re: bug#55625: GNOME: totem controls not accessible
Date: Tue, 22 Oct 2024 18:30:11 +0900

Hi,

Roman Riabenko <roman <at> riabenko.com> writes:

> Hello
>
> У сб, 2022-05-28 у 21:31 +0200, Maxime Devos пише:
>> Roman Riabenko schreef op za 28-05-2022 om 22:15 [+0300]:
>> > (totem:4116): libpeas-WARNING **: 22:05:01.766: Type not found in
>> > introspection: 'PeasActivatable'
>> > 
>> > (totem:4116): libpeas-WARNING **: 22:05:01.766: Method
>> > 'PeasActivatable.deactivate' was not found
>> 
>> ‘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.
>
> (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.

I've updated Totem to its latest commit, which fixed a problem with the
seek bar getting stuck, as well as added multiple inputs that should
bring it in line in terms of features with GNOME's official Flatpak
distribution of Totem.

Closing, but do reopen if some issues remain!

-- 
Thanks,
Maxim

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.