Ubuntu
totem package

Totem not running after upgrade to Ubuntu 22.04 (due to ~/.cache/gstreamer-1.0)

Bug #1971768 reported by Uttam Pal
46
This bug affects 7 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

$ totem

** (totem:106519): WARNING **: 01:12:30.962: Element 'gtkglsink' is missing, verify your installation

** (totem:106519): WARNING **: 01:12:30.962: Element 'glsinkbin' is missing, verify your installation

(totem:106519): GStreamer-CRITICAL **: 01:12:33.537: gst_bus_set_flushing: assertion 'GST_IS_BUS (bus)' failed

(totem:106519): GLib-GObject-CRITICAL **: 01:12:33.537: g_object_set: assertion 'G_IS_OBJECT (object)' failed
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-02-11 (448 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
NonfreeKernelModules: nvidia_modeset nvidia
Package: totem 42.0-1ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-29.30-generic 5.15.35
Tags: wayland-session jammy
Uname: Linux 5.15.0-29-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-04-30 (5 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

See original description
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. What's the output of

$ dpkg -l | grep gstreamer1.0-gtk3

?

Changed in totem (Ubuntu):
status: New → Incomplete
Daniel van Vugt (vanvugt)
tags: added: jammy
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1971768

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Uttam Pal (uttam2707) wrote :

$ dpkg -l | grep gstreamer1.0-gtk3
ii gstreamer1.0-gtk3:amd64 1.20.1-1ubuntu1 amd64 GStreamer plugin for GTK+3

Revision history for this message
Uttam Pal (uttam2707) wrote : Dependencies.txt

apport information

tags: added: apport-collected wayland-session
description: updated
Revision history for this message
Uttam Pal (uttam2707) wrote : GstreamerVersions.txt

apport information

Revision history for this message
Uttam Pal (uttam2707) wrote : LogAlsaMixer.txt

apport information

Revision history for this message
Uttam Pal (uttam2707) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Uttam Pal (uttam2707) wrote : ProcEnviron.txt

apport information

Revision history for this message
Uttam Pal (uttam2707) wrote : XorgLog.txt

apport information

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: Totem not running on Ubuntu 22.04 Wayland

what's the output of

$ gst-inspect-1.0 gtkglsink

?

Revision history for this message
Sebastien Bacher (seb128) wrote :

could you also try if moving ~/.cache/gstreamer-1.0 workaround the issue?

Revision history for this message
Uttam Pal (uttam2707) wrote :

$ gst-inspect-1.0 gtkglsink
No such element or plugin 'gtkglsink'

Revision history for this message
Uttam Pal (uttam2707) wrote :

after moving ~/.cache/gstreamer-1.0

$ totem
Stream with high frequencies VQ coding
Gdk-Message: 13:03:01.725: Error flushing display: Protocol error

$ totem
Stream with high frequencies VQ coding

(totem:21557): GStreamer-GL-CRITICAL **: 13:03:05.865: Failed to flush Wayland connection

(totem:21557): GStreamer-GL-CRITICAL **: 13:03:05.865: Failed to flush Wayland connection

Gdk-Message: 13:03:05.865: Error flushing display: Protocol error

Revision history for this message
Michael Steenbeek (gymnasiast) wrote :
Download full text (7.3 KiB)

I have the same problem, although I’m running on X11, not Wayland. After trying the workaround in post #11, Totem will open, but attempting to play anything, will either display an error saying the file cannot be cause, or cause it to segfault immediately:

```
$ totem

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.402: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.428: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.464: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.486: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.503: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.519: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.537: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.559: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.569: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.587: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.603: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:35.649: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.065: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.092: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.125: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.141: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.156: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.175: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.192: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.207: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.223: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.241: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.260: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:37.277: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:38.218: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:38.250: gst_buffer_get_meta: assertion 'buffer != NULL' failed

(totem:1012805): GStreamer-CRITICAL **: 09:29:38.277: gst_buffer_get_...

Read more...

Revision history for this message
Uttam Pal (uttam2707) wrote : Re: [Bug 1971768] Re: Totem not running on Ubuntu 22.04 Wayland
Download full text (9.3 KiB)

totem flatpak is working fine on Ubuntu 22.04 Wayland

On Fri, Jul 1, 2022 at 1:11 PM Michael Steenbeek <email address hidden>
wrote:

> I have the same problem, although I’m running on X11, not Wayland. After
> trying the workaround in post #11, Totem will open, but attempting to
> play anything, will either display an error saying the file cannot be
> cause, or cause it to segfault immediately:
>
> ```
> $ totem
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.402:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.428:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.464:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.486:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.503:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.519:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.537:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.559:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.569:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.587:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.603:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:35.649:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.065:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.092:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.125:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.141:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.156:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.175:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.192:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.207:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.223:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.241:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.260:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:1012805): GStreamer-CRITICAL **: 09:29:37.277:
> gst_buffer_get_meta: assertion 'buffer != NULL' failed
>
> (totem:10128...

Read more...

Revision history for this message
Michael Johnson (micheallsy) wrote : Re: Totem not running on Ubuntu 22.04 Wayland

I'm surprised that anyone can change the status of the bug. Anyway I encountered it too(#1982656)

Changed in totem (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Comment #13 shows Uttam fixing this bug. The new issue that occurred after that is an Nvidia Wayland bug 1966787.

summary: - Totem not running on Ubuntu 22.04 Wayland
+ Totem not running after upgrade to Ubuntu 22.04 (due to
+ ~/.cache/gstreamer-1.0)
Changed in totem (Ubuntu):
status: Incomplete → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.